FD please fix your bloody servers

Some guys have posted that trying to enter SC in a carrier overcrowded system could cause this issue. This is exactly describing my situation as I try to get out of the Dweller's base in Wyrd and my selected system was covered by the planet.

So I'll try to high-wake out once back in the game. I have to admit that I haven't known of this issue/bug yet so I have to apologize to FD for having blamed their server performance.
It's really not a problem that you blamed the servers. It's pretty much irrelevant from our point of view what's causing it. Fdev know about it and it's caused by an issue their side (servers or otherwise) so it's definitely their fault. And definitely not yours.

Obviously, you'll get told "I don't have any problems, must be you!" because some people have that overwhelming urge to defend the indefensible and demonstrate their superior position all at the same time.

Thankfully, despite being really slow to fix stuff right now due to a global Pandemic and also trying to get an expansion out the door as priority, fdev don't tend to work on that "I'm fine, must be you" basis and I'm hoping this will be fixed after Odyssey is launched.

Might even be with the launch. Fdev tend to do massive change log, wall of text patch notes on major releases. Let's hope this one is caught then. The work around you suggested does work but this is an issue that does spoil the experience for many players.

Unless you live in Anchorage, it seems.
 
And what about your ISP? Or Fdev's cloud provider? Or the network segments that neither you or FDev control? But, if you want to blame the least likely culprits, go right ahead, just be aware that all sorts of traffic records have been set in the last week or so..

Discord is full of people with connection issues over the past few days. I've seen it myself with the "404" launcher error.

Yeah, there's a real problem here.
 
I have no connection problems even in systems with high FC numbers.
By the way the servers are not owned by Frontier.
Problem is not numbers, problem is their jump. Once I posted cheap trit to inara, next 2 hours I could not use cruise as each 5 mins new carrier was incoming.
 
So you are right next to the imaginary servers, I am over 13,500 klms from said imaginary servers and also 1,200klms from the nearest major city and I have no problems but it's all because of the imaginary servers right next to you?
I don't think it matters where you are...although where you are may add extra latency.

The reason people can point the finger at FD is that the issue can be replicated.
The times when I get disconnect errors are always in systems that have a high number of cmdrs and/or FCs...usually CGs .
The last Thargoid CG was the worst I've seen it. At peak times a 20min session might go like this:

1. Login to open, docked at station. Instant.
2. Leave station, enter SC. Stuck in tunnel. After 4 minutes ED disconnected me.
3. Login to open try to enter SC, takes 2min of tunnel before I enter SC.
4. See threat lvl 5 thargoid POI, drop in, see it's scouts and not a cyclops, enter SC. Stuck in tunnel for 4 mins before disconnect.
5. Login to open. Instant. Enter SC. Tunnel for 4mins. Disconnect.
6. Login to open. Instant. Enter SC. Tunnel for 4mins. Disconnect.
7. Login to open. Instant. Enter SC. Takes 2+min in the tunnel.
8. Find threat lvl 5. Kill cyclops. Enter SC. Tunnel for 4mins, Disconnect again.
9. Refuse to play in Solo, so give up and go walk the dog.

Had the exact same thing last night when doing rescue missions at the thargoid attacked stations, where a lot of players currently are.
The error message says something about not being able to connect to the authentication server.

When I do finally get into SC there are always loads of humans flying around.
Do exactly the same, out of peak hours, when there are not many humans around and there are no disconnects and every transition to and from SC is instant.

Only ED has issues and other games/software work 100% ok while ED keeps disconnecting.
Everything certainly points to it being an ED FD issue.
 
Yeah the servers have had a rough couple of weeks. I've had more issues with both my steam and epic alt accounts, than I did in the entire month prior to the last week or so. And Frontier may not own the servers, but they rent them from a cloud provider and Frontier most likely have a min/max servers setting for budgeting reasons. Seems like on busy weekend days and Holidays the servers are stretched a bit thin, ie more resources are needed.
 
Some guys have posted that trying to enter SC in a carrier overcrowded system could cause this issue. This is exactly describing my situation as I try to get out of the Dweller's base in Wyrd and my selected system was covered by the planet.

