Bug: GoAway GUI will not start after reboot - Proxmox

[KingHunter2019]

Describe the bug
When rebooting, cloning, or restoring GoAway, the GUI is inaccessible. The same goes for restoring a Snapshot or a backup, compressed or not.

To Reproduce
Steps to reproduce the behavior:

1. Go to the Goaway container (created from Proxmox Helper Script)
2. Click on reboot, issue a command reboot, or restore a backup for a new container
3. Like any Virtual Machine or Container, the CLI will come up in Proxmox. — Totally Normal.
4. The error begins when you go back to the container GUI IP address (or domain from reverse proxy). It will not load.

Expected behavior
Getting back to the Default Interface.

Screenshots & Logs
See how a restored container, even with a different IP, will not show the Web GUI.

Please complete the following information:

• Platform: Proxmox version 8.4.14
• LXC created from helper scripts: https://community-scripts.github.io/ProxmoxVE/scripts?id=goaway&category=Adblock+%26+DNS
• GoAway Version: 0.62.6

[pommee]

Have you verified that the service is running after a reboot?
systemctl status goaway

What does the logs say?
cat /var/log/goaway.log

[KingHunter2019]

Have you verified that the service is running after a reboot? systemctl status goaway

I created a New Container for Testing. Please see below:

Able to Access CLI for Credentials:

I tested some queries, looks good so far.

Issued Reboot via CLI:

After rebooting, the Page has gone blank:

Command Issued: systemctl status goaway

What does the logs say? cat /var/log/goaway.log

Strangely, I get a few errors. I haven't added anything to it yet.

[pommee]

Looks like the order of the log gets mangled for both of us once it has been restarted. Though I don't see the same behavior on my end. Runs fine after a reboot.

Are you still able to make DNS queries after the reboot?

[KingHunter2019]

Looks like the order of the log gets mangled for both of us once it has been restarted. Though I don't see the same behavior on my end. Runs fine after a reboot.

Ah, just my luck, Lol.

Are you still able to make DNS queries after the reboot?

Yup, no issues there, thankfully.

[KingHunter2019]

Looks like the order of the log gets mangled for both of us once it has been restarted. Though I don't see the same behavior on my end. Runs fine after a reboot.

Ah, just my luck, Lol.

Are you still able to make DNS queries after the reboot?

Yup, no issues there, thankfully.

I've found a solution; running a "systemctl restart goaway" allowed the GUI to return.

Log 1 (After using Reboot at CLI):

Log 2 (Issuing command: "systemctl restart goaway"):

Log 2, starting at 13:28:12, confirms the issue was resolved because it successfully logs:

2025/09/30 13:28:12 [INFO] Web interface available at http://Go-Away-IP:8080 (In this case: 10.0.5.179)

The system was finally able to resolve its IP address as 10.0.5.179, allowing the application to complete its initialization and successfully announce the full address for the Web interface. This suggests the network had fully stabilized or the server was simply restarted after a minimal waiting period, allowing the IP to be correctly identified.

Given the [ERROR] Error getting IP address: server IP not found occurs, is there a way to implement a retry loop or a configurable delay before attempting the IP lookup? This could mitigate race conditions on systems where network interfaces initialize slowly.

[pommee]

Added some failover for this in v0.62.9. Should hopefully resolve the issue.

[nalexxx]

In v0.62.11 the issue still persists: the GUI is empty after an LXC reboot. Restarting the service fixes it.

[DannyFeliz]

I can confirm that the issue is still present in v0.62.9

[pommee]

Noted. Will spend some time testing with an LXC container once the rewrite I am working on is finished.

[0xDedSec42]

Google just lead me here, I've got the same issue with v0.62.20.