[EDIT] - This appears to be resolved in the latest container version. I was one update behind and this had been happening for a month. After the latest update, issue vanished!
Been having a problem with "500 server error", but doesn't appear to match the others, and I think I have a bunch of info for tracking it down.
Issue occurs when adding a service, but not all services. Normal use of the Heimdall pages work fine, outside of adding services.
There are no logs of the failure in Heimdall's docker log, which made this take a bit to track down specifics
If I try to add a known service, it fails 100% of the time. Example, "AdGuard Home" with any address will give "500 server error." It gives the same error if I change it and try to save. This seems to be the key...it's as though it can't lookup the apps list, but all tests show it IS getting the DNS address and can reach it fine! If I try with something not in the apps list, it works, but not if the app is in the list.
If I exec into the container and ping appslist.heimdall.site, it works fine. Doesn't appear to be a resolution issue.
If I add "Test" as the service name and "http://127.0.0.1" as the address, it adds fine. No issue.
It used to work fine as-is, but below are the tests I ran to see if I was somehow causing this problem for myself.
I removed all cap_drop rules, thinking it was those causing the issue. Issue persists.
I removed no-new-privileges. Issue persists.
I removed specified gid/uid settings from the compose file. Issue persists.
I removed any resource restrictions. Issue persists.
I removed my specified DNS. Issue persists. Also, checked my DNS server, as I saw previous users had issues with the app address not resolving. DNS server is resolving the application list address so far as I can tell. Clicking "update app list" works fine. It's only adding or changing a service that fails.
Services added previously (back when it worked, despite no changes in config since then) work fine. It's just adding new ones or changing any part of the config for them that fails.
I started fresh and removed all config files. Even fresh install with no config has the same issues. This is the point where I began flipping tables.
[EDIT] - This appears to be resolved in the latest container version. I was one update behind and this had been happening for a month. After the latest update, issue vanished!
Been having a problem with "500 server error", but doesn't appear to match the others, and I think I have a bunch of info for tracking it down.
Docker compose attached below.
services: heimdall: image: lscr.io/linuxserver/heimdall:latest container_name: heimdall network_mode: bridge restart: on-failure:5 environment: