![]() So I noticed that on my ubuntu server, the valheim server is now listening on BOTH 24 when I supply the -port 2456 argument to start_server.sh. I've even completely reinstalled the server client on my server to see if it's something steamcmd doesn't wanna update, however this is a complete shot in the dark so we'll see. * Dedicated servers use directIP connection instead of SDR, solves issues with slow steam relays in some areas of the world Good i'm not the only one at least, it's really frustrating. My guess is that this is related to the changes in connection modes, but I can't know for sure: 19:20:36: Got problem 5003:Connection dropped ![]() 19:20:36: Got status changed msg k_ESteamNetworkingConnectionState_ProblemDetectedLocally The server log only reports the following: Even though he doesn't seem to have any issues himself, we can't effectively play together at all. I was able to play fine while I was the only player, but a friend joined after work and I keep getting booted out (black screen, "Disconnected") within minutes as long as he's playing. Originally posted by Shadow:I never had any connection problems with my dedicated server (I host it on my own computer) until today's update. I'm not sure if this fix will work for everyone but it did for me, only sad part is that you have to rewrite the server script (if you weren't smart enough to copy it to another dir before deleting it) Then i ran the steamcmd command again to install it back on my system. I've fixed the issue on my system at least by completely deleting the server client from the system, only saving the world information of course. ![]() If anyone has similar issues or a fix to this, I'd be glad to hear your thoughts out on this issue. I've tried completely removing the public flag, no change. I've tried to fix this issue by switching "-public 1" to "-public 0" in the flags of the little bash script (it's running on Ubuntu Server), but no change. Other users of the server report the same issue so it's by no means a networking problem on their end. ![]() When I join through ip i get to a "connecting" screen, which holds for a few seconds before i get booted back into disconnected. It's been running now for a few days on end with no issues but recently after this new update i can't log in. Seemingly after this past update I've been getting serious issues with my dedicated server. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |