Termination Code 2 after patch.

    I can confirm what others said. I tried a friends account right after i used my own (and crashed) and there was no issue connecting with their account whatsoever.

    My own account still crashes before or right when i click on the server.

    So it has to do with the account

    I don't know if this can help the support, but this happened months ago (just look to old posts in forum, around the end of october).

    Some accounts were out of game for about 3 hours.

    I even wrote a ticket, that time too, and I don't know if they could fixed it or it was just the game which has/had some problems with our accounts <.<

    So pls, just check if you did something in october to unblock our accounts and do the same now.. maybe it will work.

    Quote from Chevv

    that wont work
    you would have to redirect

    Code
    1. serverlist.tera.gameforge.com

    to somewhere local then do port redirection and have that request then forwarded to

    serverlist.tera.gamefroge.com:443
    so basically you need something that does what a reverse proxy or loadbalancer does

    I was thinking more of redirecting that request to localhost with a copy of that file on my pc. At which point I figured I'd have to run WAMP or XAMP or similar to serve it and it's getting beyond silly. It's not a fix that could be easily shared amongst forum readers, even if it worked.

    I wonder if it has something to do with the fact what I tried login to classic server before Feb, 12th or not. Anyone?

    My installation, like many others, was fine pre-patch. Post-patch it's broken. We're just really slinging around ideas but the fix is going to have to come from GF.

    I was playing just fine on Classic server before the maintenance at 16h, but now game crashes on server select screen. So what happened during that maintenance that made my account not be able to play?

    Hey everyone!


    Just to briefly let you know that we're aware of the issue, and that it's not something newly introduced with the previous maintenance (so we cannot do a roll-back unfortunately).


    That being said, it being an account specific issue, we're trying to pin-point the exact cause, and have also contacted the developer to get their expertise to solve it.


    We're sorry that a portion of our players are unable to access the Classic Server, and will do our best to let you know once we have a viable solution at hand, though this might not be in the immediate future :(


    Thank you for your continued reports - please also make sure to create a support ticket, so we can gather all the affected accounts to better pin-point the cause of this disturbance!


    Atmorph


    Hi Atmorph - There are quite a few of us who can hold our own with IT issues. Would it possible for you to share with us what the utterly nebulous 'Termination Code 2' means in the real world? Some people have fixed this themselves by deleting cached files but it hasn't worked for me or many others. If you could be more open about what the fault is, perhaps we could find a fix at our end?


    I wasn't able to log before the 2nd maintenance and I'm sadly affected by the "Termination Code 2" error. Wrote ticket just like Atmorph suggested to be on the locked accounts list.


    So just a question - will I (and others like me) be able to obtain the "[Classic] Tenacious Chest" reward regardless of today's issues or "sorry, stuff happens"?


    Atmorph , Athena ?


    [this is kind of important, if I won't be able to get it then I won't have to bother to log each day when I won't have time to play just for this reward]

    Hi there. I am on the "Termination Code 2" band-wagon. I was really looking forward to playing as I am off today and tomorrow. I do hope that you'll be able to figure this whole mess out, before too late. I have faith and I know these things might take time, but the waiting is 'killing' me :p

    Same here. Support ticket raised and waiting for a fix.


    Tried so far to repair launcher, enable Tera executable files through windows firewall and several other Fixes for the client without luck.


    The funny part is that I hyped my whole guild with this classic server, and I am the only one facing this issue while they are all leveling up in the meanwhile. :dash:


    Hope the fix is soon deployed or a workaround that can be applied on our clients.


    Best regards


    Pazair

    several people made a ticket at game support, idk when they will respond but i find it very annoying to just wait with no information.

    I'm giving up on this for the moment, but my game installation can't see the servers:




    Was really looking forward to this but, sadly, it will have to wait for another day - nothing I have tried will fix this issue at my end and it looks like another of those GF connection bugs which occur from time to time. The good news is they always fix them - the bad news is it can take a while!

    I think the problem is for most of the players who created a character before the server maintenance for more channels, bcuzmy brother just loged in from my pc , same launcher just switched accounts he logged no problems, then I logged with my account and it crash again.

    Quote from Boltcranck

    I think the problem is for most of the players who created a character before the server maintenance for more channels, bcuzmy brother just loged in from my pc , same launcher just switched accounts he logged no problems, then I logged with my account and it crash again.

    I didnt created any character and didnt had logged in after and before the maintance, and its happening...