Homepage can't ping anything

[rudex-it]

Description

I've set up Homepage 0.8.8 in Docker on 3 machines, let's call them A, B and C.

• A: Homepage runs within Docker on Debian, on bare metal.
• B: Homepage runs within Docker on OpenMediaVault (Debian based), on bare metal.
• C: Homepage runs within Docker in an LXC container, on Proxmox, on bare metal.

All three machines are connected to the same dumb Ethernet switch; same subnet, no VLANs.
Each of the machines run other services in Docker as well.
Proxmox runs multiple LXC containers which act as Docker hosts.
All LXC containers are based on the same template: debian-12-standard, version 12.2-1.

All three Homepage instances have the exact same copies of bookmarks.yaml, services.yaml, settings.yaml and widgets.yaml. The .yaml files are accessed and read correctly: all 3 web pages correctly display the same structure and content, including the background and icons, so no problem there.

Each service in services.yaml is set up with both the ping: and the siteMonitor: options.
Each service in services.yaml is set up exclusively with IP addresses, no host names whatsoever, so it's not DNS.

On machines A and B everything works fine. Service status in Homepage web app shows two green dots for each target service.
PROBLEM: On machine C, however, service status shows a red dot for ping: and a green dot for siteMonitor: for every service, regardless of where the target service is hosted (on A, B or C).

homepage version

v0.8.8

Installation method

Docker

Configuration

Homepage is running as a Docker container within an LXC container on a Proxmox server.

Container Logs

I've set up tabs within Homepage. This line repeats every time I switch to another tab:

[2024-02-22T07:47:23.647Z] debug: No containers were found with homepage labels.

Browser Logs

No response

Troubleshooting

Ping itself is not blocked. I've tried pinging A, B, C as well as some public Internet web sites from:

• Proxmox shell - it works
• Homepage's LXC's shell on Proxmox - it works
• another LXC's shell on Proxmox - it works
• docker exec -ti homepage sh on Homepage's LXC on C - ping works from here, too
• docker exec -ti homepage ping A_ip on Homepage's LXC on C - it works
• docker exec -ti homepage ping B_ip on Homepage's LXC on C - it works
• docker exec -ti homepage ping Proxmox_on_C on Homepage's LXC on C - it works
• docker exec -ti homepage ping Homepage_LXC_on_Proxmox_on_C on Homepage's LXC on C - it works
• docker exec -ti homepage ping another_LXC_on_Proxmox_on_C on Homepage's LXC on C - it works
• docker exec -ti homepage ping Homepage_LXC_on_Proxmox_on_C on another LXC on C - it works
• docker exec -ti homepage ping another_LXC_on_Proxmox_on_C on another LXC on C - it works

The only thing that can't ping other targets is the Homepage web application on C.

I've tried running with LOG_LEVEL environment variable set to debug, but couldn't figure anything out of that.

[shamoon]

Presumably it's related to the different installation methods (you wrote "bare metal" but also said homepage in docker, which is confusing).

In general homepage's ping is just a wrapper to try and use the ping command on the underlying host, we use https://github.com/danielzzz/node-ping to do that. So my guess is it cant reach the ping tool on C, for whatever reason

[rudex-it]

All three Homepage instances are running on Docker.
I wrote the whole chain down to the bare metal for each installation.
Sorry if I wasn't clear enough.

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.