Closed Moddingear closed 9 months ago
Hi @Moddingear Thanks for taking the time to fill out a bug report, the information is very helpfull, could you run: netstat -a
on the host machine while the server is running and post the output?
Sure, here you go.
Note : I also have a seafile server, a minecraft server, a valheim server and I am connected via xRDP, so this might not be the shortest netstat ever netstata.txt
First off, I noticed that it is listening on port 8211/TCP, this is not necessary as Palworld uses UDP.
tcp 0 0 0.0.0.0:8211 0.0.0.0:* LISTEN
If possible, could you check if the issue persists if you temporarily shut down the other servers on your server (all except Palworld)?
Ok so I'm dumb but I'm also not : I just changed motherboard on my server (it died). So that changed the MAC on my ethernet. So my server didn't get the same IP from the router. So the IP was wrong, explaining why I couldn't connect... I'm sorry to have bothered you, thanks for your help !
@Moddingear no worries, glad I could help
Describe the bug
I can't connect to the server. Locally or remotely.
To Reproduce
Use the given docker-compose I have a clean palworld container and volume (using docker system prune -a) I have ufw inactive
Expected behavior
I should be able to connect
Desktop (please complete the following information):
docker-compose.yml contents
Container/Host Logs
Additional context
I have tried other containers but have only had the same issue