Synology issues

[fynaltgn]

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

I use like this.

docker run -d \ --name palworld-eklipc \ -p 8211:8211/udp \ -p 27015:27015/udp \ -v /volume1/docker/palworld:/palworld/ \ -e PLAYERS=16 \ -e PORT=8211 \ -e PUID=1000 \ -e PGID=1000 \ -e COMMUNITY=false \ thijsvanloef/palworld-server-docker

When I run it, I need to restart the dsm.

And that's why I removed reboot all the time because otherwise the dsm will let me dumb.

Desktop (please complete the following information):

• OS: Synology 7.1
• Browser firefox
• Version latest

docker-compose.yml contents

Container/Host Logs

WARNING: Error loading config file: .dockercfg: $HOME is not defined 1dea44f8d29e0c518a84720ecf069151e4836f41460506cd36e8b7878a598db8

Additional context

[thijsvanloef]

What version of docker are you running on your NAS? docker --version

[fynaltgn]

Docker Version 20.10.3, build 55f0773

[thijsvanloef]

are you able to run?

• docker run hello-world

[fynaltgn]

Sure, work it!

This message shows that your installation appears to be working correctly.

[thijsvanloef]

Are you able to run:

docker run -d
--name palworld-eklipc
-p 8211:8211/udp
-p 27015:27015/udp
-e PLAYERS=16
-e PORT=8211
-e PUID=1000
-e PGID=1000
-e COMMUNITY=false
thijsvanloef/palworld-server-docker

[fynaltgn]

WARNING: Error loading config file: .dockercfg: $HOME is not defined
"docker run" requires at least 1 argument.
See 'docker run --help'.

Usage:  docker run [OPTIONS] IMAGE [COMMAND] [ARG...]

Run a command in a new container
/volume1/Descargas/palworld eklipc/1705867146/script.log: line 2: --name: command not found
/volume1/Descargas/palworld eklipc/1705867146/script.log: line 3: -p: command not found
/volume1/Descargas/palworld eklipc/1705867146/script.log: line 4: -p: command not found
/volume1/Descargas/palworld eklipc/1705867146/script.log: line 5: -e: command not found
/volume1/Descargas/palworld eklipc/1705867146/script.log: line 6: -e: command not found
/volume1/Descargas/palworld eklipc/1705867146/script.log: line 7: -e: command not found
/volume1/Descargas/palworld eklipc/1705867146/script.log: line 8: -e: command not found
/volume1/Descargas/palworld eklipc/1705867146/script.log: line 9: -e: command not found
/volume1/Descargas/palworld eklipc/1705867146/script.log: line 10: thijsvanloef/palworld-server-docker: No such file or directory

[thijsvanloef]

ah sorry my bad, the following command:

docker run -d \
--name palworld-eklipc \
-p 8211:8211/udp \
-p 27015:27015/udp \
-v /volume1/docker/palworld:/palworld/ \
-e PLAYERS=16 \
-e PORT=8211 \
-e PUID=1000 \
-e PGID=1000 \
-e COMMUNITY=false \
thijsvanloef/palworld-server-docker

[fynaltgn]

In the end I managed to install the server with the qmarchi/palworld iso But the solution would be similar for others.

I noticed that when the container was running it did it from a folder called /game. And in this case it does it with the user /Root, so it installs everything in the root. With thijsvanloef's image I got the feeling that it did it with the user: Steam and I got an error.

The docker folder mapping should look like

Folder file (left): the address of the folder where we want to put the files from the server. y Mount path (Right): the path we found before.

we start the docker and... tachan!

We see all the files! And I was able to upload my save from another dedicated server! 🥇

But now it won't let me touch the server name in the DefaultPalWorldSetting.ini file. If I touch the file it becomes defaults.👎

We will continue to work

[chu-bin]

I successfully deployed the server on my synology nas, synology version 7.2.1 docker using the latest container manager, deployed using docker compose, the volume location is in the /docker/palword-server directory and there are no Errors

[BINGHUAice]

Latest status：Thanks for the advice, luckily I've got the NAS booting up successfully!

I experienced the same problem on my Synology NAS, but unfortunately I used “--restart unless-stopped“, so my Synology NAS would enable the docker container as soon as the system was started, and then the entire NAS would not work. Is there any way to change this?

[xiaoshaoxiaoshao]

I experienced the same problem on my Synology NAS, but unfortunately I used “--restart unless-stopped“, so my Synology NAS would enable the docker container as soon as the system was started, and then the entire NAS would not work. Is there any way to change this?

