Can't stay in game for more than 2 minutes, loses connection to server

I log into the game without problem, select either solo or open play and get into my asp explorer. Invariably within 2 minutes I'm thrown out of game with 'Red Krait' error- lost connection to authentication server. I'm not having any internet problems currently and can play any other game without dc'ing; any help/ideas?
 
Hmmmm...slightly different problem for me - but transferring cargo between ship and carrier has just stopped working entirely...

...Hamsters I guess!
 
Is this in Legacy 3.8?

I started getting Scarlet Krait errors in legacy between 2100 and 2200 last night, and now I can't stay in game for more than a minute without the error.
Before that I was on a planet's surface in the srv for over an hour without issues, the errors started after I got in my ship to SC.

Scarlet Krait is apparently a connection error associated with MTU size.
I've never had this error repeat before but I lowered the MTU anyway but it hasn't made any difference.

I contributed to this ticket which has now been closed, but lots of other tickets logged (and closed) and folk on reddit saying they're having issues since the Legacy maintenance yesterday.
https://issues.frontierstore.net/issue-detail/63067

Live 4.0 is fine for me.
 
Last edited:
At least 12 reported tickets with this issue have been closed with, currently, four awaiting confirmation.
Not sure what this says about FD's commitment to support in apparently turning these reports into each reporter's personal problem (or players' abilities in finding out what others are experiencing).
 
I hope I don't have to go through all the hassle of writing a ticket and then going through the problem with someone from FDEV. I assume, as they're aware of the problem and working on a fix, that I just need to hold tight and wait. I would be profoundly grateful for any news on this issue.
 
I have the same problem. Scarlet Krait error.
My PS Plus membership just expired yesterday, even after paying for the membership immediately, the problem persists, I thought it was related, but as I see, I'm not alone.
 
... though ofc there is no point in voting or confirming as they're aware and working on it. I guess if you like placebos then go ahead :D
 
Hmmmm...slightly different problem for me - but transferring cargo between ship and carrier has just stopped working entirely...

...Hamsters I guess!
try moving small numbers. one commodity i was able to move after few relogs (multiple times to menu as well as to desktop) but the last one i was able to move only two at the time.
 
... though ofc there is no point in voting or confirming as they're aware and working on it. I guess if you like placebos then go ahead :D
Absolutely. The voting procedure was set up long after the T****** post. The Issues reporting system is so inflexible.
Irony - completely lost on forums.
 
7 pages of reports on https://issues.frontierstore.net/issue-detail/63067 now including a request for people to switch logging on at the main menu screen. Then they lose me with instructions for finding AppConfig.xml and tinkering with it; as I use a PC and as I do not speak techno gibberish I can't do as they say. Hopefully others can.
It's just instructions for turning on detailed logging so they have more info to look at. Enough players will do it even if you don't.
 
I just logged into Legacy on PC & the servers seem stable (2am game time).

_________________

ETA just finished the session (about 4hrs) with only one server issue, a Blue Cobra (could not connect to the adjudication server) in that time.

So maybe it's fixed (thank you if that's the case), maybe it's because the weather has been calmer in the UK today, or maybe the servers were fine all the time but overwhelmed by player traffic & when it's quiet they still do their jobs as before (ie whatever extra security was applied in the patch slowed down response times & stuff started timing out) & that problems will return once player traffic picks up during the day (in Europe).

Note that at time of writing the Thursday morning server reset has not yet happened.
 
Last edited:
Back
Top Bottom