So I'll try to high-wake out once back in the game. I have to admit that I haven't known of this issue/bug yet so I have to apologize to FD for having blamed their server performance.
This is where I got stuck also yesterday . 3 orange sidey's in a row finished my session.
My next jump star was obscured by a planet so I wanted to go SC.
Did you also wanted to go to Palin's base after Wyrd?!
 
Three blue tunnels in a row, ending in orange Sidewinders and mauve Adders. Good luck, thank you and good night.

Do you have a way to test another connection to the internet? i.e. are you able to tether to your phone or some other source? I see these posts, but never experience the issues. Just throwing out some troubleshooting ideas.
 
Discord is full of people with connection issues over the past few days. I've seen it myself with the "404" launcher error.

Yeah, there's a real problem here.

I never said there wasn't an issue. And yet many of us haven't seen this issue. I'll ask again, if this is an FDev problem, shouldn't we all suffer?
 
I'll ask again, if this is an FDev problem, shouldn't we all suffer?
The only true, logically factual reply to that question can be "no" because there exists at least one historic event where not everyone was impacted exactly equally by an issue with a product.

The carrier issue doesn't affect everyone exactly the same. Drawing the conclusion that it therefore cannot be an issue for fdev to remedy is false. Even suggesting that there's a possibility that it's not FDev's responsibility and is collectively the fault of those it affects is stretching probability a long way.

It's also extremely unhelpful. Particularly given it's not accompanied with any proof of how the end user is at fault nor how the end user can resolve it without FDev's help. Because it's a problem fdev are investigating without revealing the solution, as yet.

My guess is it'll be a problem fdev fix, not the community, but we'll leave that one open to Schrodinger.
 
Last edited:
I never said there wasn't an issue. And yet many of us haven't seen this issue. I'll ask again, if this is an FDev problem, shouldn't we all suffer?
No. If that were the case identifying bugs in any software would be as easy as pie. Things like instancing and block lists instantly make things different per cmdr.
The fact the issues people are seeing a repeatedly replicable is a very good indication it's FDs issue.
 
No. If that were the case identifying bugs in any software would be as easy as pie. Things like instancing and block lists instantly make things different per cmdr.
The fact the issues people are seeing a repeatedly replicable is a very good indication it's FDs issue.

They are just as attributable to FDev's cloud provider, which would actually go further to explaining why some locations seem more affected than others.
 
I never said there wasn't an issue. And yet many of us haven't seen this issue. I'll ask again, if this is an FDev problem, shouldn't we all suffer?

As someone who's done technical support for a living, the answer is clearly NO. That's...not how software or the Internet works. Everyone doesn't have to suffer a problem, for there to be a real actual problem.
 
They are just as attributable to FDev's cloud provider, which would actually go further to explaining why some locations seem more affected than others.
Given the stock answer from support is it's carrier related, I find it tough to believe that Amazon is somehow at fault for how their servers run.

Amazon aren't responsible for the data being sent.

Still, we don't know for sure either way because we've not diagnosed the problem. This argument is really a bit directionless and definitely doesn't solve the issue nor even factually refute the op's claim that fdev are at fault (which is, I'm guessing, the entire driving force behind your argument).

Who cares, though? You're fortunate to have never seen this error, others less so and fdev have admitted it's an issue they're investigating. That's all we can factually agree on.
 
Last edited:
I had problems like this too awhile ago. what i had to do to stabilize my connection was change the MTU settings.
I think FDev changed the package sizes sometime ago to a weird size and alot of providers cant cope with that size without having to change settings.
Is that FDevs fault? I dont care.
Shld FDev make sure its game is compatible with alot of internet providers? Yes
 
I had problems like this too awhile ago. what i had to do to stabilize my connection was change the MTU settings.
I think FDev changed the package sizes sometime ago to a weird size and alot of providers cant cope with that size without having to change settings.
Is that FDevs fault? I dont care.
Shld FDev make sure its game is compatible with alot of internet providers? Yes
Might want to share your knowledge with fdev so they can fix it then. They've not got your memo yet it seems ;)
 
Back
Top Bottom