Dedicated server stopped connecting after patch 0.147.3
As per the title- I run a dedicated server through nodecraft, worked fine till the patch. Post-patch, I can't discover it in the steam browser, and can't connect to it using the IP:port combo in the 'Join by IP' option either.
After I click 'connect' in the PC client, it goes dark and I see the spinning hammer 'loading' screen for a few moments, then it kicks me back to the main menu with message 'Disconnected'.
The server doesn't log anything new during each connection attempt.
Continous development Suggested by: Ben Clark • Upvoted: 18 Sept, '22 • Comments: 20
Prior to update 0.147.3, while hosting a dedicated server off of the same PC I play on. No issues
Post update 0.147.3, unable to utilize NordVPN's split tunneling feature (enables VPN for only selected apps) and have the server on at the same time. Connection fails when attempting to connect via IP + port or via server list (server is visible on list, connection starts then fails).
Since 0.147.3 is no possible to join server on custom port (2457) via serverlist when there is more servers running at the same time on same machine. It's possible to join them only via direct IP:Port combination, only one server (on default port is accessable via server list)
Tobias Fuchsberger Merged
As of today (update 0.147.3) you are no longer to connect to a dedicated server.
It shows the loading screen "Connecting..." and an error dialog appears "Disconnected" without asking for the password beforehand.
There are multiple reports of the same problem on the Patch announcement on Twitter.
"0.147.3 Unable to connect with dedicated server" (suggested by Tobias Fuchsberger on 2021-03-02), including upvotes (1) and comments (0), was merged into this suggestion.
"Multiple dedicated servers on same machine - since 0.147.3 can't join via serverlist" (suggested by mwkaicz on 2021-03-02), including upvotes (1) and comments (0), was merged into this suggestion.
"Connection issue while using NordVPN split tunneling feature after patch 0.147.3" (suggested by Chris on 2021-03-02), including upvotes (1) and comments (0), was merged into this suggestion.
I am hosting a dedicated server on an old computer, worked well for me and my friend before 0.147.3 patch. After patch I can't join throu Server list or by external IP. At least two friends could join via server list. I can however join by computer name in IP adress field, computer name is same as displayed in server list (-name parameter).
Having the same issue here (as are many on discord) Cant connect through the internet to my own dedicated server. It looks like ports 2456/2457 aren't listening to traffic anymore. The server is still listed in public though. And connecting locally seems to work fine.
The fix is to use a different port. I was using 2456. Changed it to 2444 and now it works. For reference I did plus 1. command line to start Val used 2444. In the firewall and router opened 2444-2445.
The One True Hoff
Post 0.147.3, joining by IP and using 127.0.0.1:2456 worked. External IP and joining by name resulted in disconnects.
Friends were able to join by my external IP.
Just an update on what I did that worked to fix this issue. I was running the port on 2456, changed the bat file to 2457 and the game allowed us to join without getting disconnected. Looks like a port issue with 2456 possibly
A workaround for this problem is that if you are hosting the dedicated server on the same network as your client, you have to use the internal IP to connect to the server. i.e. if your server is on IP 192.168.1.100, you can join the server via IP 192.168.1.100:2456 (if you are using default port).
Players that connect over internet can still access the server via the public IP or the server list.
Guys a Fix that has worked for me is editing the server config file to use port 2457 rather than 2456 and it has worked a charm!! Please spread the good news! and Hope it works for you too!
I installed a CMD server on my gaming PC yesterday, and it runs perfectly. I portforward 2454:2460 to my gaming PC and I am using the following string in the BAT file to start the server; valheim_server -nographics -batchmode -name "SERVERNAME ON LIST" -port 2456 -world "GAME NAME" -password "W/E YOU LIKE BUT I USE 5 LETTERS"
Capital words are things you have to change correctly, and you don't need to spell out the seed anywhere... And no VPN installed.
May I also note, that I had some problems setting it up, but everything worked fine, as soon as I added a 5 letter password to my server. yes, I had the same problem with no listing, inability to connect properly and so on.
May I suggest you use google, keep your "question" as short as possible, so it doesn't flood you with unwanted sites? I suggest "Valheim dedicated server setup" instead of asking "how do I setup a valheim server on my own computer so me and my friends can play individually and whenever we want".
I'm hosting my server locally for friends, and none of us could connect all of yesterday after the update.
One of my friends started being able to connect today, and I just figured out that I could use the machine's local IP (& the same port).
I can't connect via my global IP, which makes me think both my laptop & the server were trying to use the global IP & port to call from after the update? This wasn't an issue before update 0.147.3
Unsure if this is the same fix for the widespread user base, especially sinc emy friends also couldn't connect yesterday, but maybe it'll help diagnose
Friend has a dedicated server. Keep getting disconnected from it every like 10min or so. It also doesn’t show up in server list for about 5min of loading as well.
This failure mode occurs regardless of VPN. I host a game in the cloud on docker, and it occurs post patch as well, just as described. There is a connecting screen, spinning glyph, then disconnected message. Server emits no connectivity information. Willing to provide client logs as requested.
connection stopped working after 0.147.3. attempted to rebuild the dedicated server, copying the world over. no dice. built a clean server with a new world, no dice.
this is running the server on ubuntu.
I think I figured this out, at least for my case. I think the issue involves this change: "Dedicated servers use directIP connection instead of SDR, solves issues with slow steam relays in some areas of the world".
Before this patch, I had to forward (only) port 2457 on my server's router in order to connect to my server, even though I specified port 2456 in the start server script. After the patch, I was unable to connect to the server using the same configuration, getting the "Connecting..." "Disconnected" message like others. But, I found that changing my port forward from 2457 to 2456 fixed the issue for me.
I know nothing about networking, but I think the game pre-patch defaulted to using Steam to connect to servers using [port]+1, and now it it connects directly using [port]+0.
tl;dr change your port forward to 2456
try connecting through the steam servers list, not in game.. its been working for me