ashton

bummer, was hoping it was something id be able to fix easily, thanks for the help though!

Thank you for the reply, stopping the docker did allow me to get the logs, I changed the public ip to xxx.xxx.xxx.xxx just so its not seen. as for steam credentials i never filled those fields in, they were left default blank i also attached an image of the machine this is running on ---PublicIP in PalWorldSettings.ini found: xxx.xxx.xxx.xxx ---Prepare Server--- ---Server ready--- ---Start Server--- ---Ensuring UID: 99 matches user--- usermod: no changes ---Ensuring GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Taking ownership of data...--- ---Starting...--- ---Update SteamCMD--- ** Press ANY KEY to close this window **

I'm not sure what I'm doing wrong, but I've tried multiple things to get Palworld to work i downloaded the docker, kept everything default, went into the palworldsettings.ini and removed the password. set the docker on a custom connection with its own IP and still cannot connect to it locally. When i try to see the logs, it loads the window for like 10 seconds than just closes. i can ping the docker using its IP but every time i try to connect through the game it says it times out. my guess is the docker is restarting every 10 seconds so it never has long enough to really connect. also because of this i cant really copy the logs, unless it saves them somewhere i don't know about tried so hard to try a bunch of different methods before coming here to help, but if anyone has any ideas I'm at whit's end