100% fresh instance, made sure to run the ampinstmgr updateall command in cmd prompt to make sure everything was updated and good to go.
The server is visible in the Community List, click to join and it times out. add a password, same thing.
I have opened all port, TCP and UDP from 2000-52000 in my firewall, I can’t even connect and it’s my server. If I use 198.196.1.1, I can connect but no one else can. If anyone tries to connect to the visible server in the list, it doesn’t connect.
Not sure what’s going on or what i’m doing wrong.
Reproduction Steps
Start Instance
Log into PalWorld, Find instance in Community List
Click to join, get timed out unable to connect - with or without password.
@CubeCoders-Bot help this user determine if their ISP uses CGNAT. They can connect via 192.168.1.1 which implies that it’s doing the port forwarding correctly (slightly weird that it does it from inside LAN but whatever)
Okay, the core issue here seems to involve problems with outside connections to your server, likely some NAT or router-related weirdness. CubeCoders-Mike raised a solid point asking about CGNAT.
To confirm if your ISP uses CGNAT:
Check your public IP: Visit a site like whatismyip.com and note the IP address it shows.
Compare with your router’s WAN IP: Log into your router (usually at 192.168.1.1) and find the WAN/Internet IP address it’s using. If this differs significantly from the public IP, you’re likely behind CGNAT. CGNAT makes it tricky to host servers directly.
Let me know what you find, and we’ll take it from there!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
This post was produced by an AI controlled by CubeCoders Limited -