search

jammsen / docker-palworld-dedicated-server

Docker container to easily provision and manage Palworld Dedicated Server
https://hub.docker.com/r/jammsen/palworld-dedicated-server
MIT License
911 stars 158 forks source link

Running this on a NAS without Steam #3

Closed kryst4line closed 9 months ago

kryst4line commented 9 months ago

Have you read the Important information text above

Current behavior

First of all this is more of a question than an actual issue, sorry about that.

My goal is to run a Palworld dedicated server on my NAS, but in the code I'm seeing references to steam itself; am I supposed to install Steam as well?

Desired behavior

Run a server on my NAS

Links to screenshots

No response

To Reproduce

-

Software setup

Hardware setup

-

Additional context

No response

Catsanova commented 9 months ago

You don't need to install Steam, the container includes SteamCMD. It works for me on a QNAP NAS without changing anything.

jammsen commented 9 months ago

What @Catsanova wrote is accurate, thanks!

chsoriano commented 9 months ago

I'm trying to get this running on a QNAP NAS also. I've created firewall rules on my gateway (Unifi) but the container still reboots with error: Fatal Error: Steamcmd needs to be online to update. Please confirm your network connection and try again. (screenshot below)

image

jammsen commented 9 months ago

Then your container isnt online, SteamCMD always auto-updates itself and then downloads the package you require.

jammsen commented 9 months ago

Hey @kryst4line is your question answered and can this issue be closed?

Luosuu commented 9 months ago

@Catsanova Would you like to publish a detailed tutorial for how to run this on QNAP? Thank you very much! Should I use the container station app to pull & run this directly?

kryst4line commented 9 months ago

@jammsen Thanks for the response, will try again with your image today! Feel free to close, if I find any issue that it's not reported will make another post if that's better for you

disfluxly commented 9 months ago

@Luosuu - I'm also running this on a QNAP NAS, specifically the TS-251+ model (which is almost 10 years old).

It's extremely simple to setup. Just run the container directly through Container Station. Use the advanced configuration to make sure to set the port mapping for 8211:8211 via NAT. Also make sure to fill in all the Environment Variables that can be seen on this repo's README. By default it wants to use a Docker volume. I changed this to use a host binded volume instead, so that I can possibly use a different device to run the server without losing any of the existing data.

After it's running, just make sure to port forward 8211 to your NAS on your router if you want to open it up to the internet.

Generally for connectivity, I recommend setting the community server setting to false. It's pretty impossible to find anything in the community server right now. Set up Dynamic DNS and use that in the Public IP portion of the Env Var. Don't set a server password (since a direct connection doesn't prompt for a password, and the recent lobby trick of seeing previously attempted connections doesn't seem to be working with how overloaded their backend servers are).

For performance, I would say it's not great, but I am on a near 10 year old NAS. I get between 20-30 Server FPS with 2-4 people playing on it.

I'm curious which QNAP NAS @Catsanova has and what Server FPS they're getting, as I was looking to upgrade my unit anyways.

Luosuu commented 9 months ago

@disfluxly Thank you so much! I will git it a try on my one later. My one is a TS-563 which is almost 10 year old (made in 2015/2016) 😢

reedickulus commented 8 months ago

I'm trying to get this running on a QNAP NAS also. I've created firewall rules on my gateway (Unifi) but the container still reboots with error: Fatal Error: Steamcmd needs to be online to update. Please confirm your network connection and try again. (screenshot below)

image

I am getting the same error message - did you find a fix?