Help Needed: Homepage Configuration – Missing Widgets & API Errors

Hi everyone,

I’m running Homepage (v0.10.9) in Docker on Arch Linux ARM (Stormux) and encountering issues with missing widgets and API errors. Some widgets are showing as “Missing” on the dashboard, and I’m seeing repeated HTTP 401 errors for Portainer and Tailscale in the logs.

Setup Details:
- Homepage Version: v0.10.9
- Host OS: Arch Linux ARM (Stormux)
- Host IP: 192.168.1.137
- Docker Network: All containers are on homepage_net (gateway: 172.23.0.1)
- Docker Containers: Homepage, Portainer, Miniflux, Uptime Kuma, Glances, etc.

Issues:

  1. Several widgets showing as “Missing”:
    - AdGuard (running on host, not in Docker)
    - Netdata
    - Uptime Kuma
    - Docker
    - Portainer
    - Miniflux
    - Tailscale
  2. Repeated HTTP 401 errors for Portainer and Tailscale in logs.

What I’ve Tried:

  1. Separated service definitions (services.yaml) and widget configurations (widgets.yaml).
  2. Updated widget URLs to use appropriate addresses (host IP for AdGuard, container names or Docker network IPs for containerized services).
  3. Regenerated API keys for Portainer and Tailscale.
  4. Verified all containers are on the same network (homepage_net).
  5. Enabled debug logging in Homepage.

Configuration Files:
I’ve uploaded my configuration files here: https://gist.github.com/Lanie-Carmelo/e01d973bc3b208e5082011e4b76532f6.
API keys and passwords have been redacted.

Any help troubleshooting this would be greatly appreciated! Let me know if you need additional details.

Hashtags & Mentions:
#SelfHosting #Linux #ArchLinux #Docker #HomeLab #OpenSource #WebDashboard #ArchLinuxARM
@selfhosted @linux @docker @opensource @selfhosting @selfhost

  • @just_another_personEnglish
    2•12 hours ago

    Sure sounds like you’re running in bridged mode and your container doesn’t know it.

    Edit, yeah, I just your configs. Things are kind of crazy. If you’re going to use compose, use the internal networking and don’t try to route out to IPs that are host-based. You can simplify this so much by just using the internal docker network. If you NEED to talk to the host for some reason, don’t do it over API, and use a socket instead. If THAT isn’t an option, make sure your network has named DNS hosts, and use those instead of IP addresses.