A certificate renewal can succeed on disk while visitors still receive the old certificate. Before searching for how to replace WAF SSL certificate files and refresh them, establish which server actually presents the certificate to the browser. Replacing a valid certificate at the wrong endpoint will not change what visitors see.
For SafeLine, the supplied documentation supports a topology and verification checklist, but it does not document certificate file locations, certificate upload controls, or a certificate refresh command. This guide therefore avoids prescribing file replacements or service reloads that those sources do not establish.
The concrete misconfiguration: replacing the upstream certificate only
Consider this troubleshooting scenario: a public hostname routes through SafeLine to an application server. An administrator replaces the certificate on that application server, then opens the public website and still sees the previous certificate in the browser's certificate viewer.
The deployment target was wrong for the intended outcome: the administrator updated the upstream server while expecting the public HTTPS endpoint to present a different certificate.
SafeLine's application guide describes it as an HTTP/HTTPS reverse proxy that receives website traffic and forwards accepted traffic to the original application. Its application configuration distinguishes the domain, the port SafeLine listens on, and the upstream application's real address. Those are separate configuration concerns. Source: SafeLine application guide
In a deployment where client TLS terminates at the WAF, the browser inspects the certificate presented at that termination point. Updating an upstream certificate alone does not replace that public-facing certificate. This is a general TLS distinction, not a documented SafeLine certificate-management procedure.
Trace the request before replacing more files
Start with the exact hostname visitors use. Record the certificate currently displayed by the browser, including its subject alternative names, issuer, expiration date, and fingerprint. Compare these with the intended replacement certificate. An expiration date alone is weaker evidence than a fingerprint comparison.
Next, inspect the application's configuration in SafeLine. The official guide directs administrators to the Applications page and documents three relevant settings:
- Domain identifies the application's hostname or address.
- Port identifies the port SafeLine listens on; HTTPS applications require the SSL option.
- Upstream identifies the original application's real address.
The guide also instructs administrators to resolve the configured domain to the SafeLine server's IP address. Check that relationship before assuming a certificate refresh failed. A browser reaching another server cannot confirm a change on the intended WAF. Source: SafeLine application configuration
Also distinguish the protected website from the administration console. The deployment guide documents the console at https://<safeline-ip>:9443/. Inspecting that address does not establish which certificate the public application hostname presents. Source: SafeLine deployment guide
Correct the target, then use the browser screen as evidence
For the example above, the corrective decision is to update the certificate at the actual public TLS termination point. Use a certificate-management procedure verified for your installed version and deployment. The supplied sources do not establish the SafeLine-specific steps, so neither an internal path nor a reload command can responsibly be inferred from them.
After completing that verified procedure, establish a fresh connection to the public hostname. Open the browser's certificate viewer and compare the presented certificate's fingerprint with the replacement certificate. Confirm that its names cover the hostname and that the browser reports no certificate validation error.
That certificate screen is the concrete evidence that resolves this scenario: before correction, it shows the previous certificate; afterward, it shows the intended replacement. A successful file copy or a healthy upstream response cannot establish the same result.
Finally, load an ordinary application page. Certificate identity and application availability are separate checks, and both matter after a change.
Does replacing the upstream certificate refresh the public certificate?
Only if that upstream is the endpoint presenting the certificate to the client. First map the actual TLS termination points. Do not assume the upstream and the public listener share certificate configuration.
Which SafeLine application setting should I check for HTTPS?
The official application guide says to check the SSL option for HTTPS applications and configure the listening port. It does not describe that option as a certificate renewal or refresh mechanism. Source: SafeLine application guide
Which command refreshes SafeLine certificate files?
The supplied official documents do not specify one. They also do not identify certificate storage paths. Obtain the procedure applicable to your installed version before changing internal files or restarting services.
What confirms that the fix worked?
A fresh connection to the intended public hostname must present the replacement certificate. Verify its fingerprint, hostname coverage, and validity in the browser's certificate viewer, then confirm that the application loads normally.
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.