[Support] Linuxserver.io - Heimdall

[Mystic]

2 hours ago, CorneliousJD said:

 

If you aren't a fan of command line you can just edit it via going to \appdata\heimdall\www and then opening the .env file with a text editor of your choice and editing it there. 

 

I put in https://sub.domain.com and saved it, restarted container, and I'm good to go now again.

 

Thanks @CorneliousJD, vi vs. GUI....  I hate to say for me GUI all the way.  

 

To understand...  there is only one file in the directory that is a .env?  

 

So example file could be Idontknow.env.....  vi opens the correct file because it is the only .env file in the directory BUT if the directory had 2 files with the .env extension I would have to specify file I wanted to edit...  How's my logic???

 

Thanks for the GUI tip.

 

[CorneliousJD]

On 1/7/2022 at 12:52 PM, Mystic said:

 

Thanks @CorneliousJD, vi vs. GUI....  I hate to say for me GUI all the way.  

 

To understand...  there is only one file in the directory that is a .env?  

 

So example file could be Idontknow.env.....  vi opens the correct file because it is the only .env file in the directory BUT if the directory had 2 files with the .env extension I would have to specify file I wanted to edit...  How's my logic???

 

Thanks for the GUI tip.

 

 

In that directory there's only one file that is .env (no filename, just .env extension)

 

\appdata\heimdall\www\.env 

[CorneliousJD]

So it seems the root cause of this issue is NGINX Proxy Manager (NPM) issue as noted here: https://github.com/jc21/nginx-proxy-manager/issues/1717

 

I would say the real fix here is to roll back until they fix the problem.

2.9.13 seems to work fine.

 

If you're using the jlesage NPM image, you can add :v1.23.1 to the end of the docker image it pulls to downgrade, and that fixes the issue as well.

 

When NPM fixes the problem itself, this .env modification we are talking about shouldn't be needed anymore.  

[TauTX]

On 1/3/2022 at 1:25 PM, Drahakar said:

Heimdall stop working with Nginx Reverse Proxy. In LAN is everything okay. Looks like CSS ist broken. 

 

*edit* i open the console from the docker /var/www/localhost/heimdall/ open wie vi  ".env" and change the host from http://localhost to http://SUBDOMAIN.DOMAIN - reboot the docker. 

 

This worked for me as well. Very helpful!

[Groto]

I made this change to make Heimdall work with NginxProxyManager, but now none of the dynamic apps work anymore, so I don't see the extra info on each of the heimdall tiles. Any ideas? My apps use https://subdomain.domain for the URL on each one instead of the IP address. 

[Mancunian]

For anyone stumbling across this after battling with SWAG, 502 errors etc.

 

I appreciate this is an old thread, but with lots of conflicting info out there, the answer for my issues was in the documentation.
 

The resolver.conf file had generated before I'd set up the custom network.

 

https://docs.linuxserver.io/general/swag - Search this page for 502

 

502

This error means that nginx can't talk to the application. There is a few common reasons for this:

The application and SWAG is not on the same custom docker network

Further up we talk about how to set up Docker networking, however there are some other common traps

The container name does not match the application name.

Covered in the section for Understanding the proxy conf structure

You manually changed the port.

Also covered in the section for Understanding the proxy conf structure

The container originally ran with host networking, or the default bridge.

In most cases the contents of /config/nginx/resolver.conf; should be ...resolver 127.0.0.11 valid=30s;, if this is not the case, you can:

Delete it, and restart the container to have it regenerate

Manually set the content(we wont override it)

Hope this helps someone, if nothing else, it will help future me should I have to do this again!

[Arbadacarba]

I'm not running a reverse proxy - I just want simple access from within my network so that my wife can quickly have links available for external cameras and the baby monitor... Plus give myself a launching point for all my internal servers and dockers.

 

I am playing with the idea of putting many of my dockers on their own IP addresses so that they can be accessed by name and without having to enter port numbers.

 

 

It seems to work, except that the advanced apps give errors on testing and if already configured they just do not show any live data. 

 

[Arbadacarba]

Aaannnd Found It

 

I guess the trick is not to read through the relevant thread, it's to read through ALL the threads.

[Danny Goh]

my current heimdall has been defacement. showing a guy d**k. the heimdall dont have any external access. 

 

any idea how to troubleshoot? just afraid my unraid has been exposed.

[xyzeratul]

On 3/1/2022 at 11:24 AM, Groto said:

I made this change to make Heimdall work with NginxProxyManager, but now none of the dynamic apps work anymore, so I don't see the extra info on each of the heimdall tiles. Any ideas? My apps use https://subdomain.domain for the URL on each one instead of the IP address. 

 

me too, once it go tho NPM, none of dynamic app info can be displayed, could not even test the connection in config

[Spyderturbo007]

I just updated a few minutes ago to the latest version and now when I navigate to the WebUI, it's just a white screen.  Everything is gone.  I'm at a loss on how to fix it.  I tried restarting the container a few times, but no luck.

Edited November 27, 2022 by Spyderturbo007

[Danuel]

hi,

 

don't know when this happened but Haimdall does not display stats for qbittorrent anymore (you should be able to see On the icon Upload/Download speeds, also search engine does not appear on the page

Edited December 3, 2022 by Danuel

[WarHawk8080]

Not sure if I set a password or not...but can't make changes, keep getting the 

 

These credentials do not match our records

These credentials do not match our records

 

Is there a way to remove/reset/change that password...all I have in 

/mnt/user/appdata/heimdall

is

root@MOBIUS:/mnt/user/appdata/heimdall# ll
total 4.0K
drwxr-xr-x 1 nobody users  83 Feb  3 06:42 ./
drwxrwxrwx 1 nobody users 236 Feb 15 20:05 ../
-rw-r--r-- 1 nobody users  48 Feb  3 06:42 .migrations
drwxr-xr-x 1 nobody users  38 Feb  3 06:42 keys/
drwxr-xr-x 1 nobody users  70 Feb 19 02:00 log/
drwxrwxr-x 1 nobody users 193 Feb 19 18:31 nginx/
drwxr-xr-x 1 nobody users  44 Feb  3 06:42 php/
drwxr-xr-x 1 nobody users 162 Feb 19 18:31 www/

 

[WarHawk8080]

Just deleted the container and the directory...reinstalled...uggh

[BigDanT]

Hi All,

 

I've just updated unraid from 6.11.5 to 6.12.4 and everything has come back up fine other than my Hemidall container that causes an 

 

Execution error

Server error

 

whenever i try and restart the container. I've tried deleting the container and reinstall but thats not helped.

 

Has anyone else had this problem ?

 

I've attached the logs which I hope will help.

 

Cheers

 

D.

 

EDIT - OK, its defo to do with the second port 443, when i change this it runs but unraid wont load the web address. any help greatly appreciated

neo-diagnostics-20230912-2025.zip

Edited September 13, 2023 by BigDanT

[InVisibleGoD]

You are not alone, I have the exact same problem! Anyone?