-
-
Notifications
You must be signed in to change notification settings - Fork 119
Top 10 Reason your Server is not working and how to fix
After helping over 600 people setup there servers, here is the top 10 reasons their servers did not work.
TL:DR
-
You do not have enough system resources to run the game and a server. Min requirements are 2CPU and 4GB RAM. If you happen to get the game to run... it will only last a few moments.
-
Your server password matches a name in your public display name. Your server password must be UNIQUE.
-
You did not install the game with root or a proper sudoer
-
You are installing from a Ubuntu ISO and not from a Cloud Service provider. Additional steps are required. Google How to install steamcmd on Ubuntu 20.04 and How to install steam on Ubuntu 20.04 before launching the script. We did not add this because most of the users are installing in a Cloud environment.
-
Your firewall rules are not setup correctly. Read the WIKI on how to complete this.
1. Password was less that 5 characters or password match public display name; must be unique and not special characters ( ! @ # $ %..etc)
Will not work:
./valheim_server.x86_64 -name "My Awesome Server" -port 2456 -nographics -batchmode -world AwesomeServer -password awesomeserver -public 1 -savedir "/home/steam/.config/unity3d/IronGate/Valheim/WorldNameOne"
./valheim_server.x86_64 -name "My Awesome Server" -port 2456 -nographics -batchmode -world AwesomeServer -password 1234 -public 1 -savedir "/home/steam/.config/unity3d/IronGate/Valheim/WorldNameOne"
./valheim_server.x86_64 -name "My Awesome Server" -port 2456 -nographics -batchmode -world AwesomeServer -password 123 -public 1 -savedir "/home/steam/.config/unity3d/IronGate/Valheim/WorldNameOne"
./valheim_server.x86_64 -name "My Awesome Server" -port 2456 -nographics -batchmode -world AwesomeServer -password 12 -public 1 -savedir "/home/steam/.config/unity3d/IronGate/Valheim/WorldNameOne"
./valheim_server.x86_64 -name "My Awesome Server" -port 2456 -nographics -batchmode -world AwesomeServer -password 1 -public 1 -savedir "/home/steam/.config/unity3d/IronGate/Valheim/WorldNameOne"
./valheim_server.x86_64 -name "My Awesome Server" -port 2456 -nographics -batchmode -world AwesomeServer -password 1 -public 1 -savedir "/home/steam/.config/unity3d/IronGate/Valheim/WorldNameOne"
./valheim_server.x86_64 -name "My Awesome Server" -port 2456 -nographics -batchmode -world AwesomeServer -password (NO FREAKING PASSWORD!!!!) -public 1 -savedir "/home/steam/.config/unity3d/IronGate/Valheim/WorldNameOne"
Will work
./valheim_server.x86_64 -name "Zero's Testing Server One" -port "2456" -nographics -batchmode -world "WorldNameOne" -password "HappyScripts" -public "1" -savedir "/home/steam/.config/unity3d/IronGate/Valheim/WorldNameOne"
./valheim_server.x86_64 -name "My Awesome Server" -port 2456 -nographics -batchmode -world AweWorldServer -password SuperDuperPass -public 1If you made a mistake with this, edit the start_valheim.sh file, save it and restart Valheim services.
vi /home/steam/valheimserver/start_valheim.shStrange server occurrences, things not saving, things becoming non-intractable, etc. are typically due to the server not being able to handle everything you're asking it to. This can be because of too large of a world, too many players at once, etc.
Solve this by upgrading/resizing your server.
Will not work:
1CPU 1GB RAM
1CPU 2GB RAM
1CPU 10000TB RAM
Will work:
2CPU+ 4GB+You can see a full list of server spec recommendations by clicking here
----Configure Networking
* Once Ubuntu is up and ready, select it, and click the Security tab.
----Networking tab, add firewall rule to allow ports 2456-2458. (this will be all three ports)
* Open port 2456-2458 to enable Valheim clients access to the server.
* Application: (Custom)
* Protocol: TCP/UDP
* Port Range: 2456-2458
----Also ensure SSH is added as well.
* Application: SSH
* Protocol: TCP (default)
* Port Range: 22 (default)4. Google Cloud networking not setup correctly. Not tagging the VM resources with 2456, 2457, 2458 TCP/UDP ingress and egress
I was bored so I did a non-listed tut for you. View Tutorial on YouTube
You're welcome!
* After creating your Azure VM, shutdown it down HARDCORE, just softly.
* Go to "All resources"
* Click the network card that is assigned to your server.
* Click on "IP Addresses"
* Enable "Public IP address"
* Click on configuration of the public ip address.
* Change the public ip address to static. IP address will be automatically assigned
* Save settings and go back to All resources
* Click on the network security group that is bound to the network card
* Click on inbound security rules
* Add: Any/2456, Any/2457, Any/2458
* Click on outbound security rules
* Add: Any/2456, Any/2457, Any/2458
* Start your vmSee DigitalOcean walkthrough here
If this doesnt work, just NUKE IT!
DigitalOcean private IP and routing fix for Valheim: Not really needed anymore but if you run into some crazy networking issues... just blow it away
edit 50-cloud-init.yaml
vi /etc/netplan/50-cloud-init.yaml
remove private IP address on eth0 (might be 10.10.something - do not remove your public IP the same one you use to SSH into the server or access it)
netplan apply
reboot7. Valheim Server not showing up in Steam Servers or Valheim Server: This is hit or miss. Do manual connections, it will work.
* Open Steam
* Right click Valheim game logo
* Select properties
* Type in the launch options
* +connect IPADDRESS:PORT
* press X
* Start Valheim
* Select viking toon to play
* Press startThis error happens when the game client and server have mismatched versions.
- Update the game client (via steam)
- Update the server (restart the server) - Visit this link for details on How To Update Your Valheim Server
So really it comes down to.... Misconfigurations of the network security policy of your hosting company. I highly recommend getting SSH to work first. Meaning if you can SSH into your Ubuntu virtual machine, then your networking is configured successfully for SSH. Which means, all you have to do is copy the rules for SSH and add ports: 2456,2457,2458 TCP/UDP.
Also make sure you set your passwords correctly. Do not have ' " @ ! within your passwords.... it will break the script. Make sure they are over 5 chars and not the same as your Public Display Name... the server will not start.
Hope this helps!
Add Windows Section Add Linux Section