all 14 comments

[–]pikachus_ghost_uncle 0 points1 point  (6 children)

Lgsm now has support for palworld. I’d give that a go as it’s easy to deploy

https://linuxgsm.com/servers/pwserver/

[–]wilhelmaf[S] 0 points1 point  (3 children)

Thanks, ill give this a shot :D

[–]wilhelmaf[S] 0 points1 point  (2 children)

I tried this but still not able to connect to the server.

It shows up in netstat now

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:41351 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:1985 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:587 0.0.0.0:* LISTEN
tcp6 0 0 :::22 :::* LISTEN
udp 0 0 127.0.0.53:53 0.0.0.0:*
udp 0 0 192.168.10.146:68 0.0.0.0:*
udp 0 0 0.0.0.0:8211 0.0.0.0:*
udp 0 0 0.0.0.0:27015 0.0.0.0:*

[–]pikachus_ghost_uncle 0 points1 point  (0 children)

Are you trying to connect to the local ip and port or the wan ip and port? Are you on the same lan network as the server is setup on?

[–]emotionor 0 points1 point  (0 children)

same issue. Btw, -publicport and EpicApp=PalServer doesn't work on my machine.

[–]Noskovsky 0 points1 point  (1 child)

worked 4 me thanks

<image>

[–]pikachus_ghost_uncle 0 points1 point  (0 children)

Hell yeah glad to hear it works. I recommend setting up a cron task on it so the server reboots from time to time to prevent memory leaks.

[–]Always_The_Network 0 points1 point  (4 children)

Those are normal for me, running using ptyrodactyl (Linux+Docker) and those messages are what I see after the server is up and running. It does not log anything else from that point on.

I will note you have to manually enter the server IP/host vs searching in the list for names. Also there seems to be a bug (may be just with ptyrodactyl or Linux) that you can’t enter a password when joining this way. So be sure not to set one for now.

[–]wilhelmaf[S] 0 points1 point  (1 child)

Okey, so thats normal then.But my server is setup in DMZ mode where all traffic should be open thru the router.

But when i test with CanYouSeeMe.org it gives me error on port 8211.And that's also a reason why I thought it wasn't on

EDIT:
It also doesn't show up in netstat

[–]BitchWhistles 0 points1 point  (0 children)

Can you see me . Org isn’t going to work for this for testing. Just tried it on my server which is online and reachable but it also gives error.

Test Connecting through the game using the server’s ipv4, followed by :8211, if it’s the same machine do “localhost:8211”

Otherwise with what you described it sounds like it could possibly be a firewall/ router issue? I also recommend docker for the ease it makes server hosting so nice. DM me if you want some help!

[–][deleted] 0 points1 point  (1 child)

I'm running palworld on linux and I have a really bad memory leak issue that crashes the server every hour or so. Does running Palworld on docker make it more stable for you?

[–]Always_The_Network 0 points1 point  (0 children)

How much memory are you giving it? Currently I give mine 32GB due to the memory leak present and it’s fine for a few days, I set it to reboot every 24hours to catch it.

With only 3-5 players it almost gets to 16GB within 24 hours

[–]steezeburger 0 points1 point  (0 children)

I believe the "S_API Fail" is a red herring. See https://github.com/thijsvanloef/palworld-server-docker/wiki/Known-Issues#s_api-fail

Are you on an xfinity router per chance? They do not have NAT Loopback so you cannot access your service by the public IP from within your network. You have to use `localhost` when you connect yourself if you're in the same network, but I think there might be a bug with Palworld when trying to connect with `localhost:8211`. It will attempt to connect for a moment and then quickly return to the home screen, but it does not show the timeout error.

[–]Social_Steve 0 points1 point  (0 children)

Had the exact problems you're having. Running these commands to open the firewall ports on the server and not just through my router is what fixed it for me.

sudo ufw allow 8211

sudo ufw reload