GrandpaXXL

The caching part makes a lot of sense ... i will try the above approach with the schedule change and maybe another dyndns provider. Get in touch again when I know for sure whether one of the approaches worked. Thanks so far ...

I have a dynamic ip and use the dyndns service of my fritz box (xxxxx.myfritz.net:2456). My friends and i use this name ... is that possibly the problem? Connection loss when my internet address changes? I checked my reboot script ... it restarts the container every night at 3:00 am, but my fritz box renews its ip roundabout 4:00 am ... Changed the reboot script starting time to 06:00 am ... we will see if this shows any progress ...

Hello all, my friends and me use your container for playing valheim a few month now … and it's working flawless (beside the fact that BepInEx died on the way … really not that important … I just disabled it). But since the start the service is unreliable in terms of availability. Meaning: Every one, two or three days the valheim server can no longer be connected (question mark or cross in the valheim server list). The solution is always just a simple reboot of the docker container ... after that, everything is back to normal. I even set a scheduled task to reboot the container every night ... but still 50% of the time i have to reboot it manually before we can start a session. Is there any explanation for this behaviour … anything I can do? Attached the view when the service is not reachable.