| Field | Value |
|---|---|
| Operating System | Linux - Debian GNU/Linux 13 on x86_64 |
| Product | AMP ‘Proteus’ v2.8.0.0 (Mainline) |
| Virtualization | Docker |
| Application | Dune Awakening |
| Module | GenericModule |
| Running in Container | Yes |
| Current State | Ready |
Game server starts but can’t be connected to.
My understanding is that Funcom themselves released a broken update. This isn’t an issue with AMP. I also understand they have subsequently released another update that addresses the issue.
Is that true? It might be tho - I updated onto the new amp instance version yesterday. And I thought that the new version of the amp instance is producing that behavior.
AMP has no involvement in the connection process. If AMP gets the server up and running then by definition any problems that come up are an issue with the game itself.
Okay thank you for clarifying that. Then I gotta wait for a patch from funcom.
Thank you for the quick reply.
What it fixed for me was restarting the dune server instance and waiting a little longer.
Early in the startup process my server was marked as offline when trying to connect to the server.
I went to the experiment servers tab and when I clicked on my server - the sietch was still loading even if the starting screen of the game offered me the “continue” button.
(Edit) Important: If you look at the experimental servers tab too early. The sietch is listed even if the server is not ready. Wait at least 3-4 minutes after server start-up. Then check again.
When I waited and refreshed in the experimental servers tab long enough finally my sietch showed up.
When I clicked on the sietch to Join the server it was in the status READY.
Yeah that update was already out and installed on my instance when I made this post