Selfhosted

41325 readers

385 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

Help Needed: Homepage Configuration – Missing Widgets & API Errors (caneandable.social)

submitted 12 hours ago* (last edited 12 hours ago) by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

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:

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

What I've Tried:

Separated service definitions (services.yaml) and widget configurations (widgets.yaml).
Updated widget URLs to use appropriate addresses (host IP for AdGuard, container names or Docker network IPs for containerized services).
Regenerated API keys for Portainer and Tailscale.
Verified all containers are on the same network (homepage_net).
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

top 3 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 11 hours ago* (last edited 11 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.

[–] [email protected] 1 points 12 hours ago (1 children)

Are any container logs reporting errors?

[–] [email protected] 1 points 10 hours ago

@NegativeLookBehind I updated the gist with some log files. There are a lot of 401 errors in the homepage logs. I know my API keys are correct so I'm not sure how to fix them.