AdGuard Addon Starts but button for WebUI is missing

I am running HAOS on a Pi. I recently installed the AdGuard add-on, and while the logs indicate it starts successfully, the button to launch the Web UI never appears in the add-on page, and the Start link persists. Basically, it looks like HA doesn’t think the add-on is starting, while the process clearly has. The logs indicate the server is running at ‘http://127.0.0.1:45158’ but I’m not able to access it.

Not positive about this, but when I initially installed it I believe it showed a successful start state in the HA UI. However, I realized that I should have setup HA with a static IP, so I shut down the add-on and did that. When I tried to restart, it was in this current state.

I’ve uninstalled and reinstalled the add-on, and I’ve restarted HA. The logs always look fine, other than seeing it sometimes say ‘adguard is already running’ if I attempt to start it again, since the UI is inaccurate.

Any ideas appreciated!

Here are the logs

2023/07/20 23:30:57 [error] Couldn't get logging settings from the configuration: yaml: unmarshal errors:
  line 3: cannot unmarshal !!str `1.1.1.1:53` into []string
2023/07/20 23:30:57.521156 [info] AdGuard Home, version v0.107.34
2023/07/20 23:30:57.521183 [info] AdGuard Home updates are disabled
2023/07/20 23:30:57.521977 [info] home.upgradeSchema0to1(): called
2023/07/20 23:30:57.522027 [info] deleting /data/adguard/dnsfilter.txt as we don't need it anymore
2023/07/20 23:30:57.522445 [info] home.upgradeSchema1to2(): called
2023/07/20 23:30:57.522468 [info] deleting /data/adguard/Corefile as we don't need it anymore
2023/07/20 23:30:57.522520 [info] home.upgradeSchema2to3(): called
2023/07/20 23:30:57.522552 [info] home.upgradeSchema3to4(): called
2023/07/20 23:30:57.522571 [info] home.upgradeSchema4to5(): called
2023/07/20 23:30:57.522581 [info] Upgrade yaml: 5 to 6
2023/07/20 23:30:57.522591 [info] Upgrade yaml: 6 to 7
2023/07/20 23:30:57.522600 [info] Upgrade yaml: 7 to 8
2023/07/20 23:30:57.522612 [info] Upgrade yaml: 8 to 9
2023/07/20 23:30:57.522622 [info] Upgrade yaml: 9 to 10
2023/07/20 23:30:57.522631 [info] Upgrade yaml: 10 to 11
2023/07/20 23:30:57.522643 [info] Upgrade yaml: 11 to 12
2023/07/20 23:30:57.522653 [info] Upgrade yaml: 12 to 13
2023/07/20 23:30:57.522662 [info] Upgrade yaml: 13 to 14
2023/07/20 23:30:57.522674 [info] Upgrade yaml: 14 to 15
2023/07/20 23:30:57.522687 [info] Upgrade yaml: 15 to 16
2023/07/20 23:30:57.522699 [info] Upgrade yaml: 16 to 17
2023/07/20 23:30:57.522710 [info] Upgrade yaml: 17 to 18
2023/07/20 23:30:57.522722 [info] Upgrade yaml: 18 to 19
2023/07/20 23:30:57.522732 [info] Upgrade yaml: 19 to 20
2023/07/20 23:30:57.522742 [info] Upgrade yaml: 20 to 21
2023/07/20 23:30:57.522752 [info] Upgrade yaml: 21 to 22
2023/07/20 23:30:57.523005 [info] Upgrade yaml: 22 to 23
2023/07/20 23:30:57.523058 [info] Upgrade yaml: 23 to 24
2023/07/20 23:30:57.538143 [info] tls: using default ciphers
2023/07/20 23:30:57.556468 [info] safesearch default: reset 253 rules
2023/07/20 23:30:57.569148 [info] Initializing auth module: /data/adguard/data/sessions.db
2023/07/20 23:30:57.580737 [info] auth: initialized.  users:0  sessions:0
2023/07/20 23:30:57.580813 [info] web: initializing
2023/07/20 23:30:57.590780 [info] dnsproxy: cache: enabled, size 4096 b
2023/07/20 23:30:57.591030 [info] dnsproxy: max goroutines is set to 300
2023/07/20 23:30:57.600033 [info] AdGuard Home is available at the following addresses:
2023/07/20 23:30:57.600346 [info] go to http://127.0.0.1:45158
2023/07/20 23:30:57.608293 [info] dnsproxy: starting dns proxy server
2023/07/20 23:30:57.608481 [info] Ratelimit is enabled and set to 20 rps
2023/07/20 23:30:57.608570 [info] The server is configured to refuse ANY requests
2023/07/20 23:30:57.608641 [info] dnsproxy: cache: enabled, size 4194304 b
2023/07/20 23:30:57.608717 [info] dnsproxy: max goroutines is set to 300
2023/07/20 23:30:57.608842 [info] dnsproxy: creating udp server socket 127.0.0.1:53
2023/07/20 23:30:57.609114 [info] dnsproxy: listening to udp://127.0.0.1:53
2023/07/20 23:30:57.609215 [info] dnsproxy: creating tcp server socket 127.0.0.1:53
2023/07/20 23:30:57.609438 [info] dnsproxy: listening to tcp://127.0.0.1:53
2023/07/20 23:30:57.609868 [info] dnsproxy: entering udp listener loop on 127.0.0.1:53
2023/07/20 23:30:57.609915 [info] dnsproxy: entering tcp listener loop on 127.0.0.1:53
[23:30:58] INFO: Starting NGinx...
2023/07/20 23:30:58.602687 [info] filtering: saving contents of filter 1 into "/data/adguard/data/filters/1.txt"
2023/07/20 23:30:58.603190 [info] filtering: updated filter 1: 1041195 bytes, 53553 rules
2023/07/20 23:30:58.603291 [info] filtering: updated filter 1; rule count: 53553 (was 0)
[23:30:58] INFO: Successfully send discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

Force refresh your browser

Thanks for the suggestion. No luck unfortunately. I see it across browsers and devices as well.