Is there an existing issue for this?
Current Behavior
Recently updated to the most recent version (v2.8.1-ls357) and noticed that my dashboard is trying to load objects from the local IP instead of the web address, e.g. https://heimdall.mydomain.net.
I'm using Caddy reverse proxy (plug-in to OPNsense). I have 19 more subdomains serviced by the same and no issues, so I don't expect this to be a configuration or cert. issue.
Once I click on any link and accepted the self-signed cert for the http://192.168... - it loads the objects and page seems like expected, but of course the browser is showing "Not Secure".
The workarounds I found for me:
- Directing my reverse proxy to HTTP instead of HTTPS
- Using an older version of the Docker image. I noticed that the last one that works for me is v2.7.6-ls352
Expected Behavior
No response
Steps To Reproduce
in the compose file, with:
`image: lscr.io/linuxserver/heimdall:latest` - I had the described issue
`image: lscr.io/linuxserver/heimdall:v2.7.6-ls352` - I don't have the issue
Environment
- OS:Ubunt 24.04 (arm64)
- How docker service was installed: as per the official doc - https://docs.docker.com/engine/install/ubuntu/
CPU architecture
arm64
Docker creation
---
services:
heimdall:
image: lscr.io/linuxserver/heimdall:latest
container_name: heimdall
environment:
- PUID=1000
- PGID=1000
- TZ=America/New_York
- ALLOW_INTERNAL_REQUESTS=false #optional
volumes:
- ./config:/config
ports:
- 88:80
- 444:443
restart: unless-stopped
Container logs
✔ Network heimdall_default Created 0.1s
✔ Container heimdall Created 0.0s
Attaching to heimdall
heimdall | [migrations] started
heimdall | [migrations] 01-nginx-site-confs-default: skipped
heimdall | [migrations] 02-default-location: skipped
heimdall | [migrations] done
heimdall | ───────────────────────────────────────
heimdall |
heimdall | ██╗ ███████╗██╗ ██████╗
heimdall | ██║ ██╔════╝██║██╔═══██╗
heimdall | ██║ ███████╗██║██║ ██║
heimdall | ██║ ╚════██║██║██║ ██║
heimdall | ███████╗███████║██║╚██████╔╝
heimdall | ╚══════╝╚══════╝╚═╝ ╚═════╝
heimdall |
heimdall | Brought to you by linuxserver.io
heimdall | ───────────────────────────────────────
heimdall |
heimdall | To support LSIO projects visit:
heimdall | https://www.linuxserver.io/donate/
heimdall |
heimdall | ───────────────────────────────────────
heimdall | GID/UID
heimdall | ───────────────────────────────────────
heimdall |
heimdall | User UID: 1000
heimdall | User GID: 1000
heimdall | ───────────────────────────────────────
heimdall | Linuxserver.io version: v2.8.1-ls357
heimdall | Build-date: 2026-07-24T19:49:25+00:00
heimdall | ───────────────────────────────────────
heimdall |
heimdall | using keys found in /config/keys
heimdall | **** The following active confs have different version dates than the samples that are shipped. ****
heimdall | **** This may be due to user customization or an update to the samples. ****
heimdall | **** You should compare the following files to the samples in the same folder and update them. ****
heimdall | **** Use the link at the top of the file to view the changelog. ****
heimdall | ┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
heimdall | │ old date │ new date │ path │
heimdall | ├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
heimdall | │ 2024-07-16 │ 2026-06-27 │ /config/nginx/site-confs/default.conf │
heimdall | │ 2024-05-27 │ 2025-12-26 │ /config/nginx/nginx.conf │
heimdall | │ 2023-08-13 │ 2026-06-27 │ /config/nginx/ssl.conf │
heimdall | └────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
heimdall | New container detected, installing Heimdall
heimdall | [custom-init] No custom files found, skipping...
heimdall | [ls.io-init] done.
Is there an existing issue for this?
Current Behavior
Recently updated to the most recent version (v2.8.1-ls357) and noticed that my dashboard is trying to load objects from the local IP instead of the web address, e.g. https://heimdall.mydomain.net.
I'm using Caddy reverse proxy (plug-in to OPNsense). I have 19 more subdomains serviced by the same and no issues, so I don't expect this to be a configuration or cert. issue.
Once I click on any link and accepted the self-signed cert for the http://192.168... - it loads the objects and page seems like expected, but of course the browser is showing "Not Secure".
The workarounds I found for me:
Expected Behavior
No response
Steps To Reproduce
in the compose file, with:
Environment
CPU architecture
arm64
Docker creation
--- services: heimdall: image: lscr.io/linuxserver/heimdall:latest container_name: heimdall environment: - PUID=1000 - PGID=1000 - TZ=America/New_York - ALLOW_INTERNAL_REQUESTS=false #optional volumes: - ./config:/config ports: - 88:80 - 444:443 restart: unless-stoppedContainer logs