I want to set up Nginx proxy manager with the first party apps in TrueNAS. I’ve heard that TrueCharts dropped support, so I am stuck with that. However, I don’t see a way to make the container use a separate IP or use port 80 and 443. Does anyone know how to bypass these limitations? In core, npm had a different IP and therefore worked fine + no restrictions on port 80 and 443.
When I try to access my URL now with npm running, I am shown the TrueNAS GUI. If I change the ports from the GUI to something else, there is no connection. If I use port redirection on my router, nothing happens either
It works with custom apps. You can specify a static IP, no forwarding required, nothing on router either, just works. Probably a little docker experience useful (regarding the doc to figure out how). I don’t use nginx but caddy so can’t comment on the exact steps needed.
Of course, you can also keep using the Truecharts apps as is, little risk with “updates”. Then worry about it once Electric Eel comes out.
Alright I tried that with this docker jc21/nginx-proxy-manager which I’ve used before in Portainer. The setup seems pretty straight forward. I add my bridge to it, but it sits stuck on “deploying”. I’ve tried using DHCP and static IP, but it seems to make no difference and it is unreachable
Logs
Related Kubernetes Events
2024-08-12 01:09:50 Back-off restarting failed container ix-chart in pod nginx-pm-ix-chart-66bbbf7dc7-k5zqh_ix-nginx-pm(6a4003f4-d581-4082-92e5-66b948f0705c)
2024-08-12 01:09:37 Created container ix-chart
2024-08-12 01:09:37 Started container ix-chart
2024-08-12 01:09:36 Add eth0 [172.16.13.237/16] from ix-net
2024-08-12 01:09:36 Add net1 [192.168.88.32/24] from ix-nginx-pm/ix-nginx-pm-0
2024-08-12 01:09:36 Container image “jc21/nginx-proxy-manager:latest” already present on machine
2024-08-12 01:09:35 Scaled up replica set nginx-pm-ix-chart-66bbbf7dc7 to 1
2024-08-12 01:09:35 Created pod: nginx-pm-ix-chart-66bbbf7dc7-k5zqh
2024-08-12 01:09:35 Successfully assigned ix-nginx-pm/nginx-pm-ix-chart-66bbbf7dc7-k5zqh to ix-truenas
Pod logs
2024-08-12 01:16:00.101231+02:00e[1;34m❯ e[1;36mConfiguring npm user …e[0m
2024-08-12 01:16:00.326201+02:00useradd warning: npm’s uid 0 outside of the UID_MIN 1000 and UID_MAX 60000 range.
2024-08-12 01:16:00.502050+02:00e[1;34m❯ e[1;36mConfiguring npm group …e[0m
2024-08-12 01:16:00.612576+02:00e[1;34m❯ e[1;36mChecking paths …e[0m
2024-08-12 01:16:00.612792+02:00e[1;31m--------------------------------------e[0m
2024-08-12 01:16:00.612861+02:00e[1;31mERROR: /etc/letsencrypt is not mounted! Check your docker configuration.e[0m
2024-08-12 01:16:00.612951+02:00e[1;31m--------------------------------------e[0m
2024-08-12 01:16:00.615560+02:00s6-rc: warning: unable to start service prepare: command exited 1
2024-08-12 01:16:00.618903+02:00/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
And, it tells you why:
“ERROR: /etc/letsencrypt is not mounted! Check your docker configuration.e[0m”
So, you have to solve that, I do not run nginx. Generally, when running custom apps or docker containers soon, you need to get assistance from the creators site. I looked this one up for you, and it’s here:
This is not a truenas issue. When doing your own apps, it’s more on you to resolve any issues.
Also, stuck on deploying is not the issue. The issue is found in the pod log.
1 Like
Ah thanks, I completely overlooked that error message. Works perfectly fine now! For anyone wondering, this is what I had to do:
Exactly, glad you got it working but remember the pod logs.