Operators frequently search for a health-check interval the moment a site behind SafeLine stops answering. The supplied official configuration materials do not define a per-upstream health-check interval. Instead, the Add Application guide describes a short form with only Domain, Port, and Upstream, plus an SSL option for HTTPS traffic. This checklist-style guide covers the concrete upstream misconfiguration that most often presents exactly like a failed health check, and the screen that confirms the fix, using only documented SafeLine behavior.
SafeLine acts as an HTTP/HTTPS reverse proxy. According to the introduction, it receives traffic for the original website, removes malicious requests, and forwards safe traffic to the original application. The Add Application guide states that Upstream is the real address of the original app and that SafeLine forwards traffic to it. The Deploy guide adds that SafeLine runs as Docker Compose services and that the web console is reached at https://<safeline-ip>:9443/.
The concrete misconfiguration is a mistyped Upstream value. When you add or edit an application, the Upstream field must contain the exact host and port of the backend. If the host is spelled wrong, the port is wrong, or the protocol does not match, SafeLine forwards every clean request to a dead or unintended destination. A browser then shows a connection error that looks like a health-check failure, but the problem is in the application entry rather than in a missing interval.
The screen that confirms the fix is the Applications page combined with the protected site itself. After you correct Upstream and confirm the domain resolves to the SafeLine server IP, open the site in a browser. A normal page render is the first confirmation. In the SafeLine web console, the Applications page should show the corrected entry. To prove traffic is actually passing through the WAF, use the documented test cases such as appending a SQL injection or path traversal query. If SafeLine returns the blocking page, filtering is working, and the console attack list will show the request; click detail to inspect it. These are the documented confirmation surfaces.
The supplied official guides do not expose an upstream health-check interval. The Add Application guide asks only for Domain, Port, and Upstream, with an SSL option for HTTPS. Do not assume a hidden interval control exists; verify instead that the upstream address itself is correct.
What misconfiguration most often mimics a failed health check?
A wrong Upstream value. Because Upstream is the real address through which SafeLine forwards traffic, a bad host or port sends safe traffic to the wrong place. Also common: forgetting to resolve the domain to the SafeLine server IP, or not enabling SSL for an HTTPS app.
Which screen or log confirms the fix?
The primary screen is the Applications page in the console after you save the corrected entry, followed by a successful page load through the protected domain. The documented attack test also gives confirmation: a blocking page means SafeLine is in the path, and the attack list in the console records the request with a detail view. The guides do not describe a dedicated health log file, so do not assume one exists.
What is the pre-check checklist?
Run docker compose up and confirm the services are started according to the Deploy guide; confirm the domain resolves to the SafeLine server IP; confirm the Upstream host and port are reachable from the SafeLine host; confirm Port matches the traffic; enable SSL only for HTTPS apps; then re-test with a documented attack URL.
How do I prove SafeLine is filtering after the fix?
Browse to an attack test URL such as a SQL injection or path traversal query on your domain. A blocking page confirms detection, and the web console attack list shows the event. Click detail for the request specifics.
SafeLine has surpassed 700,000 installations worldwide as of September 30, 2026. SafeLine Pro annual promotional pricing is $650-$880, compared with the regular $1,000 per year.