Fleet & Remote Tools

Link servers over SSH and run diagnostics on any node or ad-hoc IP, using a saved sudo password through the helper.

Unattended recovery

See resource and temperature history together

An enrolled server's Behaviour & History view keeps CPU, memory, disk and available temperature readings at five-minute resolution for up to 30 days. Temperature has its own Celsius scale so it remains readable beside percentage-based resource use. Reboot and watchdog markers stay aligned across the timeline, making it easier to connect a heat or load change with a recovery event.

Escalate only after service recovery is exhausted

Open a pinned server and expand Service Watchdog. The helper on that server should remain the first line of recovery: it checks the affected service and uses its bounded restart budget locally. FrontierStack's optional recovery ladder starts only after a new Recovery exhausted event. Old events and watchdog actions suppressed by the helper's own anti-loop rules are never replayed as a new reboot.

One reboot, then a guarded power cycle

Enable Reboot from FrontierStack to let the Mac issue one verified host reboot after the delay you choose. For the final step, link a controllable outlet in Power Control, select it in the server's watchdog panel, and set the full-outage timer. FrontierStack waits at least five minutes and cuts power only while the Mac's network is healthy and the server has no SSH, helper monitor, ping, ARP or watched service-port response. One incident can produce only one hard cycle.

Keep the final watch running without the Mac

A wedged server may be unable to control its own outlet. Choose a different, always-on enrolled server as the Recovery observer. Its updated FrontierStack helper probes the target's private address by ping and several TCP ports, so the final power watch continues while the Mac app is closed. Before cutting power it also requires a successful status response from the private power controller, saves an anti-loop receipt, and then waits until it has seen the target recover before another incident can be considered.

Treat power recovery as an emergency control. The observer receives no shell access and no credential for the watched server. It receives only the private target address, probe ports, timer and selected power-controller settings. A Home Assistant setup necessarily includes the selected entity and token; the helper stores this limited policy in protected root/system state. Target and controller addresses must be literal private, link-local or VPN IP addresses. Generic HTTP controllers need a separate status URL. Test the complete path during a maintenance window.

This is the web edition of FrontierStack's in-app Help. Open the same topic inside the app for live, clickable controls.

More help topics

• Getting started
• Hosting websites
• Databases & credentials
• Security & firewall
• SIEM & security data
• Alerts & remote notifications
• Automation, Shortcuts & Siri
• iPhone & iPad app
• Malware Audit
• The AI Administrator
• Agent platforms
• Presets & the sidebar
• Installing & connecting services