Does ich777 have an Enshrouded dedicated server docker?   sorry if im asking the same question as others or if its in the works and im early.  

Is anybody else's Palworld server crashing a lot? It seems like it starts eating up a ton of memory that might be an issue, I've seen it using 15GB which is half my total server. Can it be limited?
 

Quote

Exception was "SIGSEGV: invalid attempt to read memory at address 0x0000000000000015"

From my crash logs

3 minutes ago, mb9023 said:

Is anybody else's Palworld server crashing a lot? It seems like it starts eating up a ton of memory that might be an issue, I've seen it using 15GB which is half my total server. Can it be limited?
 

From my crash logs

People speculate it's the bEnableNonLoginPenalty. Try disabling it

Hello, I tried searching for my issue, perhaps i missed it though...

I setup a palworld yesterday evening and it was running with no issues. my friends and I played on it, then this morning I had to unplug my unraid box (i did a clean shutdown first). Now when the game tries to boot, it gets stuck in a loop. i try to watch the log to see where the error occurs, but it loops to quick to see.

And because i saw someone had a similar issue to me, but the suspicion was old hardware, here is my CPU:
AMD Ryzen 5 5600X 6-Core @ 3700 MHz
I'd suspect not hardware since it ran fine for hours.. right?

any suggestions appreciated!

Is there times I can't download your repositories? Been trying to get the Valheim server to download, but am wondering if maybe I have an issue on my end as docker keeps failing to connect.
 

Quote

docker run
  -d
  --name='ValheimServer1'
  --net='host'
  -e TZ="America/Denver"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="OuterHaven"
  -e HOST_CONTAINERNAME="ValheimServer1"
  -e 'GAME_ID'='896660'
  -e 'GAME_PARAMS'=''
  -e 'VALIDATE'=''
  -e 'SRV_NAME'='staves1'
  -e 'WORLD_NAME'='staves1'
  -e 'SRV_PWD'='staves1'
  -e 'PUBLIC'='0'
  -e 'UDP_PORT_2456-2458'='2456-2458'
  -e 'ENABLE_VALHEIMPLUS'=''
  -e 'ENABLE_BEPINEX'=''
  -e 'BACKUP_FILES'='true'
  -e 'BACKUP_INTERVAL'='62'
  -e 'BACKUP_TO_KEEP'='24'
  -e 'USERNAME'=''
  -e 'PASSWRD'=''
  -e 'GAME_PORT'='2456'
  -e 'UID'='99'
  -e 'GID'='100'
  -e 'DEBUG_OUTPUT'='false'
  -e 'LOG_OUTPUT'='false'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/ich777/docker-templates/master/ich777/images/valheim.png'
  -v '/mnt/user/appdata/steamcmd':'/serverdata/steamcmd':'rw'
  -v '/mnt/cache/appdata/valheim':'/serverdata/serverfiles':'rw'
  --restart=unless-stopped 'ich777/steamcmd:valheim'

Unable to find image 'ich777/steamcmd:valheim' locally
docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp [2600:1f18:2148:bc01:571f:e759:a87a:2961]:443: connect: network is unreachable.
See 'docker run --help'.

The command failed.

 

Edited January 31, 20242 yr by Staves

30 minutes ago, Staves said:

Is there times I can't download your repositories? Been trying to get the Valheim server to download, but am wondering if maybe I have an issue on my end as docker keeps failing to connect.
 

 

Looks like your system is having issues connecting to docker hub.  Not directly related to this or any other docker images.

Edited January 31, 20242 yr by dlchamp

13 minutes ago, dlchamp said:

Looks like your system is having issues connecting to docker hub.  Not directly related to this or any other docker images.

Okay thats what I thought. Still learning my way around Unraid, I appreciate the insight and now know where to look a bit deeper.

The thing I find weird about this is my other docker containers update/function fine

6 hours ago, ich777 said:

How do you try to connect exactly? What error message do you get? On which branch are you on the client, so to speak your PC?

I found some one who had the same issue a few months back on this thread. Apparently the only way to connect to it is to open up steam go to favorites and manually add it as ipaddress:27016 and this allows it to be discovered. This is not the game port apparently its the discovery port. 🤷‍♂️

