chrisanton18

Yes indeed, all my buddies were able to connect last night with the new server name and have stopped and started the container a few times with no issues or delay on it appearing.

Yes, the picture on the post outlining how to delete the original UDP Range and add a new one if I used a different range was extremely helpful. As far as I can tell it is indeed a server name issue. I stopped the container and re-edited it back to the original name I had and the issue returned (without making any port changes, just the server name), waited about an hour or 2 and server still didn't know up via public IP. Soon as I change it to no longer use what I believe to be the "culprit" word. Server shows up and my friends can connect. And I have indeed been using a password with at least 6 characters.

To answer your question first, yes I'm able to join by LAN and I've lost count of the amount of times I rebooted my router. I only host on one at a time, not both at the same time and I was trying different port ranges so there would be no conflict. The port forwarding I was doing (again not at the same time or from multiple devices on the same ports) were the following: 2456-2458 2466-2468 But I think I figured out the problem and it's kind of embarrassing. At least when I change this it works perfectly fine. I decided to just start a brand new Docker container without importing our old world/name/password. Just created a new one with a new name, password and default port ranges. Within a minute Public IP and port was showing up in steams server list and I was able to also search it up in Valheim itself. Had a friend connect and was able to confirm. The embarrassing part was our "server name"... I guess it contains what Steam would consider a not so PG word. Every time I would use our old Server name running from the docker container I Could wait and wait and nothing shows up. The moment I changed the server name... well there it was. So I'm all good now. I can start and start the container and even re-set it up again within minutes and everyone can connect. Never encountered this when I was running the server straight from my Windows PC (non Docker). I'm assuming the way the Valheim Dedicated Server script runs from a desktop environment versus a docker container bypasses any type of check steam does for friendly names lol.

Hey ich777, sorry should've mentioned it. Talking about Valheim. Visible in terms that it doesn't appear at all on the server list and my friends can't connect via public IP if I just started the container (and even a few hours after startup). But if I wait long enough (I'll monitor today to try and nail down how long it takes) it'll become available and my friends can connect. The weird part is this only happens when I try to host the valheim server from a Docker container in unRAID. If I just host it on my Windows PC like I used too (just tried it again now) the option to connect to via both LAN and Public IP appear rather quickly. Was mostly curious on the behavior and if there was anything I missed configuring within unRAID or the container itself.

Hello @ich777Thank you that did it. Slightly different question, is it normal for it to take a long time for the server to be connectable via public IP + port. on my LAN it's pretty quick for it to appear if I use my internal LAN network + port. But for external connections it can take hours. For example I left mine running last night, first hour or two server was not visible via Public IP + port. When I woke up this morning everything was good and my friends were able to connect. Since I just updated the container and started it up again I'm just curious if it's normal for it to take that long for it to show in either steam > servers or even within the game when connecting via Public IP + port.