Challenges getting reverse proxy working with homebox
Challenges getting reverse proxy working with homebox
Question for folks and a note. I'm struggling with a similar issue as the one below for a couple of services so this may not just be a homebox item but rather a PEBKAC issue.
I've got NGINX proxy manager set up and directing to homebox. I'm using the sub-domain 'homebox.mydomain.tld' and have SSL certificates etc already configured for all sub domains. Homebox is configured to be accessed on port 3100 and is installed on a docker.
My docker containers are managed by portainer and so I've set the environment to access any of my containers via 'http://portainer.mydomain.tld/:
<port>
'. That works like a charm any time I go directly to that link. I then have configured 'homebox.mydomain.tld' to point to 'http://portainer.mydomain.tld:3100/' . It uses my SSL certificate but does not force ssl. I've also enabled websockets support. This however doesn't work and the access hangs.The reason I'm posting here to ask if I may have missed a configuration on homebox that is necessary is that other containers such as Photprism and Jellyfin which I use the same structure for work with no trouble. Anyone have some ideas you could share? Even if its an RTFM and you can point me to a good manual I'd be happy with the help.
So I'm still not sure why jellyfin and photoprism work but I have a theory that the problem is that nginx is deployed on my Asustor NAS. I've found a few things indicating that because the NAS requires ports 80 and 443, services like nginx struggle to capture the requests and route them correctly.
I did try mapping nginx to use 444 and 380 instead but was unsuccessful. I believe this is because incoming traffic is on the default port 80 http port. I don't know that its feasible to capture requests indicating my domain name and somehow have the NAS route only those through to inside the nginx container.
My next step will be trying to deploy nginx reverse proxy on a raspberry pi and then manage traffic from there.
Using the nginx reverse proxy manager on the Raspberry Pi has fully resolved my issue. The conflict of being hosted on the NAS was the problem. Hopefully this proves helpful to one or two other folks!
Glad you got it sorted!