Egg: ARK: Survival Ascended
File: ark_survival_ascended/egg-ark-survival-ascended.json
**Issue Description:
ASA server no longer displays correctly in the server browser after the latest update
Since the latest ARK: Survival Ascended update, our dedicated server no longer displays correctly in the in-game server browser while using the official Pterodactyl ASA Egg.
The server starts successfully, all required ports are open, and the server is reachable. However, the server browser does not display the server correctly anymore.
Environment
Official Pterodactyl ASA Egg
Docker Image: ghcr.io/ptero-eggs/steamcmd:proton
Running under Proton
Latest ARK: Survival Ascended server version
Latest Steam client version
Map: Valguero
Expected Behavior
The server should appear normally in the Unofficial server browser.
The server should display its correct ping.
The build version should be displayed.
The server should remain visible after refreshing the server list.
Actual Behavior
The server starts successfully.
The server initially appears in the Unofficial server browser.
The server reports:
Ping: 0
Build: ---.--
The server is sometimes displayed as greyed out.
After refreshing the server list, the server disappears completely.
Players are no longer able to reliably discover the server through the browser.
What has already been verified
UDP game port is open.
UDP query port is open and listening.
Docker port mappings are correct.
UFW firewall rules are configured correctly.
The server binds to all configured ports successfully.
No startup errors or crashes occur.
The issue started immediately after the latest ASA update.
The same configuration worked correctly before the update.
Additional Information
The only way right now is to join via the console using the open <ip> command without a password. But that's not an option for a server with restricted access.
The server log contains the following message:
Initializing Steam Subsystem for server validation.
Steam Subsystem initialized: FAILED**
Egg: ARK: Survival Ascended
File: ark_survival_ascended/egg-ark-survival-ascended.json
**Issue Description:
ASA server no longer displays correctly in the server browser after the latest update
Since the latest ARK: Survival Ascended update, our dedicated server no longer displays correctly in the in-game server browser while using the official Pterodactyl ASA Egg.
The server starts successfully, all required ports are open, and the server is reachable. However, the server browser does not display the server correctly anymore.
Environment
Official Pterodactyl ASA Egg
Docker Image: ghcr.io/ptero-eggs/steamcmd:proton
Running under Proton
Latest ARK: Survival Ascended server version
Latest Steam client version
Map: Valguero
Expected Behavior
The server should appear normally in the Unofficial server browser.
The server should display its correct ping.
The build version should be displayed.
The server should remain visible after refreshing the server list.
Actual Behavior
The server starts successfully.
The server initially appears in the Unofficial server browser.
The server reports:
Ping: 0
Build: ---.--
The server is sometimes displayed as greyed out.
After refreshing the server list, the server disappears completely.
Players are no longer able to reliably discover the server through the browser.
What has already been verified
UDP game port is open.
UDP query port is open and listening.
Docker port mappings are correct.
UFW firewall rules are configured correctly.
The server binds to all configured ports successfully.
No startup errors or crashes occur.
The issue started immediately after the latest ASA update.
The same configuration worked correctly before the update.
Additional Information
The only way right now is to join via the console using the
open <ip>command without a password. But that's not an option for a server with restricted access.The server log contains the following message:
Initializing Steam Subsystem for server validation.
Steam Subsystem initialized: FAILED**