Connectivity Problem with Icarus - Server discoverable from external network

System Information

Field Value
Operating System Linux - Debian GNU/Linux 12 on x86_64
Product AMP ‘Callisto’ v2.5.1.2 (Mainline)
Virtualization Docker
Application Icarus
Module GenericModule
Running in Container Yes
Current State Ready

Problem Description

Issue

I’m trying to host ICARUS from Amp. The instance is created an running. I’m able to discover the server via lan wen connected to the same network, however, when connect to an external network (using my phone’s hotspot) i’m un able to discover the server. I’m using opnsense as my router and firewall. I suspect I have something configured wrong for port forwarding but could use some guidance.

Reproduction Steps

  • Install Amp
  • Create Icarus instance
  • Search dedicated servers via ip:27015 (using address from whatismyipaddress.com)

@CubeCoders-Bot can you take a crack? My guess is CGNAT because he mentioned a hot spot in which case it’s a no-go.

Alright, let’s dig into this connectivity puzzle! :globe_with_meridians:

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

  1. 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.

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

  1. 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! :rocket:


:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.