没错我也遇到了这个问题 我去把我的群辉强制关机再重启就连上了（此时dokcer是未启动的状态） 如果还是不能连的话多重试几次 我的理解是重复重启总有一次ssh服务是比docker启动的快的 能连上ssh就可以把这个 container 关掉了

[fynaltgn]

I experienced the same problem on my Synology NAS, but unfortunately I used “--restart unless-stopped“, so my Synology NAS would enable the docker container as soon as the system was started, and then the entire NAS would not work. Is there any way to change this?

I've made that mistake on other servers before. That option is fine to set if you know that the server starts up and connects fine and works without overflowing anything.

Try: Turn off your dsm, turn it on and quickly connect via ssh.

dokcer ps -a

docker stop idcontainer

[JoycieC]

In the end I managed to install the server with the qmarchi/palworld iso But the solution would be similar for others.

I noticed that when the container was running it did it from a folder called /game. And in this case it does it with the user /Root, so it installs everything in the root. With thijsvanloef's image I got the feeling that it did it with the user: Steam and I got an error.

The docker folder mapping should look like

Folder file (left): the address of the folder where we want to put the files from the server. y Mount path (Right): the path we found before.

we start the docker and... tachan!

We see all the files! And I was able to upload my save from another dedicated server! 🥇

But now it won't let me touch the server name in the DefaultPalWorldSetting.ini file. If I touch the file it becomes defaults.👎

We will continue to work

Hey, could you explain this in more detail? I'm struggling to get this set up with any docker image and a very easy to understand guide would be super appreciated!

Thanks for powering through to get as far as you have so far.

[zapoqx]

I just wanted to add 2 cents to this because I did this a few days ago (like Saturday) when I was going through testing and making a dedicated server. Ironically, it was this one that worked the best, but I think the other 2 options just were missing a few things was all. Anyways... for Synology, I use Portainer to do the same docker handling instead of Synology's own. I use Synology's own to setup Portainer initially and that solves most of the translations for Dockers. It also will solve updating.

Now if anyone else comes across this and has never done it before with a Synology server, even if you have 1 volume, you still have to point to your folder starting with /volume1/path/to/folder. If you have write errors, yes, linux could do the standard chown, but you can write to just the specific folder you made to all. Simply right click the folder in DSM and click on properties, then go into Permissions. Click Advanced Options and click "Make inherited permissions explicit" and then you can define the "Everyone" to have read & write. Otherwise, once you use Portainer, it is literally copy and paste from the front page here and you now have it all working.

THAT SAID, with portainer, I found that I had a block port issue going and took me forever to find why, so the only change I did since 8211 has been said to be required is set the public mapping port on both the "ports" configuration and the environment "PUBLIC_PORT" setting to a different port for external access and that got it going. "PORT" can remain default.

Hope it solves for all.

[xiaoshaoxiaoshao]

我的群辉是 DSM7.1.1-42962 昨天在跑这个项目的时候系统无响应了两次 后来就放弃了 直到我跑了另一个项目 https://github.com/jammsen/docker-palworld-dedicated-server?tab=readme-ov-file 并且在 docker-compose up 的时候看到了与这个项目同样的报错

Creating palworld-server ... done Attaching to palworld-server palworld-server | Executing usermod... palworld-server | usermod: no changes palworld-server | STARTING INSTALL/UPDATEtid(22) burning pthread_key_t == 0 so we never use it palworld-server | Redirecting stderr to '/home/steam/Steam/logs/stderr.txt' palworld-server | Logging directory: '/home/steam/Steam/logs' palworld-server | src/tier0/threadtools.cpp (4213) : Probably deadlock or failure waiting for thread to initialize. palworld-server | [ 0%] Checking for available updates... palworld-server | Thread failed to initialize palworld-server | src/tier0/threadtools.cpp (4213) : Probably deadlock or failure waiting for thread to initialize. palworld-server | Thread failed to initialize

于是我怀疑是系统的问题之后着手升级了我的群辉(DSM7.1.1-42962 -> DSM7.2.1-69057)

服务器就成功的跑起来了！

PS : 此外我还发现了一个有趣的东西可以带ui的配置服务器参数 https://github.com/DysonCheng/PalWorldSettingGenerator https://dysoncheng.github.io/PalWorldSettingGenerator/setting.html

[jryanearl]

I just wanted to add 2 cents to this because I did this a few days ago (like Saturday) when I was going through testing and making a dedicated server. Ironically, it was this one that worked the best, but I think the other 2 options just were missing a few things was all. Anyways... for Synology, I use Portainer to do the same docker handling instead of Synology's own. I use Synology's own to setup Portainer initially and that solves most of the translations for Dockers. It also will solve updating.

