Try changing your Server Property Online Mode to false and restart the server.
I tried that and it then works fine but it then of course it doesnât use the userâs skins and saves their inventories separately from users who logged in while online-mode was set to true
Authentication doesnât happen on your Minecraft server. The process goes like this:
- Authenticate at the Mojang (creators of Minecraft) server with username and password
- Retrieve a session id
- Contact the server you want to play on and send your username and session id (for verification that you own tat name)
- Send every 5 minutes a keep-alive request to the Mojang server so that the id does not timeout
Authentication is the sending of your username and password to Mojang servers at step #1. Provided all goes well, they return an authentication token back to your client (on your desktop) that verifies this.
Your client (desktop) then contacts your server (mineos) and says âI am this playerâlet me log inâ. The server checks the server.properties value online-mode and if true, says âyeah, well show me your auth tokenâ. Your client provides the token, and you are logged in.
If the online-mode is false, your client contacts your server and says âI am this playerâlet me log inâ and the server says âsure, I believe itâ and thatâs that.
In receiving the error after trying to connect to your server (mineos), this is aligned with the idea that the Minecraft jar (the server) has connectivity to your desktop. If you want to remove the firewall, you can, though I doubt it would fix the issue.
At any rate, in the past few hours there have been a few tweets with your same symptoms:
Itâs not surprising that for intermittent issues (read: a problem a few people are having, so they assume âall is wellâ and âthe problem must be on your endâ), but for these peopleâlike youâit is less likely that non-existent changes to your own firewall config is going to work one moment, and stop the next.
Furthermore, these people are not likely using MineOS, which corroborates the idea itâs authentication-server based, rather than your own config/server.
ahhh okay I see, thanks for the explanation. so i guess all i can do is just wait till mojang does something about it then?
I remember having trouble with this on mineOS.
The problem was that the serverclock was wrong and that somehow affected the authentification. I think the server says to the client âI donât belive you! That authfication token is to old.â
The resulution was to set the clock to current time.
wow do I feel dumb, this was what was wrong, the system thought it was the year 2022, guess i forgot to check the time settings in the BIOS, works fine now. Thanks guys!
I am happy to help.
Ah, thatâs an amazing catchâŚthank you for letting us know about this!
The fact that you can actually help and get appreciation for that is very rewarding and good for your self esteem. Thank you.
My server clock was only off by five hours, and it still wonât connect.
I guess it thought I was at GMT 00:00 time or something. Iâm actually
at GMT +05:00. Regardless⌠Iâm still pretty stuck. Help?
Just to make sure you have it as perfect as it can be, here is the official Turnkey page on configuring the timezone (and recommends keeping your hardware clock at UTC!)
ahhhh, but now it wonât connect to the internet! (It wonât download update packages). I typed in apt-get update, and it sat for a bit and spat out a bunch of "error: could not connect"s and stuff.
Hereâs what I got after trying your advice:
Installing package(s) with command apt-get -y --force-yes -f install webmin-time âŚ
Reading package listsâŚ
Building dependency treeâŚ
Reading state informationâŚ
The following NEW packages will be installed:
webmin-time
0 upgraded, 1 newly installed, 0 to remove and 18 not upgraded.
Need to get 67.4 kB of archives.
After this operation, 92.2 kB of additional disk space will be used.
Err http://archive.turnkeylinux.org/debian/ wheezy/main webmin-time amd64 1.630-turnkey+0
Could not resolve âarchive.turnkeylinux.orgâ
Failed to fetch http://archive.turnkeylinux.org/debian/pool/wheezy/main/w/webmin-time/webmin-time_1.630-turnkey+0_amd64.deb Could not resolve âarchive.turnkeylinux.orgâ
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
⌠install failed!
EDIT: installed it by downloading the .deb and using the package upload feature.
Based on that error, I think we can safely deduce itâs a connectivity issue at a much higher level. Your other problem with authentication server is down seems to be explained perfectly by lack of connectivity.
I suspect youâll find pings are also not working, so that is what weâd need to address.
Are you connected wirelessly or by wires?
When you boot up the server (and you can reboot it if you need to), does the prompt at the start say youâve been issued an IP address?
(side note, donât worry about the timezone now anymore, that seems to be a non-issue here. If you are interested in setting the timezone all the same, this blue screen from boot-up is a better alternative than the apt-get methodâitâs described at the bottom of the linked page).
Um, let me check the ping⌠thing. (sorry, it rhymed, couldnât help it)
The server is wired into the router.
I told the server to take a specific address. When it boots up, at the blue configuration console screen, it says I have an IP address that is 192.168.1.xxx, and I can fill in those xâs for you if you need them. I told it to take the address at 192.168.1.xxx, though, so it makes sense it would take that one.
Do I need to change this in order to get my server working? I thought that was sort of against the whole concept of port forwarding.
Also, I was able to connect to it with the webmin and WebUI.
When you have addresses with 192.x.x.x, theyâre âprivateâ, but they need not be secret; thereâs no harm in showing them.
With the loss/lack of connectivity, but youâre telling me youâre using a static IP, here is my recommendation:
- Turn off static IP. Let your router allocate the IP address it wants. Yes, I know youâd want it static in the end, but right now, setting up the static might be the reason for lack of operability.
- Test your pinging after youâre using DHCP
- Explore if your router has static routes or âstatic dhcpââit is the preferred equivalent of you getting an IP address issued dynamically but with the added bonus that the address never changes, and therefore will be suitable when you want to make your server accessible to the world.
All of this can be done from the blue screen that pops up from restarting your host system. Restart from there as well is probably the easiest way.
Okay, Iâll try that. Thisâll probably be all for tonight; I have homework for classes tomorrow, so I need to get to that. Iâll check back tomorrow after I do the stuff youâve just told me, and post the results here.
How do I test the ping?
I skipped the ping step and went straight to Minecraft, and it worked, at least, locally. I was not only able to connect to the server without the âauthentication errorsâ but I was also able to resume playing as the character I had been playing as before I switched to offline mode.
Time to go! See you on the flipside.