First identify the problem
An offline computer, a blank individual card and an empty computer menu are different problems. Check which parts still work before changing settings.
The computer is missing from the menu
- Open Manage systems and confirm it is listed and enabled.
- Confirm the saved name and address are correct.
- Use Test and fix any reported address or connection problem.
- Wait 15–30 seconds for target discovery, then refresh the widget.
The target is present but offline
- Confirm the computer is powered on and connected to the private network or VPN.
- Check that node exporter or windows_exporter is running.
- From the Prometheus computer, request the exporter /metrics address.
- Check the computer firewall permits the Prometheus server.
- Open Prometheus Targets and read the last scrape error when available.
Only some cards are blank
The selected exporter may not expose those measurements, or the required collector may be disabled. Hide unsupported cards or enable the appropriate exporter collector. A working CPU card alongside a blank Windows-service card normally means collection works but that specific metric is unavailable.
The wrong name appears
- Rename the target in Manage systems.
- Save or leave the name field as instructed by the widget.
- Wait for Prometheus file discovery to reload.
- Refresh HomeStart and select the renamed target again.
Connection refused or timed out
Good to know
- Connection refused usually means the address is reachable but no exporter is listening on that port.
- A timeout usually points to routing, VPN or firewall problems.
- An HTTP 404 often means the wrong path or a reverse proxy that does not pass /metrics.
- A TLS or certificate error means HTTPS was selected but the certificate cannot be validated.
Safe recovery order
- Do not expose the exporter publicly as a quick fix.
- Test locally on the monitored computer.
- Test from the Prometheus computer.
- Fix the private route or firewall.
- Retest in HomeStart, then wait for the next scrape.