Now if anyone else comes across this and has never done it before with a Synology server, even if you have 1 volume, you still have to point to your folder starting with /volume1/path/to/folder. If you have write errors, yes, linux could do the standard chown, but you can write to just the specific folder you made to all. Simply right click the folder in DSM and click on properties, then go into Permissions. Click Advanced Options and click "Make inherited permissions explicit" and then you can define the "Everyone" to have read & write. Otherwise, once you use Portainer, it is literally copy and paste from the front page here and you now have it all working.

THAT SAID, with portainer, I found that I had a block port issue going and took me forever to find why, so the only change I did since 8211 has been said to be required is set the public mapping port on both the "ports" configuration and the environment "PUBLIC_PORT" setting to a different port for external access and that got it going. "PORT" can remain default.

Hope it solves for all.

I have this running on my Synology DS1821+ with the "Container Manager" package from Synology. It's super simple there to set this up. I even found this github through its Docker Registry search interface.

[zapoqx]

I have this running on my Synology DS1821+ with the "Container Manager" package from Synology. It's super simple there to set this up. I even found this github through its Docker Registry search interface.

Same club, but I point this out because it was far easier to also setup console access within Portainer while also making sure you have the internal networks properly set. There is a reason a place like Marius was switching to Portainer. Also, I joined this when it wasn't in the registry yet (Day 2 of game release?).

[reedickulus]

THAT SAID, with portainer, I found that I had a block port issue going and took me forever to find why, so the only change I did since 8211 has been said to be required is set the public mapping port on both the "ports" configuration and the environment "PUBLIC_PORT" setting to a different port for external access and that got it going. "PORT" can remain default.

Can you give more details or show your set-up? I am having a weird issue where I can connect using my Local-IPAddress:8211, but not with Public-IPAddress:8211, despite port forwarding correctly in my router.

[zapoqx]

Can you give more details or show your set-up? I am having a weird issue where I can connect using my Local-IPAddress:8211, but not with Public-IPAddress:8211, despite port forwarding correctly in my router.

Use a tool to check the port from an outside source. If its blocked, its either the ISP blocking it or some other secure element is blocking it. Sometimes Stealth methods can also block it. In that case, change to a port that is much higher and see if that helps. It seems the Public Port isn't respected though for whatever reason now, but will respect the "port" configuration when starting so I just full changed the external port for 8211 on exposed and internal to the same port I chose that nothing else had access to (give you have up to 65535 I believe, too tired to reference right now as its been a long day, there is a darn good chance of finding something above 12000 that works). Make sure router setup is reflective of that. So for instance, if you wanted to try like 11000, just change the UDP Port to 11000:11000 and set the port configuration to 11000. Then make sure your router will expose port 11000 to whatever the server device is.

That should do it.

[reedickulus]

Can you give more details or show your set-up? I am having a weird issue where I can connect using my Local-IPAddress:8211, but not with Public-IPAddress:8211, despite port forwarding correctly in my router.

Use a tool to check the port from an outside source. If its blocked, its either the ISP blocking it or some other secure element is blocking it. Sometimes Stealth methods can also block it. In that case, change to a port that is much higher and see if that helps. It seems the Public Port isn't respected though for whatever reason now, but will respect the "port" configuration when starting so I just full changed the external port for 8211 on exposed and internal to the same port I chose that nothing else had access to (give you have up to 65535 I believe, too tired to reference right now as its been a long day, there is a darn good chance of finding something above 12000 that works). Make sure router setup is reflective of that. So for instance, if you wanted to try like 11000, just change the UDP Port to 11000:11000 and set the port configuration to 11000. Then make sure your router will expose port 11000 to whatever the server device is.

That should do it.

Thanks, I'm going to try your steps. I used outside checker (https://check-host.net/ --> UDP Port) and it says open. https://www.yougetsignal.com/tools/open-ports/ says closed (maybe it does TCP but not UDP)?

To be clear, you mean in the docker-compose, you changed the following (where <------- arrow is pointing)?

palworld: image: thijsvanloef/palworld-server-docker:latest # Use the latest-arm64 tag for arm64 hosts restart: unless-stopped container_name: palworld-server stop_grace_period: 30s # Set to however long you are willing to wait for the container to gracefully stop ports:

• 8211:8211/udp <-------------------
• 27015:27015/udp environment:
  • PUID=1000
  • PGID=1000
  • PORT=8211 # Optional but recommended
  • PLAYERS=6 # Optional but recommended
  • SERVER_PASSWORD= # Optional but recommended
  • MULTITHREADING=true
  • RCON_ENABLED=true
  • RCON_PORT=25575

Can you share your compose file?

[zapoqx]

yes and also

• PORT=8211 # Optional but recommended

