montmyint

Yeah I've been stopping the docker between changes (it only took one time of settings not sticking to remember). So it was the steam client confusing me, I was able to connect via direct connection in game. Looks like patience on the cards tonight, I'll set it back up as a community server and just leave it

@therave39 No dice. Rebooted after removing the params, got to the loop I had above and it's stuck on starting again. No local server available.

I'll disable the community server param and see if it turns up on my local server lists. Will update in a few mins

No too sure what I'm doing wrong (or if I'm doing anything wrong). But I've tried a Palworld server and it seems to boot fine, however after 15-20 mins the server is not available. Like others , I believe port forwarding id fine because I use your other servers without issue. What seems to happen is that the server starts, a random restart kicks in then it gets stuck on starting server. A manual restart of the docker restarts the whole process again. Log below:

unless you ask the pack to be updated your players will need to downgrade to the version of ATM7 your docker is running

Hi, would it be possible to push the 1.3 update to the docker image? Thanks in advance!

thanks

Would it be possible to push an upgrade to 1.2 for this please?

Yes, which is what I've done. What you do is edit the container and update the repository to add :TAG after the arch-emby bit like below I would check for updates on the docker hub for updates and only use the above as a workaround for now.