My MC server setup has been working perfectly up until the end of Feb. The server version was 1.3 and I am running it on a Linux box. I could login, log out, op, deop, etc.. with no issues and little load. Unfortunately, I had to drop Minecraft for a month while I did a work related project (gotta eat, y'know...)
Now, I decide to fire up my MC server via SSH (I'm not currently at home) and my MC client (on my laptop) and all heck has broken loose. The server is unreachable, the client has been updated and now also doesn't work and the whole thing has blown up in my face. I'm pretty much begging for assistance in getting this up and running, even if this means I did lose my 1.3 map. The web-based MC application causes my laptop to freak out but the client (showing version 1.4) works properly in single player mode, not multiplayer.)
I do not use standard port forwarding at my site. I have a NAT router that forwards SSH to this machine, then I use an SSH port forward to bring the MCserver's port 25565 to my machine's port 25565. I have to connect via localhost.
Please keep in mind that prior to 1.4, my server worked perfectly using this configuration. Granted it is oddball, but I want to make sure that I'm the only person that can connect to my minecraft server.
I downloaded the mc server archive to my Linux server and extracted the 1.4 version of minecraft_server.jar and was able to get it running however my client can not connect. When I attempt a web-based connection using the MC launcher, I get "connecting.... " in the launcher, but the "Kicking 192.168.0.2. You need to login" in the server's console. (as shown below.) At this point, the client will go black-screen and abnormally exits.
mcserver@littleblackbox:~$ java -Xms512M -Xmx512M -cp minecraft-server.jar com.mojang.minecraft.server.MinecraftServer
23:53:32 Setting up
23:53:32 Loading level
23:53:34 Now accepting input on 25565
23:53:36 Level saved! Load: 0/20
23:53:58 /192.168.0.2 connected
23:54:03 Kicking /192.168.0.2: You need to log in!
23:54:03 /192.168.0.2 disconnected
23:54:36 Level saved! Load: 0/20
23:55:36 Level saved! Load: 0/20
23:56:36 Level saved! Load: 0/20
23:57:36 Level saved! Load: 0/20
23:58:36 Level saved! Load: 0/20
23:59:36 Level saved! Load: 0/20
00:00:36 Level saved! Load: 0/20
00:00:58 /192.168.0.2 connected
00:01:03 Kicking /192.168.0.2: You need to log in!
00:01:03 /192.168.0.2 disconnected
Trying it via minecraft.net/play.jsp?ip=127.0.0.1?port=25565 produces an error "The name wasn't verified by minecraft.net" on both the server and client as shown below:
00:03:41 /192.168.0.2 connected
00:03:41 Kicking /192.168.0.2: The name wasn't verified by minecraft.net!
00:03:41 /192.168.0.2 disconnected
Another thing that is odd is that I have public set to false and server-ip set to blank (no entry) based on research performed here. It is safe to assume that all other variables in the server.properties are stock and have not been tampered with. There are no mods/addons/expansions, this is all (even the client) stock Minecraft. I have tried setting verify-names=false, but that did not change the name verification error so it has been reset to "true".
Please help. If you need more information, I will do my best to answer your questions.
If you encounter such an error like this, download the minecraft_server.jar directly from http://www.minecraft.net/download.jsp and do not use any other links to download minecraft_server.jar. I don't remember where I got the new server package from (I know it was from minecraft.net, just don't remember the link) but that version clearly was not ready for release/testing.
My client version is 1.4_01 (auto-updated via the Launcher)
My server version is 1.4_01 (downloaded from minecraft.net at above link)
When you download and run the minecraft_server.jar file for the first time, it will automatically perform the conversion of the existing world to the new format. Once it's complete, your MC server is ready to rock.
Now, I decide to fire up my MC server via SSH (I'm not currently at home) and my MC client (on my laptop) and all heck has broken loose. The server is unreachable, the client has been updated and now also doesn't work and the whole thing has blown up in my face. I'm pretty much begging for assistance in getting this up and running, even if this means I did lose my 1.3 map. The web-based MC application causes my laptop to freak out but the client (showing version 1.4) works properly in single player mode, not multiplayer.)
I do not use standard port forwarding at my site. I have a NAT router that forwards SSH to this machine, then I use an SSH port forward to bring the MCserver's port 25565 to my machine's port 25565. I have to connect via localhost.
Please keep in mind that prior to 1.4, my server worked perfectly using this configuration. Granted it is oddball, but I want to make sure that I'm the only person that can connect to my minecraft server.
I downloaded the mc server archive to my Linux server and extracted the 1.4 version of minecraft_server.jar and was able to get it running however my client can not connect. When I attempt a web-based connection using the MC launcher, I get "connecting.... " in the launcher, but the "Kicking 192.168.0.2. You need to login" in the server's console. (as shown below.) At this point, the client will go black-screen and abnormally exits.
mcserver@littleblackbox:~$ java -Xms512M -Xmx512M -cp minecraft-server.jar com.mojang.minecraft.server.MinecraftServer
23:53:32 Setting up
23:53:32 Loading level
23:53:34 Now accepting input on 25565
23:53:36 Level saved! Load: 0/20
23:53:58 /192.168.0.2 connected
23:54:03 Kicking /192.168.0.2: You need to log in!
23:54:03 /192.168.0.2 disconnected
23:54:36 Level saved! Load: 0/20
23:55:36 Level saved! Load: 0/20
23:56:36 Level saved! Load: 0/20
23:57:36 Level saved! Load: 0/20
23:58:36 Level saved! Load: 0/20
23:59:36 Level saved! Load: 0/20
00:00:36 Level saved! Load: 0/20
00:00:58 /192.168.0.2 connected
00:01:03 Kicking /192.168.0.2: You need to log in!
00:01:03 /192.168.0.2 disconnected
Trying it via minecraft.net/play.jsp?ip=127.0.0.1?port=25565 produces an error "The name wasn't verified by minecraft.net" on both the server and client as shown below:
00:03:41 /192.168.0.2 connected
00:03:41 Kicking /192.168.0.2: The name wasn't verified by minecraft.net!
00:03:41 /192.168.0.2 disconnected
Another thing that is odd is that I have public set to false and server-ip set to blank (no entry) based on research performed here. It is safe to assume that all other variables in the server.properties are stock and have not been tampered with. There are no mods/addons/expansions, this is all (even the client) stock Minecraft. I have tried setting verify-names=false, but that did not change the name verification error so it has been reset to "true".
Please help. If you need more information, I will do my best to answer your questions.
If you encounter such an error like this, download the minecraft_server.jar directly from http://www.minecraft.net/download.jsp and do not use any other links to download minecraft_server.jar. I don't remember where I got the new server package from (I know it was from minecraft.net, just don't remember the link) but that version clearly was not ready for release/testing.
My client version is 1.4_01 (auto-updated via the Launcher)
My server version is 1.4_01 (downloaded from minecraft.net at above link)
When you download and run the minecraft_server.jar file for the first time, it will automatically perform the conversion of the existing world to the new format. Once it's complete, your MC server is ready to rock.