1. Install Docker Probe
Deploy Docker Probe on a host that can reach the internal services and infrastructure connections you want to monitor.
Keep private services private
Many homelab services are intentionally hidden behind NAT or a firewall: NAS panels, Proxmox dashboards, Docker apps, Linux services, internal tools, and experiments that should never be public. Exposing those services to the internet just to let a cloud uptime checker reach them creates unnecessary risk.
OpsHome lets you keep those services private while still seeing whether they are up, down, recovering, or needing attention. Docker Probe runs where your private services are reachable, checks the Private Monitors you configure, and reports supported status to OpsHome Cloud over outbound HTTPS.
How private monitoring works
2. Connect outbound
The probe connects to OpsHome Cloud over outbound HTTPS. Your router does not need inbound port forwarding.
3. Configure Private Monitors
Add private HTTP, HTTPS, TCP Private Monitors or supported infrastructure connections for systems you own or are authorized to operate.
4. Review from iPhone
Use OpsHome NOC to review status, alerts, history, and infrastructure connection health when you are away from your desk.
No VPN required for status review
You may still use VPN for administration, SSH, and direct troubleshooting. OpsHome does not replace those tools. The difference is that checking whether your homelab is healthy should not require opening a laptop, connecting to a VPN, and clicking through several dashboards every time you leave home.
With Docker Probe, the iPhone app can show a quick operations view without your phone joining the private network. That makes it useful when you are commuting, traveling, or simply away from your desk and want to know whether the NAS, Proxmox host, Docker services, or internal app stack still looks healthy.
Private HTTP, HTTPS, and TCP checks
Use private monitors for internal services that should not be public. Common examples include NAS dashboards, Proxmox management pages, internal web apps, Docker services, home automation panels, personal APIs, and TCP services running inside your own network.
- Monitor only systems you own or are authorized to monitor.
- Keep administrative interfaces private instead of publishing them for cloud checks.
- Use local service discovery carefully and only on authorized network ranges.
- Pair private monitoring with normal firewall and credential hygiene.
Infrastructure connections and location grouping
Private monitoring becomes more useful when status is tied to the place or probe that can actually reach the target. OpsHome can associate Private Monitors and infrastructure connections with Docker Probe locations, so a Synology NAS, Proxmox node, Linux host, or Docker service can be understood in context instead of appearing as a disconnected list item.
This is especially useful for homelabs with more than one physical area or node: a rack, study, utility closet, remote home, or small lab segment. The goal is not to create a complex enterprise CMDB. It is to make the first question easy to answer: where is the problem likely happening?
Security boundaries
Private monitoring is safer than exposing management panels to the internet, but it is not a substitute for basic security discipline. Give Docker Probe only the access it needs. Use least-privilege credentials where integrations require credentials. Avoid scanning ranges you do not own. Keep your Docker host and network segmentation in good condition.
OpsHome does not need your NAS files, photos, documents, or payment card information for monitoring. The monitoring path is about supported status, health, and infrastructure signals, not personal file access.
FAQ
Do I need a VPN to use private monitoring?
No. OpsHome uses Docker Probe inside your network, so the iPhone app does not need to VPN into your home network just to review status.
Do I need to expose my home IP?
No. Docker Probe runs inside your network and connects outbound.
Can Private Monitors appear on public status pages?
Private Monitors should remain masked or excluded from public status pages unless explicitly designed otherwise.
Is this safer than port forwarding?
It avoids exposing private management panels directly to the internet, which is usually safer. You should still use least-privilege access and monitor only systems you own.
Does OpsHome replace my firewall or VPN?
No. OpsHome is a monitoring and operations view. Keep using proper firewall and VPN practices for administration.
Related OpsHome topics
Monitor private services without making them public
Install OpsHome NOC and use Docker Probe to review authorized private services from your iPhone.