Error occurred while contacting login servers, are they down?

I have had the above error twice now. Players received that message when they tried to login and it did not allow them to join until I restarted the proxy. Login servers were not actually down at the time as I could join other servers. It seems to just randomly occur(players can join fine most of the time). I have made sure my firewall rules are correct(port 80 and 443 are allowed) so I do not believe it is a network/firewall issue.

I was getting this too. Unable to login to my server with the same error. Tried at least a dozen different times over the past 30 minutes. Tried one last time, got this error, restarted proxy and was instantly able to log in and out repeatedly without issue. That doesn't seem like a mojang issue despite the error text.

Which part of Mojang's API returning an HTTP error 503 "Service Unavailable: Back-end server is at capacity" is BungeeCord's fault? Mojang's servers are telling BungeeCord that they are currently at capacity!

Which part of Mojang's API returning an HTTP error 503 "Service Unavailable: Back-end server is at capacity" is BungeeCord's fault? Mojang's servers are telling BungeeCord that they are currently at capacity!

Click to expand...

I've read what you have said and I understand that. The thing I am stating is a simple restart fixed the problem. The servers were not at capacity the one Bungeecord was connecting to was. I don't know how Bungeecord or Mojang server shit works but by the looks of things whatever Bungeecord was connecting to was saying it was down. After a Bungeecord restart it could connect again.

So my theory is that Bungeecord was connecting to a certain IP and when that went down on Mojangs bungeecord kept trying to connect to that IP when it changed.

Its not Bungeecord's fault that the server went down in the first place but it seemed to be connecting to something and erroring even though essentially it was up.

AdministratorDeveloper

I've read what you have said and I understand that. The thing I am stating is a simple restart fixed the problem. The servers were not at capacity the one Bungeecord was connecting to was. I don't know how Bungeecord or Mojang server shit works but by the looks of things whatever Bungeecord was connecting to was saying it was down. After a Bungeecord restart it could connect again.

So my theory is that Bungeecord was connecting to a certain IP and when that went down on Mojangs bungeecord kept trying to connect to that IP when it changed.

Its not Bungeecord's fault that the server went down in the first place but it seemed to be connecting to something and erroring even though essentially it was up.

Click to expand...

Mojang runs many different servers. If they are "at capacity" not every single request is going to fail, just the ones which bring it over capacity.

Mojang runs many different servers. If they are "at capacity" not every single request is going to fail, just the ones which bring it over capacity.

Click to expand...

Okay but all requests were failing so I assumed it would be down. But after restart everything works fine again. So what it seemed like was Bungeecord was trying to connect to down servers when others were up. Couldn't you check if that server was over capacity and try another instead?

You are wrong sir... just had this situation 10 minutes ago... My network keep saying: error occurred while contacting login servers. Are they down
Mineplex heep saying the same... Then after few minutes I noticed mineplex is up but my server is still down for premium users...

I restarted my bunge 4 minutes ago and its fine now... So as Spurlex said... Bungee keeps some informations about auth server that went down - untill you restart bungee you won't get online as premium.

While it was a huge necro.
I did have to restart my bungee 2 times today for players to be allowed to join.
And I noticed a lot of other servers were having the same issue, including Mineplex. (Early morning US today)

I was just assuming it had something to do with the upcoming name change crap.

I can vouch for this. I saw that login servers were down earlier for all servers. Later, I could access pretty much all other servers, but I kept getting that same error message constantly for my own server. It was fixed with a restart of bungee.