Does anyone, anywhere know what causes this infernal 'bad request' error and how to reliably fix it?
Before you start typing, I am NOT talking about 'Bad login'. That is a separate error, but just about every hit I get on Google searching for 'Unable to login: Bad request' leads me to threads where people have asked about 'Unable to login: Bad request', and responders say, "Oh, you mean 'Unable to login: Bad login'", and proceed to answer that instead. Which doesn't help, because they're offering solutions to the wrong problem.
Here is an example of what happens. I have an MCPC+ 1.6.2 test server running on port 25566 on my Gentoo Linux application server. I can connect to this perfectly every time, 100% reliable, and the server is stable and finally doing everything I want it to. (Well, until a few more mods update to 1.6, anyway.) So, I decide I'm ready to make it live. But I want to keep my test server separately, so that I can test updates and configuration changes. So I stop the test server. I make an exact copy of the entire server directory. I change the server name, server MOTD, and server port in the server.properties file, and nothing else. I start it up and try to connect to it.
"Unable to login: Bad request."
OK, I kill my client and restart it, and try again. This has worked sometimes in the past after adding or removing mods.
"Unable to login: Bad request."
OK, so, I've already saved the seed for my world. Just out of paranoia, I stop it again, wipe the world, start it back up, let it create a new world with the same seed, and try to connect.
"Unable to login: Bad request."
WTF? I start the test server on 25566 back up and go to connect to that. Instant success on the first try. I restart the "live" server again and go to try to connect to it again.
"Unable to login: Bad request."
Then suddenly, on one try, it works. But I have no idea why it was happening, or what fixed it, or when it will fail again.
I've searched high and low and I cannot find anyone who seems to actually know what causes this error, what it means, or how to reliably fix it, or even diagnose it and figure out why it's happening.
Anyone from Mojang? Help please? There has to be a way to troubleshoot this problem.
Before you start typing, I am NOT talking about 'Bad login'. That is a separate error, but just about every hit I get on Google searching for 'Unable to login: Bad request' leads me to threads where people have asked about 'Unable to login: Bad request', and responders say, "Oh, you mean 'Unable to login: Bad login'", and proceed to answer that instead. Which doesn't help, because they're offering solutions to the wrong problem.
Here is an example of what happens. I have an MCPC+ 1.6.2 test server running on port 25566 on my Gentoo Linux application server. I can connect to this perfectly every time, 100% reliable, and the server is stable and finally doing everything I want it to. (Well, until a few more mods update to 1.6, anyway.) So, I decide I'm ready to make it live. But I want to keep my test server separately, so that I can test updates and configuration changes. So I stop the test server. I make an exact copy of the entire server directory. I change the server name, server MOTD, and server port in the server.properties file, and nothing else. I start it up and try to connect to it.
"Unable to login: Bad request."
OK, I kill my client and restart it, and try again. This has worked sometimes in the past after adding or removing mods.
"Unable to login: Bad request."
OK, so, I've already saved the seed for my world. Just out of paranoia, I stop it again, wipe the world, start it back up, let it create a new world with the same seed, and try to connect.
"Unable to login: Bad request."
WTF? I start the test server on 25566 back up and go to connect to that. Instant success on the first try. I restart the "live" server again and go to try to connect to it again.
"Unable to login: Bad request."
Then suddenly, on one try, it works. But I have no idea why it was happening, or what fixed it, or when it will fail again.
I've searched high and low and I cannot find anyone who seems to actually know what causes this error, what it means, or how to reliably fix it, or even diagnose it and figure out why it's happening.
Anyone from Mojang? Help please? There has to be a way to troubleshoot this problem.