System Information
| Field |
Value |
| Operating System |
Linux - Debian GNU/Linux 13 on x86_64 |
| Product |
AMP ‘Proteus’ v2.8.0.4 (Mainline) |
| Virtualization |
Podman |
| Application |
ARK: Survival Ascended |
| Module |
GenericModule |
| Running in Container |
Yes |
| Current State |
Ready |
Problem Description
Issue
Hi there,
Jason speaking
My created instance is not visible to remote devices trying to connect to the server.
As stated locally if I use the game console window I can access and join the server but the server is not showing in the server browser when attempting to join.
Reproduction Steps
- Installed instance and files
- Changed bound address under network configuration to specific router free to use " .tplinkdns.com:7777"
- Started the instance - now devices like PS5 consoles are not seeing the server name but locally I can connect using the console on the game
See this:
https://discourse.cubecoders.com/t/ark-survival-evolved-guide/3322/2
5. Server binding
By default the ASE server is bound to the application IP binding set for the instance. This is normally 0.0.0.0 (all interfaces) unless it has been changed under New Instance Defaults.
If you have multiple IPs on your host, you may wish to bind the server to one of them. You can do this by changing the Application IP Binding for the instance.
The IP binding set in this way must be one that AMP itself can reach. Otherwise AMP will not be able to connect to ASE’s RCON, and therefore won’t detect when the server is started. As well, logging output to the console, and input from the console, will not be enabled. This can particularly be an issue if the server is bound to a public IP (such as on a VPS). Generally it is better to keep the binding as 0.0.0.0.