Private service checks
Monitor internal HTTP, HTTPS, and TCP services that should stay behind your firewall, such as dashboards, admin panels, self-hosted apps, and LAN-only service endpoints.
See inside your private homelab without opening ports
Most homelab services are intentionally private. Your NAS admin panel, Proxmox UI, internal apps, dashboards, Docker services, and Linux hosts usually sit behind NAT, a firewall, or a home router. That is good for security, but it makes normal cloud monitoring difficult because a cloud checker cannot reach Private Monitors that are not public.
Docker Probe solves that problem by running inside your network. It checks the services and infrastructure connections you authorize, then sends supported status and metrics back to OpsHome over outbound HTTPS. Your router does not need a public management port, and your private services do not need to become public just so you can review their state from your phone.
What Docker Probe does
Docker Probe is the bridge between OpsHome Cloud and your private homelab. It runs on a Docker host, reaches the Private Monitors you configure, and reports operational state to OpsHome. It is designed for quick review and alerting, not for taking control of your machines or replacing deeper administration tools.
Infrastructure context
Associate infrastructure connections with the Docker Probe that can reach them. This makes it easier to understand which local node, NAS, or server is responsible for a monitor or asset group.
Docker container state
When configured, Docker Probe can provide supported container state and event timeline data for restarts, recoveries, abnormal states, and OOM kills.
Location grouping
Use probe locations to group Docker Probes, infrastructure connections, and Private Monitors by rack, room, apartment, lab segment, or remote homelab site.
Outbound-only by design
Docker Probe does not accept inbound requests from the internet. It should only be given access to the networks and services you explicitly want to monitor. This matters because many homelab operators run sensitive management surfaces, including NAS panels, Proxmox dashboards, container control panels, and private apps that should not be exposed publicly.
Outbound-only monitoring is not magic security. You still need normal firewall practices, least-privilege credentials where integrations require credentials, and careful scope control for local discovery. The important distinction is that OpsHome does not ask you to publish your private management interfaces to the internet as a monitoring workaround.
The generated Compose file uses the official OpsHome image with the latest tag for simple updates. OpsHome publishes the current digest for verification; digest pinning is optional for users who want stricter image control and are ready to update the digest manually.
docker run -d --name opshome-probe \
-e OPSHOME_API_URL=replace-with-opshome-api-url \
-e OPSHOME_PUBLIC_USER_ID=replace-with-user-id \
-e OPSHOME_PROBE_NAME=replace-with-probe-name \
-e OPSHOME_PROBE_BOOTSTRAP_TOKEN=replace-with-bootstrap-token \
opshomenoc/opshome-noc:latestAfter the probe connects, configure Private Monitors and infrastructure connections in OpsHome. Only scan or monitor networks, services, and systems you own or are authorized to operate.
What you can monitor
- Internal HTTP and HTTPS services inside your network.
- TCP services you own or are authorized to monitor.
- NAS panels, self-hosted dashboards, and internal admin pages.
- Docker containers and supported container health or event states.
- Supported infrastructure integrations connected through a specific probe.
- Synology, Proxmox, and Linux assets when configured through supported integrations.
OpsHome presents this information as an iPhone-first operations view. The goal is to answer the practical question quickly: is everything still running, and which part of the homelab needs attention?
FAQ
Does Docker Probe require port forwarding?
No. Docker Probe uses outbound connections and does not require opening inbound ports to your home network.
Where should I install Docker Probe?
Install it on a Docker host that can reach your private services, such as a NAS, mini PC, Linux server, or homelab node.
Can Docker Probe scan any network?
No. Only use discovery and monitoring on networks, services, and systems you own or are authorized to monitor.
Does Docker Probe replace Prometheus or Grafana?
No. OpsHome is a lightweight NOC-style operations view for homelab operators. It can complement deeper observability stacks.
Does Docker Probe access my personal files?
OpsHome does not need your NAS files, photos, documents, or payment card information for monitoring. Grant only the minimum access needed for supported status and infrastructure checks.
Related OpsHome topics
Use Docker Probe from your iPhone NOC view
Install OpsHome NOC, deploy Docker Probe inside your network, and start monitoring authorized private services without opening inbound ports.