Help with Reverse Proxy - Letsencrypt + Heimdall

  • Lots of interesting things going.
    Are you using an apple device?
    Do you have your hard drives attached vis usb and trying to do zfs? There is a warning that says it doesn’t work if you try to do via usb.

  • Lots of interesting things going.
    Are you using an apple device?
    Do you have your hard drives attached vis usb and trying to do zfs? There is a warning that says it doesn’t work if you try to do via usb.

    Yes, I've repurposed an old Macbook and drive is attached via USD. No ZFS at all.
    If I am honest, I was using this setup more as a sandbox for testing out OMV, Plex, the various plugins and how to reverse proxy.
    More as a dry run before I invest in a more permanent setup. So I know that this setup is far from ideal for my use case.

  • The usb drive is one of the problems.


    Try running OMV in a virtual machine, then you can test and learn as much as you want.


    I do the same as you. I am using lots of old hardware. I have OMV running on a raspberry pi, a netbook, a old business laptop, old gaming pc and a server, but not a MacBook. I am thinking of building a hackintosh though with a Nuc that I just got. :thumbup:

  • The usb drive is one of the problems.


    Try running OMV in a virtual machine, then you can test and learn as much as you want.


    I do the same as you. I am using lots of old hardware. I have OMV running on a raspberry pi, a netbook, a old business laptop, old gaming pc and a server, but not a MacBook. I am thinking of building a hackintosh though with a Nuc that I just got. :thumbup:

    Will try VM - it's something I havent dabbled with yet, so want learn.
    Good luck with the hackintosh - let me know how you get on!

  • @denny2k2 I found your idea to have a heimdall dashboard as a starting page intriguing. So i tried to set it up myself and first hit the same point as you. In my case I solved the problem of the "bad gateway" endpoint by joining the letsencrypt and heimdall docker in a network. My letsencrypt docker was already in a network called my-net together with the nextcloud docker (following TechnoDadLife's tutorials). So I added the extra argument --network my-net to the heimdall docker. After that i could reach heimdall over a subdomain of my duckdns account -> e.g. https://heimdall.mydomain.duckdns.org

  • @denny2k2 I found your idea to have a heimdall dashboard as a starting page intriguing. So i tried to set it up myself and first hit the same point as you. In my case I solved the problem of the "bad gateway" endpoint by joining the letsencrypt and heimdall docker in a network. My letsencrypt docker was already in a network called my-net together with the nextcloud docker (following TechnoDadLife's tutorials). So I added the extra argument --network my-net to the heimdall docker. After that i could reach heimdall over a subdomain of my duckdns account -> e.g. https://heimdall.mydomain.duckdns.org

    You sly dog!
    That was actually on my "to try" list.
    Glad that it worked for you. Will give it a bash myself.

  • I'd like to password protect this also - but I think we should just tackle one thing at a time haha.

    This is pretty forward. According to the info page:


    Adding password protection


    This image now supports password protection through htpasswd. Run the following command on your host to generate the htpasswd file docker exec -it heimdall htpasswd -c /config/nginx/.htpasswd <username>. Replace with a username of your choice and you will be asked to enter a password. New installs will automatically pick it up and implement password protected access. Existing users updating their image can delete their site config at /config/nginx/site-confs/default and restart the container after updating the image. A new site config with htpasswd support will be created in its place.


    Btw: my heimdall.subdomains.conf contains this line at the end: proxy_pass https://$upstream_heimdall:443;

  • Well, what i found is that the new network "my-net" is not necessary, this not only for Heimdall but for Letsencrypt and Nextcloud too, it's just enough to leave each container in bridge mode forwarding the ports of each container so to don't have one in conflict with someone else;
    So, for Heimdall, to don't have the "Bad Gateway" error, you need to change the last line in the file heimdall.subdomain.conf like this:


    proxy_pass https://$upstream_heimdall:443;


    change in


    proxy_pass http://yourServerIP:HTTP-Port-Forwarded;


    or if you prefer the https port


    proxy_pass https://yourServerIP:HTTPS-Port-Forwarded;


    Save the file, restart Letsencrypt and that's all


    :)

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!