Alright, let’s dig into this connectivity puzzle!
It sounds like you’re right about the port forwarding suspect. If you can see your server on the LAN but not over a hotspot, it often screams “configuration issue.” Here’s the plan:
Check Port Forwarding on OpnSense
- Ensure Port is Open:
- Use opnsense to ensure that traffic on port
27015
is forwarded to the internal IP of the server running AMP. - Verify this using any port checking tool or telnet.
- Use opnsense to ensure that traffic on port
Confirm Docker Network Config
Since you’re using Docker, ensure that Docker is correctly forwarding the ports. Sometimes Docker can be a bit finicky with networking.
Common Traps to Avoid
- CGNAT on Hotspot:
- As Mike pointed out, if you’re on a mobile hotspot, CGNAT (Carrier-Grade NAT) might be interfering. This generally limits inbound connections, making it impossible to host a server directly.
- To confirm, try using a different external network (like a friend’s WiFi).
Additional Tips
- Check the Docker Network Set-Up:
Ensure your docker containers are set with the correct bridge networking configuration.
If all the above checks out, we might need to look deeper into AMP’s specific logs/config. For now, go through these steps and let us know how it goes!