Support

Help with Ping Light.

Ping Light monitors the HTTP endpoints you configure from a focused menu-bar popover on macOS.

Your first useful check

Add a website or HTTP API you are authorised to check. Choose the request method, expected status, timeout and interval.
Run a check. Compare the result with the expected HTTP status; a response is not automatically a successful check.
Leave the app running for another scheduled check. The Mac must be awake and able to reach the endpoint.

Only test failure and recovery against an endpoint you control or have permission to use. Do not deliberately interrupt somebody else's production service.

No notification arrived

Allow Ping Light in System Settings → Notifications, check alert settings in the app, and check Focus / Do Not Disturb. Notification delivery is controlled by macOS. A failed request in history does not itself prove that a visible notification was delivered.

Check the configured failure threshold and cooldown: not every repeated failure creates another alert. Recovery must follow a previously reported failure under the endpoint's settings.

Sleep, offline and local networks

Ping Light is not a cloud monitor. It cannot keep checking while the app is closed or the Mac sleeps. A missed period does not mean that the server was healthy during that period. After waking, confirm that checks resume and your connection is available.

For private-network endpoints, allow Local Network access when macOS requests it, verify the VPN / network route, and confirm the address works from this Mac. Local Network controls vary by macOS version. A denial is a permission problem, not necessarily an endpoint outage.

For automatic startup, enable launch at login in the app and verify it in macOS Login Items. Do not rely on scheduled checks until you have confirmed that the app has started.

Authentication and request errors

Re-enter expired credentials in the endpoint editor. Basic-auth passwords and bearer tokens are kept in macOS Keychain. A 401 / 403 response can indicate authentication or authorisation failure; a DNS error, timeout, TLS error or redirect has a different cause. Check the result rather than treating every failure as the same problem.

Share a configuration safely

Keychain credentials are not exported in configuration JSON. However, a URL's query string, a manually supplied header or a POST body may contain a secret. Review and redact exports yourself before sharing. Credentials may need to be entered again after import.

Before contacting support

Confirm that the endpoint opens from the same Mac and network connection.
Check the expected HTTP status, request method, timeout, and redirect setting in the endpoint rule.
Use the app's recent results to note the error message and time of the failed check.

Contact

Email admin@raindigit.ie with “Ping Light support” in the subject line. Include the macOS version, Ping Light version, and a short description of the issue.

Never email endpoint passwords, bearer tokens, or private URLs. Redact them from screenshots and logs before sharing.

Privacy

Read the Ping Light Privacy Policy for the app's local-first data handling.