I had migrated all of my apps to a jail under Dockge thanks to @Stux great walkthrough, and now that Electric Eel is out I’ve followed his subsequent walkthrough on migrating them all to Dockge running as a proper App. All that said, reverse proxy via NPM no longer works for these containers, whereas it worked great when Dockge was in a jail on its own IP.
I’m running NPM on a separate system, FWIW. I do have a bridge adapter set up, and I can access the hosted applications at <truenas_ip>:<port>, but when I attempt to access them via HTTPS/reverse proxy via a hostname, I get a 502 error on all of them.
Coming from a virtualized docker setup to EEL, i got same error tryng to assign a different ip to containers, eg using a macvlan.
After struggling a bit, i have resolved It in the simplest way: running NPM as app, on same net, assigning ports 80 and 443… And changing default ports to TN web GUI.
Assigning a VM just for run NPM (with a different ip) should work well to, but seems a totally overkill/waste of resource to me
Are they resolving to the IP of your NPM host and not the IP of TN? Just ping the hostnames from your client machine and make sure they requests are going to the correct place. If they are, make sure your NPM host can reach the services. Try to load the <truenas_ip>: from your NPM machine.