Unfortunately, I cannot as I'm about to head to bed as it needs super sanitizing, but I didn't put my the env variables in an env file (though I could), I just left it in below a comment point. But if you still want it, I'll see if I have time in the morning to post my config (sanitized of course)

[reedickulus]

Thanks - I got it working. Apparently, it might have been working for a long time. Made the mistake of trying to connect to the server (hosted on my NAS) while on the same network (i.e. both my computer and the NAS are connected to the same router). Well - turns out, in this situation, I need to connect using the local IP address of the NAS. But those on a different network, had no issue connecting using my Public IP address.

[zapoqx]

Made the mistake of trying to connect to the server (hosted on my NAS) while on the same network (i.e. both my computer and the NAS are connected to the same router). Well - turns out, in this situation, I need to connect using the local IP address of the NAS. But those on a different network, had no issue connecting using my Public IP address.

Hah at least you don't have the complexities of my network, as small as it is, having multiple subnets. That challenge was far worse. Glad you got it working!

[reedickulus]

Made the mistake of trying to connect to the server (hosted on my NAS) while on the same network (i.e. both my computer and the NAS are connected to the same router). Well - turns out, in this situation, I need to connect using the local IP address of the NAS. But those on a different network, had no issue connecting using my Public IP address.

Hah at least you don't have the complexities of my network, as small as it is, having multiple subnets. That challenge was far worse. Glad you got it working!

I guess I celebrated too soon. I'm still having issues. In my folder "docker > palworld > data" everything is empty. I double and triple checked that permissions are all set-up correctly, but still having issues (your steps about giving "Everyone" permissions with explicit inherit).

This guy might have the solution (docker folder mapping), but I didn't understand his instructions or where his screenshot came from: https://github.com/thijsvanloef/palworld-server-docker/issues/35#issuecomment-1905094934

[reedickulus]

In the end I managed to install the server with the qmarchi/palworld iso But the solution would be similar for others.

I noticed that when the container was running it did it from a folder called /game. And in this case it does it with the user /Root, so it installs everything in the root. With thijsvanloef's image I got the feeling that it did it with the user: Steam and I got an error.

The docker folder mapping should look like

Folder file (left): the address of the folder where we want to put the files from the server. y Mount path (Right): the path we found before.

we start the docker and... tachan!

We see all the files! And I was able to upload my save from another dedicated server! 🥇

But now it won't let me touch the server name in the DefaultPalWorldSetting.ini file. If I touch the file it becomes defaults.👎

We will continue to work

Please I need help with your instructions - where is that screenshot from for folder mapping?!

[zapoqx]

Made the mistake of trying to connect to the server (hosted on my NAS) while on the same network (i.e. both my computer and the NAS are connected to the same router). Well - turns out, in this situation, I need to connect using the local IP address of the NAS. But those on a different network, had no issue connecting using my Public IP address.

Hah at least you don't have the complexities of my network, as small as it is, having multiple subnets. That challenge was far worse. Glad you got it working!

I guess I celebrated too soon. I'm still having issues. In my folder "docker > palworld > data" everything is empty. I double and triple checked that permissions are all set-up correctly, but still having issues (your steps about giving "Everyone" permissions with explicit inherit).

This guy might have the solution (docker folder mapping), but I didn't understand his instructions or where his screenshot came from: #35 (comment)

Alright, at least I'm home so let me ask this, since this is a NAS, whatever the folder you made, you sure its pointing properly? In other words, for the folder, if its on Volume 1, is the volume set to "Volume1/path/to/folder:game"?

Also, Marius just posted the proper instructions on the NAS, you will like his instructions which should explain it all here, but then you can go more advanced with the options here. https://mariushosting.com/how-to-install-palworld-server-on-your-synology-nas/

[smithore]

Whew, I had the same problem as those above. I stupidly set the process to auto-start and was completely locked out of my NAS. I had to do a hard reboot, SSH in as quickly as possible to run the top command. Thankfully once top was running, it kept resource priority and I was able to kill the docker process (I found the keyword "steam" in the list of processes). I also used docker update --restart=no [containerName] to set the container to not auto-start.

Lesson learned -- don't set a docker container to auto-start until you've started it manually a few times and know that it works.

Now to try to figure out what the root problem is, and why this docker container runs away with the NAS.

[zapoqx]

Now to try to figure out what the root problem is, and why this docker container runs away with the NAS.

The only question I'll ask: Is Your NAS less than 6 GB in Memory?

[smithore]

Now to try to figure out what the root problem is, and why this docker container runs away with the NAS.

The only question I'll ask: Is Your NAS less than 6 GB in Memory?

