Skip to content
The Chat Archive
command-a-03-2025· Cohere LMArena Human Preference 140K

If I set the "reverse proxy" feature in Synology disk drive, and both my Synology domain…

  1. 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 ?

  2. Assistant

    When setting up a reverse proxy on a Synology DiskStation, ensuring that the connection remains secure (HTTPS) depends on several factors, especially when both the Synology domain and the target domain have valid HTTPS certificates. If the connection is showing as "not secure" after setting up the reverse proxy, here are some potential reasons and troubleshooting steps:

    1. Certificate Mismatch or Misconfiguration

    • Issue: The reverse proxy might not be correctly forwarding the HTTPS certificate or could be using the wrong certificate.
    • Solution: Ensure that the reverse proxy is configured to use the correct HTTPS certificate for the domain. In Synology's Reverse Proxy settings, verify that the certificate for the source domain (the one users access) matches the domain they are using.

    2. Mixed Content Issues

    • Issue: The target server might be serving resources (e.g., images, scripts) over HTTP instead of HTTPS, causing mixed content warnings.
    • Solution: Check the target server for any hardcoded HTTP links and update them to HTTPS. Use browser developer tools to identify and fix mixed content issues.

    3. HSTS (HTTP Strict Transport Security)

    • Issue: If the target domain has HSTS enabled, browsers may refuse to connect over HTTP, even if the reverse proxy is not properly configured for HTTPS.
    • Solution: Ensure the reverse proxy is correctly configured to handle HTTPS requests and that the certificate is trusted by browsers.

    4. Synology Certificate vs. Target Certificate

    • Issue: If the Synology NAS is using its own certificate for the reverse proxy, but the target server has a different certificate, browsers might flag the connection as insecure due to certificate mismatch.
    • Solution: Use the same certificate for both the Synology reverse proxy and the target server, or ensure the Synology NAS is properly configured to forward the target server's certificate.

    5. Reverse Proxy Configuration Error

    • Issue: Incorrect settings in the Synology Reverse Proxy configuration, such as wrong port forwarding or protocol mismatch.
    • Solution: Double-check the reverse proxy settings:
      • Ensure the Source and Destination protocols are both set to HTTPS.
      • Verify the ports (typically 443 for HTTPS).
      • Confirm the target server's hostname and IP address are correct.

    6. Certificate Chain Issues

    • Issue: The certificate chain might not be properly trusted by the client's browser.
    • Solution: Ensure the certificate is issued by a trusted Certificate Authority (CA) and that the intermediate certificates are properly installed.

    7. Self-Signed Certificates

    • Issue: If either the Synology NAS or the target server is using a self-signed certificate, browsers may flag the connection as insecure.
    • Solution: Use a trusted CA-issued certificate for both the Synology NAS and the target server.

    8. Browser Cache

    • Issue: The browser might be caching an old or incorrect certificate.
    • Solution: Clear the browser cache and try accessing the site again.

    Steps to Fix:

    1. Verify Certificates: Ensure both the Synology NAS and the target server have valid, trusted HTTPS certificates.
    2. Check Reverse Proxy Settings: Confirm that HTTPS is selected for both the source and destination in the Synology Reverse Proxy settings.
    3. Test Target Server: Directly access the target server via HTTPS to ensure its certificate is working correctly.
    4. Use Let's Encrypt: If possible, use Let's Encrypt certificates for both the Synology NAS and the target server to ensure compatibility.
    5. Review Logs: Check Synology and target server logs for errors related to HTTPS or certificates.

    By addressing these potential issues, you should be able to restore the secure connection when using the reverse proxy.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.