1 hour ago, Miykael13 said:

i try to watch the log to see where the error occurs, but it loops to quick to see.

Stop the container, open the logs and post the output here.

6 hours ago, mb9023 said:

Is anybody else's Palworld server crashing a lot?

No.

 

6 hours ago, mb9023 said:

It seems like it starts eating up a ton of memory that might be an issue, I've seen it using 15GB which is half my total server.

On my server it consumes at times now 20GB+
 

6 hours ago, mb9023 said:

Can it be limited?

Sure, you can limit the size that the container can use, bit be aware if the container reaches that limit it will crash and restart, that will ultimatily lead to corrupt save files in the long term.

 

6 hours ago, mb9023 said:

Exception was "SIGSEGV: invalid attempt to read memory at address 0x0000000000000015"

Are you sure that your RAM in your system is okay and that you weren‘t running out of RAM already?

6 hours ago, Ikeasofa said:

People speculate it's the bEnableNonLoginPenalty. Try disabling it

Where you able to confirm that, I don‘t see any change on my system.

1 hour ago, Staves said:

docker: Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp [2600:1f18:2148:bc01:571f:e759:a87a:2961]:443: connect: network is unreachable.

Are you sure that IPv6 is set up correctly in your network?

It seems like your system can‘t communicate with DockerHub and that‘s the reason why it fails to download the container.

 

Are other containers working? I do nothing different than other maintainers and host the containers on DockerHub.

43 minutes ago, FunkyJamma said:

This is not the game port apparently its the discovery port. 🤷‍♂️

Exactly the Query port is used to query the server and the Query port returns the Game port and all other things like Map, Server Name,…

I don‘t see a reason why that should be wrong.

 

45 minutes ago, FunkyJamma said:

Apparently the only way to connect to it is to open up steam go to favorites and manually

That‘s not entirely true, he actually managed to find it in game, I think he had not set the checkbox Show Password protected Servers IIRC.

6 hours ago, IzzleDude said:

Enshrouded

Please read this post:

 

You should really look first in the CA App since @Nodiaque already made a container for the game.

Hi I'm facing an issue by connecting to my Palword server remotely 
Connection type : Bridge 
8211 UDP open and pointing to the server local ip

27015 TCP/UDP open and pointing to the server's local ip ( Reddit comment suggestion ) 

 

I can connect locally with a password

but my friend is getting a "Connection Timed Out" Message when he tries to connect to my public ip.

Modem restarted .. router restarted .. container restarted  .... didn't work !!!

My ISP is fine I can access other dockers via SWAG so this Palworld Server should be less complicated. 

Edited January 31, 20242 yr by Thamer Alfuraiji

1 minute ago, Thamer Alfuraiji said:

Hi I'm facing an issue by connecting to my Palword server remotely 

8211 UDP open and pointing to the server local ip

27015 TCP/UDP open and pointing to the server's local ip ( Reddit comment suggestion ) 

 

I can connect locally with a password

but my friend is getting a "Connection Timed Out" Message when he tries to connect to my public ip.

Modem restarted .. router restarted .. container restarted  .... didn't work !!!

 

You shouldn't need to open 27015.

Did you give your friend your public-ip:port? For example: 10.42.215.5:8211

5 minutes ago, Ikeasofa said:

You shouldn't need to open 27015.

Did you give your friend your public-ip:port? For example: 10.42.215.5:8211

yes I did .. and as I said ( Public IP) 
please read what I said. 

2 minutes ago, Thamer Alfuraiji said:

yes I did .. and as I said ( Public IP) 
please read what I said. 

Mistakes can happen. Please remain friendly....

Your mistake is that you have bridge. it should be a static IP.

18 minutes ago, Thamer Alfuraiji said:

27015 TCP/UDP open and pointing to the server's local ip ( Reddit comment suggestion ) 

This is completely wrong, nothing is using that port...

 

18 minutes ago, Thamer Alfuraiji said:

but my friend is getting a "Connection Timed Out" Message when he tries to connect to my public ip.