I've got a 1515+ with 16GB of memory. When I start the docker container, the CPU usage goes through the roof and the system becomes mostly unresponsive until I kill the container.

[zapoqx]

I've got a 1515+ with 16GB of memory. When I start the docker container, the CPU usage goes through the roof and the system becomes mostly unresponsive until I kill the container.

Hmm. I wonder if it has to do with the outdated Docker version? If it has been updated that is for that NAS.

[thijsvanloef]

Is this issue still relevant?

[zapoqx]

Is this issue still relevant?

To the initial bug or Smithore's issue about the runaway CPU? To Smithore's issue, I can say that on the Synology, there was an update last year that fixed up Docker components by being updated to something more supported, and I think there is supposed to be another one in the next few months to really update stuff as the docker component prior to last year's update was very old. It is why I am curious if the runaway CPU thing on Smithore's issue is only singled to a device from 2014/2015 that might have lost support.

I know on mine being a year 20/21 release, it has worked for a long time, but I prefer installing Portainer to use the initial code offered (Docker Compose) vs the accepted Docker Run format that Synology's container manager uses, but this way, I also have access to the console individually if something comes up.

But that is only my response. I can't speak for everyone here.

[smithore]

I was never able to resolve this issue with my Synology DS1515+. I am happy to continue to be a guinea pig for any potential fixes, but am also happy to move on to another solution and let this issue close without resolution, especially if we think the trouble is with a certain model / year of DS.

[TheKogoro]

I have installed on an ASUSTOR NAS, for people doing this, this is exactly same as https://mariushosting.com/how-to-install-palworld-server-on-your-synology-nas/ tutorial exept one things (if you dont do that, it will write the install in a non accessible to user folder). You need to change "docker" by "Docker" in the line "- /volume1/docker/palworld-server:/palworld:rw" (yeah, just a "D" and for me, that is working fine :)

[reedickulus]

I'm still getting "dlmopen steamservice.so failed when start up."

Going to continue troubleshooting.

[reedickulus]

I fixed it by deleting my entire palworld folder inside of the docker folder. Re-created the palworld image/container/stack and then manually imported my backup saved files (using the posted method in the ReadMe), then everything fixed itself.

[TheKogoro]

I try to manage to make my server accessible on the internet from my Asustor NAS but i was unable to do it. i can without problems acces from local network but not from internet. I have a port redirection on my router but it didnt know what make the server not accessible from internet.

I have read many things but also not helped because english isnt my native language and understand why isnt work and what to do is verry dificult.

[reedickulus]

I try to manage to make my server accessible on the internet from my Asustor NAS but i was unable to do it. i can without problems acces from local network but not from internet. I have a port redirection on my router but it didnt know what make the server not accessible from internet.

I have read many things but also not helped because english isnt my native language and understand why isnt work and what to do is verry dificult.

I am not familiar with Asustor, but do you have a firewall on your NAS? In other words, make sure the ports are open (1) on your router and (2) on your Asustor NAS.

[reedickulus]

I try to manage to make my server accessible on the internet from my Asustor NAS but i was unable to do it. i can without problems acces from local network but not from internet. I have a port redirection on my router but it didnt know what make the server not accessible from internet. I have read many things but also not helped because english isnt my native language and understand why isnt work and what to do is verry dificult.

I am not familiar with Asustor, but do you have a firewall on your NAS? In other words, make sure the ports are open (1) on your router and (2) on your Asustor NAS.

Have you checked if your port is open on https://www.yougetsignal.com/tools/open-ports/ or https://portchecker.co/ ?

[TheKogoro]

I try to manage to make my server accessible on the internet from my Asustor NAS but i was unable to do it. i can without problems acces from local network but not from internet. I have a port redirection on my router but it didnt know what make the server not accessible from internet. I have read many things but also not helped because english isnt my native language and understand why isnt work and what to do is verry dificult.

I am not familiar with Asustor, but do you have a firewall on your NAS? In other words, make sure the ports are open (1) on your router and (2) on your Asustor NAS.

Have you checked if your port is open on https://www.yougetsignal.com/tools/open-ports/ or https://portchecker.co/ ?

It's closed, but i really dont know how to open it on my Asustor, it's open on my router, Reverse proxy isnt same as synology and i already have a web server that use HTTP and HTTPS ports. I think the NAS didnt kwno what to do with this port from internet (but from local network with local ip it working)

[reedickulus]

I try to manage to make my server accessible on the internet from my Asustor NAS but i was unable to do it. i can without problems acces from local network but not from internet. I have a port redirection on my router but it didnt know what make the server not accessible from internet. I have read many things but also not helped because english isnt my native language and understand why isnt work and what to do is verry dificult.

