Description: Unable to connect to server. So LOST

OS Name/Version: Ubuntu 24.04.2 LTS

Product Name/Version: ( AMP Release "Phobos"v2.6.1.2, built 25/03/2025 13:00)

Problem: Unable to connect to instance

Steps to reproduce:

  • Step 1- Installed AMP with docker
  • Step 2 - Created instance
  • Step 3 - Started instance
  • step 4- started server
  • step 5 - opened all ports for game in router (ubiquity Dream machine Pro)
  • step 6 - Tried to connect to public IP and failed
  • step 7 - can connect locally.

Actions taken to resolve so far:
Searched the support and did some troubleshooting with displaying the firewall ports and the instance. the instance has 0.0.0.0 for IP.
Rebooted router
Rebooted server.
Rebuilt instance
still can not connect.

Below is instance info
|OS |Linux|
|Platform —Debian GNU/Linux 12|
|System Type ----x86_64|
|Hardware Platform ----Gigabyte Technology Co., Ltd. AX370-Gaming K7|
|CPU Model |AMD Ryzen 7 1800X Eight-Core Processor|
|CPU Layout |1S/8C/16T|
|Installed RAM |32038|
|Virtualization |Docker|
|Network Mode |Host Mode|
|Module |GenericModule|
|Module Application |Seven Days To Die|
|Loaded Plugins |FileManagerPlugin, EmailSenderPlugin, WebRequestPlugin, LocalFileBackupPlugin, CommonCorePlugin, AnalyticsPlugin|
|Application Name |AMP|
|Application Version |2.6.1.2|
|Codename |Phobos|
|Tools Version |2.6|
|Release Stream |Mainline|
|Build Spec |Release|
|Build Date |25/03/2025 13:00|
|InstanceID |4342cd60-3ffd-479b-b7d7-de78b0a81e22|
|Last Executable |/AMP/seven-days-to-die/294420/7DaysToDieServer.x86_64|
|Last Arguments |-quit -batchmode -nographics -dedicated -configfile=serverconfig.xml -UserDataFolder=User|
|Last Process ID |106|

Below is Amp info

OS Linux
Platform Ubuntu 24.04.2
System Type x86_64
Hardware Platform Gigabyte Technology Co., Ltd. AX370-Gaming K7
CPU Model AMD Ryzen 7 1800X Eight-Core Processor
CPU Layout 1S/8C/16T
Installed RAM 32038
Virtualization None
Network Mode Standard
Module ADSModule
Module Application Application Deployment
Loaded Plugins FileManagerPlugin, EmailSenderPlugin, WebRequestPlugin, LocalFileBackupPlugin, CommonCorePlugin, AnalyticsPlugin
Application Name AMP
Application Version 2.6.1.2
Codename Phobos
Tools Version 2.6.1.2
Release Stream Mainline
Build Spec Release
Build Date 25/03/2025 13:00
InstanceID 5921bd05-cbff-41ca-9cb1-95274bc05b3f
Last Executable
Last Arguments
Last Process ID 786436

Check that you have NAT hairpin enabled in the UDM Pro and that your WAN address as shown in the UDM Pro isn’t in the range 100.64.x.x to 100.127.x.x

My ip is not in the range 100.64.x.x to 100.127.x.x and unify doc say hairpin NAT is already enabled.

Assuming this is home hosted - are you able to connect using a different device using your internal IP?

If you can connect locally using your internal IP, then it’s a port forwarding/NAT/hairpin issue. If you can’t, it’s an issue with the firewall on the machine AMP is running on.

Also what exactly happens when you try and connect?

When I try to connect from game to server 7d2d. tell me not found could not retrieve sever info. that is from out side. Do i need to create a NAT rule? I have used Steam CMD before and never had to change Nat route I just used port forwarding. and yes I can connect locally

Show your port forwarding rules

of course the x.x.x.x is to block out ip.

App Protocol Remote Port Dest External IP Local Port Interface
7D2D-Game Ports-TCP TCP/UDP Any 10.171.5.5:26900 x.x.x.x 26900 Primary (WAN1)
7D2D-Game Ports-Udp UDP Any 10.171.5.5:26901-26902 x.x.x.x 26901-26902 Primary (WAN1)

You are missing a forward. You need to forward at least:
26900 TCP/UDP (Server and Steam Port)
26901-26903 UDP (Server Port +1, +2, +3)

Assuming the default ports are allocated in AMP - adapt as needed

Also the external IP should be empty - by putting a value there you’re limiting it to connections only from that IP.

@Greelan When you say “Assuming the default ports are allocated in AMP” you are talking about the listening ports in the instance.

@Mike Yes Mike, in the instance is says 0.0.0.0:26900.I will assume that is what you are talking about

I’m talking about your port forwarding rules. I’m pretty sure you’ve unintentionally set it up so anyone can connect. Show us a screenshot of the Unifi settings, censoring out your external IP only.


Here you go

Okay that all looks fine - did you check what I said earlier whether a different device on the same network can connect using your Internal IP?