When you used to run servers, was it with Windows 8.1?
I have struggled with the Windows 8.1 firewall for multiple applications- it seems to behave differently.
Let me know.
You need to access your router, there is conflicting documentation on the web, but it looks like the default IP for the FIOS Actiontech is 192.168.1.1
You will need the admin credentials to authenticate. Unless it's been changed, the default username will be blank. The password should be the serial number of the router. You can find it on a label on the router. (atleast, that's what I've read).
From there you can set up port forwarding. If you have more questions post some screenshots of what your router's webpage looks like- it will help others help you.
Are the players outside of your local network attempting to connect using your modem's external IP address; and not the same address that the players inside the network are using?
This is a known issue with the Minecraft Executable for a few revisions now and I've read mixed input on if the jar displays the GUI or not. Either way, you're not doing anything wrong, just wait for it to be fixed in the next patch. Or the next after that.
Enough positive feedback has been received that I think this fix should be made a thread of it's own.
This is not a fix for everything and every situation, but if your server was working, then suddenly wasn't after upgrading- GIVE THIS A TRY.
Symptoms reported:
Chunks would not render in background regardless of client's settings.
"It's not actually lag but it feels like lag" when walking or running. Player was on LAN connection which ruled out network connectivity. Most noticeable on horses or railways.
Breaking blocks has a delay to disappear. May disappear and then reappear on player's client. Reported as "Blocks are not breaking all the time and sometimes disappear. I can break a row of ten dirt but only be able to pick up seven."
"This is completely unplayable. I am so frustrated I am going outside to mow an acre of lawn."
Cause:
Upgrading the server to 1.8
Server Symptoms:
Server logged many [Server thread/WARN] messages whereas NONE were logged before upgrading to 1.8
CPU use maxed out on all cores. More specifically Java.exe (or the Javaw.exe) process taxes the CPU even with no players connected, and spikes between consuming 65% and 99% of the CPU.
Java would not correctly allocate memory, ie: Allocate a gig, only 256mb would be used.
Resolution:
Edited the script that starts the server to include the nogui option at the end of the execute Java command.
Personal Notes:
This solution took care of the CPU usage issue, chunks started rendering again, and all the "lag" disappeared.
The only thing notable is that the GUI will not load and administration commands will have to be executed from the CLI window that opens with the script. NOT LIKE THAT REALLY MATTERS given that the GUI has been broke since previous updates, lacking the resource monitor and log summary.
DO NOT DOWNGRADE YOUR SERVER IF THE WORLD HAS ALREADY CONVERTED TO 1.8. DOWNGRADING IS NEVER A GOOD IDEA.
Players will lose ALL inventory items and ALL chests will be empty.
I can not stress enough that there was no changes made to the host server other than running 1.8.
Changing the systems JRE did not make any difference.
Attempting to allocate up to 4GB of RAM did not make any difference.
There was no reason to suspect the CPU of needing an upgrade, as it worked with 1.7.10 just fine.
Version 1.8 has some pretty fatal server bugs. The exact reason is highly debated, though somewhere in the excitement claims that AMD processors are to blame have come up- which I personally don't buy the time of writing this but who knows? It feels like everyone is having the same problems regardless of hardware.
So you've isolated the issue to Network 1. That leaves the Modem, the Trendnet router, and any computers running server services as suspects.
One of those three devices are routing internal traffic for your public IP to somewhere funky instead of directly to your dedicated server or out to the internet and back in.
That's a vague answer- I know.
You seem to have a firm understanding of networking. If I were you, I'd run Wireshark on your PC and watch the packets.
Stare at it until it makes sense. Like the Matrix.
If I understand correctly you are using the MinecraftServer executable. The console being blank is a known issue that has not been fixed in recent updates.
From what you report it sounds like it's functioning.
If that's all that's going on, don't worry about it.
Unless you or someone changed the local IP schema- open a new browser session and connect to http://192.168.0.1
Leave the username blank and enter "admin" for the password.
Click on the advanced settings button/link on the left of the page.
From there you can forward port traffic to a specific IP on your lan. I would recommend giving the machine that's hosting a static IP.
I've been spending the past 6 hours trying to figure out what's wrong with my personal Minecraft Server, and only found this thread AFTER concluding that the problems my players are reporting are directly caused by updating to the server to 1.8 last week.
Symptoms reported:
Chunks would not render in background regardless of client's settings.
"It's not actually lag but it feels like lag" when walking or running. Player was on LAN connection which ruled out network connectivity. Most noticeable on horses or railways.
Breaking blocks has a delay to disappear. May disappear and then reappear on player's client. Reported as "Blocks are not breaking all the time and sometimes disappear. I can break a row of ten dirt but only be able to pick up seven."
"This is completely unplayable. I am so frustrated I am going outside to mow an acre of lawn."
Cause:
Upgrading the server to 1.8
Server Symptoms:
Server logged many [Server thread/WARN] messages whereas NONE were logged before upgrading to 1.8
CPU use maxed out on all cores. More specifically Java.exe (or the Javaw.exe) process taxes the CPU even with no players connected, and spikes between consuming 65% and 99% of the CPU.
Java would not correctly allocate memory, ie: Allocate a gig, only 256mb would be used.
Resolution:
Edited the script that starts the server to include the nogui option at the end of the execute Java command.
Personal Notes:
This solution took care of the CPU usage issue, chunks started rendering again, and all the "lag" disappeared.
The only thing notable is that the GUI will not load and administration commands will have to be executed from the CLI window that opens with the script. NOT LIKE THAT REALLY MATTERS given that the GUI has been broke since previous updates, lacking the resource monitor and log summary.
DO NOT DOWNGRADE YOUR SERVER IF THE WORLD HAS ALREADY CONVERTED TO 1.8. DOWNGRADING IS NEVER A GOOD IDEA. Players will lose ALL inventory items and ALL chests will be empty.
I can not stress enough that there was no changes made to the host server other than running 1.8. Changing the systems JRE did not make any difference. Attempting to allocate up to 4GB of RAM did not make any difference. There was no reason to suspect the CPU of needing an upgrade, as it worked with 1.7.10 just fine.
Final Thought: I hope this write up helps someone else running the Windows executable of Minecraft Server.
0
0
I have struggled with the Windows 8.1 firewall for multiple applications- it seems to behave differently.
Let me know.
0
If you don't know, PM me your IP- if you feel comfortable with that.
0
You will need the admin credentials to authenticate. Unless it's been changed, the default username will be blank. The password should be the serial number of the router. You can find it on a label on the router. (atleast, that's what I've read).
From there you can set up port forwarding. If you have more questions post some screenshots of what your router's webpage looks like- it will help others help you.
0
Your server is running, but the gui isn't reporting anything other than memory usage.
0
0
1
Enough positive feedback has been received that I think this fix should be made a thread of it's own.
This is not a fix for everything and every situation, but if your server was working, then suddenly wasn't after upgrading- GIVE THIS A TRY.
Symptoms reported:
- Chunks would not render in background regardless of client's settings.
- "It's not actually lag but it feels like lag" when walking or running. Player was on LAN connection which ruled out network connectivity. Most noticeable on horses or railways.
- Breaking blocks has a delay to disappear. May disappear and then reappear on player's client. Reported as "Blocks are not breaking all the time and sometimes disappear. I can break a row of ten dirt but only be able to pick up seven."
- "This is completely unplayable. I am so frustrated I am going outside to mow an acre of lawn."
Cause:- Upgrading the server to 1.8
Server Symptoms:- Server logged many [Server thread/WARN] messages whereas NONE were logged before upgrading to 1.8
- CPU use maxed out on all cores. More specifically Java.exe (or the Javaw.exe) process taxes the CPU even with no players connected, and spikes between consuming 65% and 99% of the CPU.
- Java would not correctly allocate memory, ie: Allocate a gig, only 256mb would be used.
Resolution:- Edited the script that starts the server to include the nogui option at the end of the execute Java command.
- Link to Minecraft Forum's tutorial for a simple server start script
Personal Notes:This solution took care of the CPU usage issue, chunks started rendering again, and all the "lag" disappeared.
The only thing notable is that the GUI will not load and administration commands will have to be executed from the CLI window that opens with the script. NOT LIKE THAT REALLY MATTERS given that the GUI has been broke since previous updates, lacking the resource monitor and log summary.
DO NOT DOWNGRADE YOUR SERVER IF THE WORLD HAS ALREADY CONVERTED TO 1.8. DOWNGRADING IS NEVER A GOOD IDEA.
Players will lose ALL inventory items and ALL chests will be empty.
I can not stress enough that there was no changes made to the host server other than running 1.8.
Changing the systems JRE did not make any difference.
Attempting to allocate up to 4GB of RAM did not make any difference.
There was no reason to suspect the CPU of needing an upgrade, as it worked with 1.7.10 just fine.
Final Thought:
Hope this helps.
0
Players outside of your local network will not be able to join.
Provide players with your external IP; the IP address that your provider has assigned to your modem.
0
Creating a startup script with the No Gui tag worked for me using the Windows executable of server 1.8- and it seems to be working for others too.
I have asked a user from another thread to test the solution on his server which runs the 1.8 jar, though no feedback yet. Give it a try and let me know how it goes.
0
One of those three devices are routing internal traffic for your public IP to somewhere funky instead of directly to your dedicated server or out to the internet and back in.
That's a vague answer- I know.
You seem to have a firm understanding of networking. If I were you, I'd run Wireshark on your PC and watch the packets.
Stare at it until it makes sense. Like the Matrix.
0
0
From what you report it sounds like it's functioning.
If that's all that's going on, don't worry about it.
0
Leave the username blank and enter "admin" for the password.
Click on the advanced settings button/link on the left of the page.
From there you can forward port traffic to a specific IP on your lan. I would recommend giving the machine that's hosting a static IP.
Source.
10
I've been spending the past 6 hours trying to figure out what's wrong with my personal Minecraft Server, and only found this thread AFTER concluding that the problems my players are reporting are directly caused by updating to the server to 1.8 last week.
Symptoms reported:
- Chunks would not render in background regardless of client's settings.
- "It's not actually lag but it feels like lag" when walking or running. Player was on LAN connection which ruled out network connectivity. Most noticeable on horses or railways.
- Breaking blocks has a delay to disappear. May disappear and then reappear on player's client. Reported as "Blocks are not breaking all the time and sometimes disappear. I can break a row of ten dirt but only be able to pick up seven."
- "This is completely unplayable. I am so frustrated I am going outside to mow an acre of lawn."
Cause:- Upgrading the server to 1.8
Server Symptoms:- Server logged many [Server thread/WARN] messages whereas NONE were logged before upgrading to 1.8
- CPU use maxed out on all cores. More specifically Java.exe (or the Javaw.exe) process taxes the CPU even with no players connected, and spikes between consuming 65% and 99% of the CPU.
- Java would not correctly allocate memory, ie: Allocate a gig, only 256mb would be used.
Resolution:- Edited the script that starts the server to include the nogui option at the end of the execute Java command.
- Link to Minecraft Forum's tutorial for a simple server start script
Personal Notes:This solution took care of the CPU usage issue, chunks started rendering again, and all the "lag" disappeared.
The only thing notable is that the GUI will not load and administration commands will have to be executed from the CLI window that opens with the script. NOT LIKE THAT REALLY MATTERS given that the GUI has been broke since previous updates, lacking the resource monitor and log summary.
DO NOT DOWNGRADE YOUR SERVER IF THE WORLD HAS ALREADY CONVERTED TO 1.8. DOWNGRADING IS NEVER A GOOD IDEA.
Players will lose ALL inventory items and ALL chests will be empty.
I can not stress enough that there was no changes made to the host server other than running 1.8.
Changing the systems JRE did not make any difference.
Attempting to allocate up to 4GB of RAM did not make any difference.
There was no reason to suspect the CPU of needing an upgrade, as it worked with 1.7.10 just fine.
Final Thought:
I hope this write up helps someone else running the Windows executable of Minecraft Server.