starred/Heimdall-linuxserver

Fork 0

mirror of https://github.com/linuxserver/Heimdall.git synced 2026-03-03 00:26:56 -05:00

Traefik Reverse Proxy #72

New issue

Closed

opened 2026-02-20 11:15:10 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-20 11:15:10 -05:00

Owner

Originally created by @gi8lino on GitHub (Feb 16, 2018).

I use Traefik as reverse proxy. I cannot add a URL. I get ther error:
Mixed Content: The page at 'https://domain.com/' was loaded over HTTPS, but requested an insecure script 'http://domain.com/js/app.js'. This request has been blocked; the content must be served over HTTPS.
If I forward port 443 to Heimdall, I get "502 Bad Gateway".

Originally created by @gi8lino on GitHub (Feb 16, 2018). I use Traefik as reverse proxy. I cannot add a URL. I get ther error: `Mixed Content: The page at 'https://domain.com/' was loaded over HTTPS, but requested an insecure script 'http://domain.com/js/app.js'. This request has been blocked; the content must be served over HTTPS.` If I forward port 443 to Heimdall, I get "502 Bad Gateway".

deekerman closed this issue

2026-02-20 11:15:11 -05:00

deekerman commented

2026-02-20 11:15:13 -05:00

Author

Owner

@aptalca commented on GitHub (Feb 16, 2018):

when you do port 443, also use https so it's proxied to
https://heimdall:PORT (where port is 443 or whatever you mapped that to)

@aptalca commented on GitHub (Feb 16, 2018): when you do port 443, also use https so it's proxied to https://heimdall:PORT (where port is 443 or whatever you mapped that to)

deekerman commented

2026-02-20 11:15:13 -05:00

Author

Owner

@gi8lino commented on GitHub (Feb 16, 2018):

now I get a "500 Internal Server Error"
I set these labels:

"traefik.enable=true"
"traefik.frontend.rule=Host:heimdall.domain.com"
"traefik.backend=heimdall"
"traefik.port=443"
"traefik.protocol=https"

PS: I run Heimdall in the official linuxserver/heimdall container...

@gi8lino commented on GitHub (Feb 16, 2018): now I get a "500 Internal Server Error" I set these labels: - "traefik.enable=true" - "traefik.frontend.rule=Host:heimdall.domain.com" - "traefik.backend=heimdall" - "traefik.port=443" - "traefik.protocol=https" PS: I run Heimdall in the official linuxserver/heimdall container...

deekerman commented

2026-02-20 11:15:13 -05:00

Author

Owner

@KodeStar commented on GitHub (Feb 18, 2018):

v1.4.1 hopefully fixes a lot of reverse proxy issues, so probably worth giving that a go.

@KodeStar commented on GitHub (Feb 18, 2018): v1.4.1 hopefully fixes a lot of reverse proxy issues, so probably worth giving that a go.

deekerman commented

2026-02-20 11:15:13 -05:00

Author

Owner

@gi8lino commented on GitHub (Feb 18, 2018):

great, it works now!

@gi8lino commented on GitHub (Feb 18, 2018): great, it works now!

deekerman commented

2026-02-20 11:15:13 -05:00

Author

Owner

@vikramgorla commented on GitHub (Aug 15, 2018):

Spent a lot time of figuring out the fix, this github issue was the first hit in google.

I had the same issue and the fix was as in below ticket
https://github.com/linuxserver/Heimdall/issues/187

Container labels for heimdall container

        traefik.frontend.rule:  Host:heimdall.${domain}
        traefik.port: 443
        traefik.protocol: https

IMPORTANT config to make this work is to add below line in traefik.toml config file as heimdall uses self signed certificates by default and it is OK behind traefik (note that this config is applied at traefik level for all backends, so know the impact if you have other container/.. backends where you dont want to trust certificates by default)

insecureSkipVerify = true

@vikramgorla commented on GitHub (Aug 15, 2018): Spent a lot time of figuring out the fix, this github issue was the first hit in google. I had the same issue and the fix was as in below ticket [https://github.com/linuxserver/Heimdall/issues/187](https://github.com/linuxserver/Heimdall/issues/187) Container labels for heimdall container ``` traefik.frontend.rule: Host:heimdall.${domain} traefik.port: 443 traefik.protocol: https ``` IMPORTANT config to make this work is to add below line in traefik.toml config file as heimdall uses self signed certificates by default and it is OK behind traefik (note that this config is applied at traefik level for all backends, so know the impact if you have other container/.. backends where you dont want to trust certificates by default) `insecureSkipVerify = true`

deekerman commented

2026-02-20 11:15:13 -05:00

Author

Owner

@KodeStar commented on GitHub (Aug 15, 2018):

Thanks for adding some useful information, hopefully it will help anyone else having the same issue.

@KodeStar commented on GitHub (Aug 15, 2018): Thanks for adding some useful information, hopefully it will help anyone else having the same issue.

deekerman referenced this issue

2026-02-20 11:21:14 -05:00

Problems Re-Editing Jellyfin #398