I am not familiar with Asustor, but do you have a firewall on your NAS? In other words, make sure the ports are open (1) on your router and (2) on your Asustor NAS.

Have you checked if your port is open on https://www.yougetsignal.com/tools/open-ports/ or https://portchecker.co/ ?

It's closed, but i really dont know how to open it on my Asustor, it's open on my router, Reverse proxy isnt same as synology and i already have a web server that use HTTP and HTTPS ports. I think the NAS didnt kwno what to do with this port from internet (but from local network with local ip it working)

I found this on Google: https://www.asustor.com/en/online/College_topic?topic=224

Did you try the steps there for (EZ-Router)?

Also, use this: https://check-host.net/check-udp to check if your port is open (more reliable than the other ones I shared).

[reedickulus]

I try to manage to make my server accessible on the internet from my Asustor NAS but i was unable to do it. i can without problems acces from local network but not from internet. I have a port redirection on my router but it didnt know what make the server not accessible from internet. I have read many things but also not helped because english isnt my native language and understand why isnt work and what to do is verry dificult.

I am not familiar with Asustor, but do you have a firewall on your NAS? In other words, make sure the ports are open (1) on your router and (2) on your Asustor NAS.

Have you checked if your port is open on https://www.yougetsignal.com/tools/open-ports/ or https://portchecker.co/ ?

It's closed, but i really dont know how to open it on my Asustor, it's open on my router, Reverse proxy isnt same as synology and i already have a web server that use HTTP and HTTPS ports. I think the NAS didnt kwno what to do with this port from internet (but from local network with local ip it working)

I found this on Google: https://www.asustor.com/en/online/College_topic?topic=224 Did you try the steps there for (EZ-Router)? Also, use this: https://check-host.net/check-udp to check if your port is open (more reliable than the other ones I shared).

I have acces on all my services that is installed on my Asustor from internet, Exept the Palworld Server (that is not in the list of EZ-Router).

So do this: "If the service that you wish to open is not on the list or you wish to set up self-defined port forwarding, you can click on [Self define]."

And open the port (default is 8211 and 27015).

[TheKogoro]

I try to manage to make my server accessible on the internet from my Asustor NAS but i was unable to do it. i can without problems acces from local network but not from internet. I have a port redirection on my router but it didnt know what make the server not accessible from internet. I have read many things but also not helped because english isnt my native language and understand why isnt work and what to do is verry dificult.

I am not familiar with Asustor, but do you have a firewall on your NAS? In other words, make sure the ports are open (1) on your router and (2) on your Asustor NAS.

Have you checked if your port is open on https://www.yougetsignal.com/tools/open-ports/ or https://portchecker.co/ ?

It's closed, but i really dont know how to open it on my Asustor, it's open on my router, Reverse proxy isnt same as synology and i already have a web server that use HTTP and HTTPS ports. I think the NAS didnt kwno what to do with this port from internet (but from local network with local ip it working)

I found this on Google: https://www.asustor.com/en/online/College_topic?topic=224 Did you try the steps there for (EZ-Router)? Also, use this: https://check-host.net/check-udp to check if your port is open (more reliable than the other ones I shared).

I have acces on all my services that is installed on my Asustor from internet, Exept the Palworld Server (that is not in the list of EZ-Router).

So do this: "If the service that you wish to open is not on the list or you wish to set up self-defined port forwarding, you can click on [Self define]."

And open the port (default is 8211 and 27015).

