502 Bad Gateway - Accessing Dashy on LXC via HTTPS/SSL, behind NGINX Proxy on different LXC? #1235
Unanswered
BlackrazorNZ
asked this question in
Help and Support
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
First of all, thanks for your work on Dashy - it's awesome - so much more fun to tinker with than other 'homepages' I've tried, and you even got me into learning how to YAML/JSON a bit which is an achievement for a crotchety old fart like me! :)
To my question: I have a small home server set up running Adguard, NGINX Proxy, Home Assistant, and now Dashy.
HA is on a VM and the others are on LXC's, all running on a Proxmox VE hypervisor.
All of the above works perfectly, and I can access everything except Dashy via the proxy using Lets Encrypt certificates generated on the NGINX Proxy.
I can also access Dashy just fine if I use the HTTP transport and point it at port 4000 on the Dashy LXC.
However, I cannot for the life of me get it working on HTTPS / SSL, even though I have the appropriate SSL cert setup just like the other hosts that are pointed at via HTTPS.
I have tried pointing at both ports 4001 and 443 (the indicated ports in the documentation), however I still get the 502 Bad Gateway error.
Do you know where I need to look, which port I need to point it at, or which setting I need to change to assign an appropriate port so that Dashy can listen to, and receive, certed HTTPS redirects from NGINX?
Many thanks for any help!
Beta Was this translation helpful? Give feedback.
All reactions