[Enhancement Request] Document Apache Reverse Proxy Settings #901

New issue

Closed

opened 2026-02-20 11:08:44 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 11:08:44 -05:00

Owner

Originally created by @tkedwards on GitHub (Oct 20, 2025).

I've started using Heimdall with an Apache reverse proxy. I needed to search the web and even use ChatGPT to find the right settings, which don't seem to be documented in one place anywhere. I'm using the Docker image and the Apache r-proxy is running on the Docker host machine, with Heimdall Docker running on 10080 on that Docker host.

I was getting a problem where no CSS or scripts would load. These are the fixed settings that reverse-proxy Heimdall properly:

<VirtualHost *:80>
    ServerName example.com
    ServerAlias www.example.com

    # Automatic redirect to https, see https://wiki.apache.org/httpd/RedirectSSL
    Redirect / https://www.example.com/
</VirtualHost>

<VirtualHost *:443>
    ServerName example.com
    ServerAlias www.example.com

    SSLEngine on

    # Proxy to Heimdall
    ProxyPass / http://127.0.0.1:10080/ retry=0 timeout=5
    ProxyPassReverse / http://127.0.0.1:10080/

    ProxyPreserveHost On
    ProxyRequests Off

    # Fix cookie & path issues
    ProxyPassReverseCookieDomain 127.0.0.1 www.example.com
    ProxyPassReverseCookiePath / /

    # Critical: make Heimdall aware of HTTPS
    RequestHeader set X-Forwarded-Proto "https"

    # Optional security headers
    Header always set X-Frame-Options SAMEORIGIN
    Header always set X-Content-Type-Options nosniff
    Header always set Referrer-Policy strict-origin-when-cross-origin

    # SSL certificate from Let's Encrypt
    SSLCertificateFile  /etc/ssl/_wildcard.example.com/cert.pem
    SSLCertificateKeyFile /etc/ssl/_wildcard.example.com/privkey.pem

    #   Server Certificate Chain:
    #   Point SSLCertificateChainFile at a file containing the
    #   concatenation of PEM encoded CA certificates which form the
    #   certificate chain for the server certificate. Alternatively
    #   the referenced file can be the same as SSLCertificateFile
    #   when the CA certificates are directly appended to the server
    #   certificate for convinience.
    SSLCertificateChainFile /etc/ssl/_wildcard.example.com/fullchain.pem

</VirtualHost>

Originally created by @tkedwards on GitHub (Oct 20, 2025). I've started using Heimdall with an Apache reverse proxy. I needed to search the web and even use ChatGPT to find the right settings, which don't seem to be documented in one place anywhere. I'm using the Docker image and the Apache r-proxy is running on the Docker host machine, with Heimdall Docker running on 10080 on that Docker host. I was getting a problem where no CSS or scripts would load. These are the fixed settings that reverse-proxy Heimdall properly: ``` <VirtualHost *:80> ServerName example.com ServerAlias www.example.com # Automatic redirect to https, see https://wiki.apache.org/httpd/RedirectSSL Redirect / https://www.example.com/ </VirtualHost> <VirtualHost *:443> ServerName example.com ServerAlias www.example.com SSLEngine on # Proxy to Heimdall ProxyPass / http://127.0.0.1:10080/ retry=0 timeout=5 ProxyPassReverse / http://127.0.0.1:10080/ ProxyPreserveHost On ProxyRequests Off # Fix cookie & path issues ProxyPassReverseCookieDomain 127.0.0.1 www.example.com ProxyPassReverseCookiePath / / # Critical: make Heimdall aware of HTTPS RequestHeader set X-Forwarded-Proto "https" # Optional security headers Header always set X-Frame-Options SAMEORIGIN Header always set X-Content-Type-Options nosniff Header always set Referrer-Policy strict-origin-when-cross-origin # SSL certificate from Let's Encrypt SSLCertificateFile /etc/ssl/_wildcard.example.com/cert.pem SSLCertificateKeyFile /etc/ssl/_wildcard.example.com/privkey.pem # Server Certificate Chain: # Point SSLCertificateChainFile at a file containing the # concatenation of PEM encoded CA certificates which form the # certificate chain for the server certificate. Alternatively # the referenced file can be the same as SSLCertificateFile # when the CA certificates are directly appended to the server # certificate for convinience. SSLCertificateChainFile /etc/ssl/_wildcard.example.com/fullchain.pem </VirtualHost> ```

deekerman

2026-02-20 11:08:44 -05:00

closed this issue
added the
no-issue-activity

closed-issue-activity
labels

deekerman commented

2026-02-20 11:08:45 -05:00

Author

Owner

@LinuxServer-CI commented on GitHub (Nov 19, 2025):

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@LinuxServer-CI commented on GitHub (Nov 19, 2025): This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

deekerman commented

2026-02-20 11:08:46 -05:00

Author

Owner

@LinuxServer-CI commented on GitHub (Feb 17, 2026):

This issue is locked due to inactivity

@LinuxServer-CI commented on GitHub (Feb 17, 2026): This issue is locked due to inactivity