Hi guys,
I’m struggling with getting NPM to do its job on its dedicated IP on the new eel version. I used the Kubernetes version back then, using a static IP address to have just the NPM as my ingress as it’s just plain simple for my LAN.
So after the update, “nothing works ™” and I started to look into the networking. To get things back on track, I added an IP address to the interface and limited the web UI to the other one so that we do not get a port conflict there.
In the NPM container, I set the newly set IP to be handled by the portal (after figuring out the hard way) and pointed my DNS accordingly.
So npm.homelab was pointing to the NPM, proxying its admin interface of port 81 through itself.
Port 80 and 443 are portals with an app path of / to get the job done - in theory.
Now as I go to https://npm.homelab, the login page shows as expected - but as soon as it tries to access some path like /login, stuff breaks.
Any idea on how to get around this dilemma?
I mean, my dream setup would be truenas being able to handle the internal reverse proxying itself and offer some basic ssl termination for apps like PiHole…
Thanks in advance as I’m running out of ideas.
Edit: add a linebreak for readability, s/for/on/ in topic.