Are you sure that you've forwarded the correct port with the correct protocol, UDP in this case and yes, you only need 8211 UDP.

Please don't forward other ports! It's not necessary, I only list ports which are necessary!

 

Are you sure that your friends have the correct public IP which is also reflected in the log from the container? If it times out then it is not reachable from outside.

 

What is the exact message? Do they see a loading screen or not? If they see a loading screen for about 30 seconds then chances are high that the public IP in your config is not correct or that the port forwarding is not working properly.

 

BTW if you have a domain name assigned to that IP for example yourdomain.com then they simply can connect with yourdomain.com:8211

6 minutes ago, Ikeasofa said:

Your mistake is that you have bridge. it should be a static IP.

The answer is simply no, the bridge is also working fine.

Just now, ich777 said:

The answer is simply no, the bridge is also working fine.

Learned more today. Thanks! People told me I need to assign a static IP for the local network.

2 minutes ago, Ikeasofa said:

Learned more today. Thanks! People told me I need to assign a static IP for the local network.

My server is working just fine on the bridge (about 9 to 11 players on it on a daily basis and have no issues whatsoever with the bridge -  this is the server idling after a container restart) :

 

It will work either way if you are using the default bridge, if you are using a custom bridge, if using the br0 or another interface and if you are using the host network.

26 minutes ago, ich777 said:

This is completely wrong, nothing is using that port...

 

Are you sure that you've forwarded the correct port with the correct protocol, UDP in this case and yes, you only need 8211 UDP.

Please don't forward other ports! It's not necessary, I only list ports which are necessary!

 

Are you sure that your friends have the correct public IP which is also reflected in the log from the container? If it times out then it is not reachable from outside.

 

What is the exact message? Do they see a loading screen or not? If they see a loading screen for about 30 seconds then chances are high that the public IP in your config is not correct or that the port forwarding is not working properly.

 

BTW if you have a domain name assigned to that IP for example yourdomain.com then they simply can connect with yourdomain.com:8211

Ok let's agree on these facts :

1- I'm not a beginner with Unraid / Reverse Proxy / Port forwarding / Basics and differences between local and public IPs and domains. 

2- yes he is connecting via my public IP and port 8211 the loading screen starts for 10-15sec then we get the message in the attached screenshot 

 

3- yes the port 8211 is open and only UDP . 

4- I know about your seggestion of using my domain instead my public ip and that's the plan after I make sure that actually the public ip access is working which for now is not working .. 

 

5- I have attached some screenshots to confirm and to give more details. 

 

6- Yes the Palworld Server is working locally on my other gaming PCs via 192.168.1.181:8211 

 

7- I removed the port forwarding of steam port from my router. 

 

 

Edited January 31, 20242 yr by Thamer Alfuraiji
more details for number 2

7 minutes ago, Thamer Alfuraiji said:

a beginner with Unraid

I have never said that.

 

7 minutes ago, Thamer Alfuraiji said:

2- yes he is connecting via my public IP and port 8211 

7 minutes ago, Thamer Alfuraiji said:

6- Yes the Palworld Server is working locally on my other gaming PCs via 192.168.1.181:8211 

Then something is not working with the forwarding or the public IP address that is specified in the config from the dedicated server is not correct.

Please check in the logs from the container if the public IP matches your real public IP, the container should be able to update the IP on it's own if you enable the option in the template for that.

 

Did he yet try to connect with your domain name like mentioned above, of course only if you've have assigned a domain name to your public IP.

1 minute ago, ich777 said:

I have never said that.

 

Then something is not working with the forwarding or the public IP address that is specified in the config from the dedicated server is not correct.

Please check in the logs from the container if the public IP matches your real public IP, the container should be able to update the IP on it's own if you enable the option in the template for that.

 

Did he yet try to connect with your domain name like mentioned above, of course only if you've have assigned a domain name to your public IP.

the container is updating the IP correctly. shows fine in the log. also the ini gets the updated ip too. 

 

and we tried to restart my modem 3 times
and his also to get new public IPs and we tried  all the 3 and still getting the same results 

 

and also yes just tried my public domain and we got the same message.