If I set the "reverse proxy" feature in Synology disk drive, and both my Synology domain…
- User
If I set the "reverse proxy" feature in Synology disk drive, and both my Synology domain and the domain that is it referring to do have HTTPS certificate, how come if I put the "reverse proxy" url, the connection is no longer secure ?
Assistant
When you set up a reverse proxy in Synology DSM and notice that the connection is "not secure" (HTTPS warning) despite both domains having valid SSL certificates, the issue is likely due to one or more of the following reasons:
1. SSL Certificate Not Properly Configured for the Reverse Proxy
- The reverse proxy itself must have a valid SSL certificate for the public-facing domain (the one users access).
- Even if the backend server (the domain being proxied) has HTTPS, the reverse proxy must handle HTTPS termination.
- Solution:
- Go to Control Panel > Security > Certificate and ensure the correct certificate is assigned to the reverse proxy domain.
- If using Let's Encrypt, ensure auto-renewal is working.
2. Mixed Content (HTTP & HTTPS) Issues
- If the backend server serves some resources (images, scripts, CSS) over HTTP instead of HTTPS, browsers will mark the page as "not fully secure."
- Solution:
- Check the browser console (F12 > Console) for mixed-content warnings.
- Ensure all resources (APIs, images, etc.) are loaded via HTTPS.
3. Incorrect Reverse Proxy Settings (HTTP Instead of HTTPS Backend)
-
If the reverse proxy forwards requests to the backend server using HTTP instead of HTTPS, the connection between the proxy and backend is insecure.
-
Solution:
- In Control Panel > Application Portal > Reverse Proxy, ensure:
- Source Protocol:
HTTPS - Destination Protocol:
HTTPS(if the backend supports it) - Destination Port:
443(for HTTPS)
- Source Protocol:
Example Configuration:
Source: Protocol: HTTPS Hostname: yourdomain.com Port: 443 Destination: Protocol: HTTPS Hostname: internal.domain.com Port: 443 - In Control Panel > Application Portal > Reverse Proxy, ensure:
4. HSTS (HTTP Strict Transport Security) Issues
- If the backend enforces HSTS but the reverse proxy doesn’t, browsers may reject the connection.
- Solution:
- Ensure the reverse proxy correctly forwards HSTS headers or enforces HTTPS.
5. Certificate Chain or Trust Issues
- If the SSL certificate is self-signed or from an untrusted CA, browsers will warn.
- Solution:
- Use a trusted certificate (e.g., Let's Encrypt, commercial CA).
- Ensure intermediate certificates are properly installed.
6. Browser Cache or Redirect Loops
- Sometimes, old cached SSL errors persist.
- Solution:
- Clear browser cache or test in incognito mode.
- Check for redirect loops (e.g., HTTP → HTTPS → HTTP).
How to Debug:
- Check Browser Console (F12) for SSL errors or mixed-content warnings.
- Test with
curl -v https://your-reverse-proxy-domain.comto see certificate details. - Verify Synology Reverse Proxy Logs (
/var/log/nginx/reverse_proxy.log). - Use SSL Labs Test (https://www.ssllabs.com/ssltest/) to check certificate validity.
Final Fix:
- Ensure both the reverse proxy and backend use HTTPS.
- Assign the correct SSL certificate in Synology DSM.
- Check for mixed content or misconfigured headers.
If the issue persists, share the exact error message or logs for further diagnosis.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.