I have ad it on the list (It's now on the EZ-Router and on the "UPNP" list on the router) but, when i test it say port is always closed :/

[reedickulus]

I try to manage to make my server accessible on the internet from my Asustor NAS but i was unable to do it. i can without problems acces from local network but not from internet. I have a port redirection on my router but it didnt know what make the server not accessible from internet. I have read many things but also not helped because english isnt my native language and understand why isnt work and what to do is verry dificult.

I am not familiar with Asustor, but do you have a firewall on your NAS? In other words, make sure the ports are open (1) on your router and (2) on your Asustor NAS.

Have you checked if your port is open on https://www.yougetsignal.com/tools/open-ports/ or https://portchecker.co/ ?

It's closed, but i really dont know how to open it on my Asustor, it's open on my router, Reverse proxy isnt same as synology and i already have a web server that use HTTP and HTTPS ports. I think the NAS didnt kwno what to do with this port from internet (but from local network with local ip it working)

I found this on Google: https://www.asustor.com/en/online/College_topic?topic=224 Did you try the steps there for (EZ-Router)? Also, use this: https://check-host.net/check-udp to check if your port is open (more reliable than the other ones I shared).

I have acces on all my services that is installed on my Asustor from internet, Exept the Palworld Server (that is not in the list of EZ-Router).

So do this: "If the service that you wish to open is not on the list or you wish to set up self-defined port forwarding, you can click on [Self define]." And open the port (default is 8211 and 27015).

I have ad it on the list (It's now on the EZ-Router and on the "UPNP" list on the router) but, when i test it say port is always closed :/

Hmm, what router are you using (ASUS, Netgear, other?). I don't like UPNP - try disabling UPNP and manually forwarding the port (pointing to your internal NAS IP address, of course).

[TheKogoro]

I try to manage to make my server accessible on the internet from my Asustor NAS but i was unable to do it. i can without problems acces from local network but not from internet. I have a port redirection on my router but it didnt know what make the server not accessible from internet. I have read many things but also not helped because english isnt my native language and understand why isnt work and what to do is verry dificult.

I am not familiar with Asustor, but do you have a firewall on your NAS? In other words, make sure the ports are open (1) on your router and (2) on your Asustor NAS.

Have you checked if your port is open on https://www.yougetsignal.com/tools/open-ports/ or https://portchecker.co/ ?

It's closed, but i really dont know how to open it on my Asustor, it's open on my router, Reverse proxy isnt same as synology and i already have a web server that use HTTP and HTTPS ports. I think the NAS didnt kwno what to do with this port from internet (but from local network with local ip it working)

I found this on Google: https://www.asustor.com/en/online/College_topic?topic=224 Did you try the steps there for (EZ-Router)? Also, use this: https://check-host.net/check-udp to check if your port is open (more reliable than the other ones I shared).

I have acces on all my services that is installed on my Asustor from internet, Exept the Palworld Server (that is not in the list of EZ-Router).

So do this: "If the service that you wish to open is not on the list or you wish to set up self-defined port forwarding, you can click on [Self define]." And open the port (default is 8211 and 27015).

I have ad it on the list (It's now on the EZ-Router and on the "UPNP" list on the router) but, when i test it say port is always closed :/

Hmm, what router are you using (ASUS, Netgear, other?). I don't like UPNP - try disabling UPNP and manually forwarding the port (pointing to your internal NAS IP address, of course).

Already tried to do manually add port redirection directly on the router but didnt work too (port is added sucefully but always recognised as closed on test).

Every app or container downloaded on Asustor store have "redirection" i think. i have deluge , Vaultwarden (That is also on docker) and it's accessible on internet without problem. i think the NAS didnt know what to do with the Palworld ports and dont know where nee to redirect on the correct container and it act as is closed because it go on nothing, but why is working on local and not on internet, that i didnt kwnow

Did is possible i nee to add a specific "Config line" into the "Stacks" for make accessible from internet ?

[reedickulus]

You don't need the port to be open for local access.

Probably the app or container downloaded from Asustor store automatically opens the right port on the NAS firewall.

How did you create your palworld image on your Asustor NAS? I imagine it wasn't available on the Asustor store... so did you use Portainer, or some sort of Asustor-branded "Container Manager"? Did you use a docker-compose file (with our without an .env file) or did you use docker command line to make palworld server image?

[reedickulus]

Also, to be clear, did you open BOTH ports I mentioned (assuming these default ones are the ones you specified when you built your palworld image, 8211 and 27015)? And make sure the ports are open for UDP (though if you want to open them to "All" or "TCP/UDP" that would be fine and preferrable as we troubleshoot.

[TheKogoro]

Also, to be clear, did you open BOTH ports I mentioned (assuming these default ones are the ones you specified when you built your palworld image, 8211 and 27015)? And make sure the ports are open for UDP (though if you want to open them to "All" or "TCP/UDP" that would be fine and preferrable as we troubleshoot.

It's open on UDP Both 8211 and 27015. I have build the server with Portainer CE (Note that is no obligation to "Activate" a redirection in EZ-Router, HTTP and HTTPS is actived only on router and webserver working fine (I manage to use less possible UPNP)).

Here is the "Stacks" used for building the server:

version: "3.9"
services:
   palworld:
      image: thijsvanloef/palworld-server-docker:latest # Use :latest-arm64 tag instead of :latest for arm64 NAS
      restart: unless-stopped
      container_name: Palworld-Server
      stop_grace_period: 30s # Set to however long you are willing to wait for the container to gracefully stop
      ports:
        - 8211:8211/udp
        - 27015:27015/udp
      environment:
        - PUID=1002
        - PGID=1000
        - PORT=8211
        - PLAYERS=6
        - SERVER_PASSWORD=PASSWORDIPUT
        - MULTITHREADING=true
        - RCON_ENABLED=true
        - RCON_PORT=25575
        - TZ=Europe/Zurich
        - ADMIN_PASSWORD=PASSWORDIPUT # You can secure the access to a server by using the admin password.
        - COMMUNITY=false  # Enable this with true if you want your server to show up in the community servers tab, USE WITH SERVER_PASSWORD above.
        - SERVER_NAME=Kogoro Server
        - SERVER_DESCRIPTION=Serveur Palworld de Kogoro (Heberge sur NAS)

        - DIFFICULTY=None
        - DAYTIME_SPEEDRATE=1.000000
        - NIGHTTIME_SPEEDRATE=1.000000
        - EXP_RATE=1.300000
        - PAL_CAPTURE_RATE=2.000000
        - PAL_SPAWN_NUM_RATE=1.000000
        - PAL_DAMAGE_RATE_ATTACK=1.000000
        - PAL_DAMAGE_RATE_DEFENSE=1.000000
        - PLAYER_DAMAGE_RATE_ATTACK=1.500000
        - PLAYER_DAMAGE_RATE_DEFENSE=0.700000
        - PLAYER_STOMACH_DECREASE_RATE=1.000000
        - PLAYER_STAMINA_DECREASE_RATE=1.000000
        - PLAYER_AUTO_HP_REGEN_RATE=1.000000
        - PLAYER_AUTO_HP_REGEN_RATE_IN_SLEEP=1.000000
        - PAL_STOMACH_DECREASE_RATE=1.000000
        - PAL_STAMINA_DECREASE_RATE=1.000000
        - PAL_AUTO_HP_REGEN_RATE=1.000000
        - PAL_AUTO_HP_REGEN_RATE_IN_SLEEP=1.000000
        - BUILD_OBJECT_DAMAGE_RATE=1.000000
        - BUILD_OBJECT_DETERIORATION_DAMAGE_RATE=0.000000
        - COLLECTION_DROP_RATE=2.000000
        - COLLECTION_OBJECT_HP_RATE=1.000000
        - COLLECTION_OBJECT_RESPAWN_SPEED_RATE=1.000000
        - ENEMY_DROP_ITEM_RATE=2.000000
        - DEATH_PENALTY=None
        - ENABLE_PLAYER_TO_PLAYER_DAMAGE=False
        - ENABLE_FRIENDLY_FIRE=False
        - ENABLE_INVADER_ENEMY=True
        - ACTIVE_UNKO=True
        - ENABLE_AIM_ASSIST_PAD=True
        - ENABLE_AIM_ASSIST_KEYBOARD=True
        - DROP_ITEM_MAX_NUM=4079
        - DROP_ITEM_MAX_NUM_UNKO=100
        - BASE_CAMP_MAX_NUM=128
        - BASE_CAMP_WORKER_MAX_NUM=20
        - DROP_ITEM_ALIVE_MAX_HOURS=1.000000
        - AUTO_RESET_GUILD_NO_ONLINE_PLAYERS=False
        - AUTO_RESET_GUILD_TIME_NO_ONLINE_PLAYERS=72.00000
        - GUILD_PLAYER_MAX_NUM=20
        - PAL_EGG_DEFAULT_HATCHING_TIME=0.50000
        - WORK_SPEED_RATE=1.000000
        - IS_MULTIPLAY=True
        - IS_PVP=False
        - CAN_PICKUP_OTHER_GUILD_DEATH_PENALTY_DROP=False
        - ENABLE_NON_LOGIN_PENALTY=True
        - ENABLE_FAST_TRAVEL=True
        - IS_START_LOCATION_SELECT_BY_MAP=False
        - EXIST_PLAYER_AFTER_LOGOUT=False
        - ENABLE_DEFENSE_OTHER_GUILD_PLAYER=False
        - COOP_PLAYER_MAX_NUM=4
        - REGION=
        - USEAUTH=True
        - BAN_LIST_URL=https://api.palworldgame.com/api/banlist.txt

      volumes:
         - /volume1/Docker/palworld-server:/palworld

[reedickulus]

In portainer, what network is the server one? ("bridge" or "palworld_default_network") or something like that - make sure that the network is also "allowed" in your NAS firewall ... Eitherwise, I'm out of suggestions on why you're port remains closed - but that's the issue, I think. If you can get the port open, others will be able to connect.

[zapoqx]

I had a similar problem with 8211 where it took me realizing somehow the port was blocked by ISP so I simply changed it. At the time with public port working, I only used the changed value for external, but kept it to 8211 and used public port value to force it to realize what I want. But changing all port settings to match is practically the same without using public port. Try changing the port and the port request to something else, like 12500 for example and make sure it is updated in your router then try again.