01 First decide: missing listing or failed connection?
A Pine Hosting Palworld server can accept a direct connection and still be absent from Community search. Those are two different symptoms. Where your client supports direct IP, copy the full address and port from the Pine console’s Server Info area and attempt a connection. Pine’s official joining guide ↗ describes that address-copy workflow.
Do not replace the allocated port with a familiar default from another guide. If you cannot connect directly either, first examine startup errors and the allocated endpoint. If direct IP works, focus on Community registration, displayed name, platform and external advertisement. PS5 players need the Community path, so a successful PC direct connection alone is not complete acceptance.
02 Check the real startup configuration
Pocketpair’s documented Community mode adds -publiclobby. Pine also discusses it in its missing-server guide ↗. Use the startup controls your current panel actually exposes. We could not verify one universally named Pine “Community” toggle; if startup arguments are locked, ask support to confirm the effective launch command instead of searching for an invented menu.
For a self-managed native installation, the official Linux example is ./PalServer.sh -publiclobby. A managed Pine instance should be started through its own panel, not by launching an unmanaged second process. After a clean restart, check that the selected world and visible name are correct. Do not repeatedly wipe or reinstall the world to refresh a listing.
03 Use a small decision table, not a giant port list
| Observation | Next check |
|---|---|
| No one can join; console has startup errors | Fix the process or version first. |
| PC direct IP works; Community search fails | Confirm public-lobby mode, name and platform visibility. |
| Server appears; selecting it times out | Compare the advertised external endpoint with the actual allocation. |
| Only the owner’s home network fails | Test externally; the router may lack hairpin NAT. |
| Only one platform fails | Check its allowed-platform setting and current client build. |
These are diagnostic branches, not certain causes. Record a test result before moving to the next branch. For rented hosting, the provider controls the network edge; give support the allocation and evidence rather than trying to change your home router for a server located in their data centre.
04 Why PublicPort is not a listening-port fix
The official configuration reference ↗ describes PublicIP and PublicPort as Community advertisement values. PublicPort does not change the listener. If your host maps an external port to a different internal port, both sides must be consistent with that mapping. Ask support which values they supply automatically before overriding them.
The official Community server guide ↗ also notes the hairpin NAT limitation. Have a friend outside your LAN search the precise name and test joining, and note the client platform and time. There is no verified universal “wait exactly five minutes” rule, so do not present a guessed delay as a guarantee.
05 Send support a reproducible report
Include the server identifier, build, allocated address/port, configured name, whether direct connection succeeds, the client platform and a sanitized startup-log excerpt. Ask: “Is this instance starting with public-lobby mode, and does its advertised endpoint match the allocation?” Keep passwords and admin tokens out of screenshots.
For console joining, use the PS5 invitation checklist. If the question is actually camera zoom or FOV, that belongs to the local-client FOV guide; it is not evidence that Pine’s server discovery is broken.