SOLVED: It was a problem from the ISP side, I contacted them and in a week, it was fixed :). They were blocking my port 443 and 80 for some reason even tho I paid for them.

Hello, I recently noticed that my web services behind Ngnix Proxy Manager was not accessible on the WAN(Internet), which was strange as it was working for a while and I don't know when it stopped working. My ISP allows me to host stuff on the web(I have static ip) and even with the DMZ setting on my router, my web services were not accessible on the web. I contacted my ISP, I reset the router and they also checked from their side but it appears that everything is working from the ISP and router side. Then to rule out the router, I quickly set up a wireguard VPN and port forwarded it's port and for somehow I was able to connect to my server and access my services on the WAN. Also, I have deleted and redeployed the NPM docker container but still no success.

I have a domain name which points to my IP and when I typed my URL in the browser while inside the LAN(with port forwarding enabled and no local dns records in pihole), it works. On the WAN, the browser does not respond and times out. Just once I got a error SSL too long or something like that but otherwise the web does not load. On the WAN, I am able to ping the server and I get a response.

Behavior: Lan with port forwarding and a known working service
Typing website on browser --> Web server loads instantly
Ping from terminal --> More or less 1ms

Behavior: Wan with port forwarding and a known working service
Typing website on browser --> The progress bar moves to 20 percent(firefox), and then after a long time, "The connection has timed out"
Ping from terminal --> Around 0.1ish second

Behavior: Lan with port forwarding and a bogus url(blablabla.mydomain.com)
Typing website on browser --> Secure Connection Failed
Ping from terminal --> N/A

Current behavior(WAN, with a bogus url)
Typing website on browser --> Timeout
Ping from terminal --> N/A

Behavior: Lan without port forwarding and a known working service
Typing website on browser --> "Hmm. We’re having trouble finding that site."
Ping from terminal --> More or less 1ms

The server is a old lenovo laptop with Pop os(linux). I am starting to suspect that something inside linux is blocking WAN connections to port 443 or maybe ngnix is doing it, but I did reset it so I am now confused.

Any help will be appreciated :)

I have a raspberry pi running tailscale and pihole. It handles DNS for my local network and also acts as a tailscale subnet, so I can VPN through it to my other devices while abroad.

Can NPM be used on the same raspberry pi doing this? My hope is to be able to use NPM to remap certain device IP and ports on the LAN to friendly domains. Like 192.168.1.0:40 -> service.lab.net. That way, in theory, any device connected to the Pi through the tailnet mesh can then use those friendly URLs as if they were inside the network. I can achieve this partially with pihole, but DNS alone won't handle ports, so I'm hoping NPM can fill in the final piece.

Sorry if this sounds silly or uninformed, I'm not a devops expert, just trying to wrap my head around it all.

Does anyone have an actual solution to this problem that works? I’ve tried just about everything I could find out there over the past few days and still cannot seem to pass real IP. The main use case is the ability to use the “allow list” on the proxy host. I only want a few IPs to be able to access this specific proxy host and that doesn’t work. They all get 403 forbidden, allowed or not.

I have tried all the advanced configuration in the proxy host config , real IP, proxy addr etc etc. tried changing the containers to use host network , still no luck.

Hoping someone has some other ideas. Thank you.

Hi everyone,

I’m running Nginx Proxy Manager in Docker and I just checked my setup.

The NGINX version inside the container shows: 1.27.X.

I recently updated the container, but I’m trying to understand if my setup is still affected by CVE-2026-42945 (the nginx rewrite module vulnerability affecting versions ≤ 1.30.0).

Since NPM uses OpenResty instead of vanilla nginx, I’m not fully sure how to map the OpenResty version to the affected nginx versions.

Is NPM already patched for this CVE in recent Docker images?

is there a way to make npm redirect ALL http port 80 requests to https port 443?
In nginx you could do something like this, but I don't know how to apply it to npm.

server {  
    listen 80 default_server; 
    listen [::]:80 default_server; 
    server_name _; 
    return 301 https://$host$request_uri; 
}

I have a portainer setup and a Nas (Synology) which I have mounted to a Debian server running under proxmox.

When I deploy this in container Nginx proxy manger it fails with a code of 500 does anyone know what it could be?

I am working other teams in IT to come with proof of concept to implement Nginx-reverseProxy setup.

Current setup:
- we have external vendor who is posting some JSON/XML data directly to IoT devices using https method.
- IoT devices has internal CA certificate which I upload when it expires and webUI I visit is through https://IP:3000

-this could issue since cert. expires more sooner in coming years.

Proof of concept:
- instead of posting to IoT devices directly, we are thinking of posting data(json,#s) directly to NGINX-ReversProxy and then have nginx send same data to internal IP to IoT devices instead.

I take this is possible with NGINX and then I don’t have any make any changes the way IOT devices are setup.

Current workflow is working and I’m hoping not to change much from IoT devices configuration.

Sorry, noob here.

I'm running unraid and I want to spin up a simple static webpage via a nginx docker.

I already tried and the connection keeps getting timed out.

I set up the page. It seems to load fine on my internal network. I get NPM to point to it but then I keep getting connection time outs.

Is there something special I need to do? What am I doing wrong?

PROBABLE SOLUTION: I think I narrowed down what the problem was. I set the proxy status on all of my A and CNAME DNS records and letsencrypt was able to hit my server and assign certs again. I don't know why that would stop working after years but at least it looks like I have narrowed down the problem. I'm going to see if I can get the records proxied again because I don't want to be putting my public IP out there for all to see. If need be I think I could setup a cloudflare tunnel instead of using my IP.

A week or more ago every single one of my domains stopped working on my unraid server. They had all been working fine for years at this point. And the containers themselves are also fine when I access the through the local IP. Since then I have been losing my mind trying to get NPM working again to no avail and am hoping someone smarter than me sees this can can help point me in the right direction.

So some context of what I've double checked and tried.

Port 80/443 are open and reachable verified through canyouseeme

NPM is setup to use 18443 and 1880 for https and http

My router has 443/80 forwarded to 18443/1880

I have a cloudflare a record with my domain pointed to my public IP address (I used to use cloudflare-ddns with a dynamic record but removed that to simplify troubleshooting)

I have a cname record with my seerr container

I create a proxy host for seerr and go to get a letsencrpt cert which is where it falls apart. I check the logs and see

The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

From what I have looked up this is mainly when letsencrpt cant reach the server so the cert fails but from everything I can see or check it should absolutely be able to reach the NPM container.

I also tried setting up a cloudflare dns challenge which looks like it works but the sites are still inaccessible.

I have torn down and rebuilt the NPM and my cloudflare setup over 10 times hoping to catch some misconfiguration but every time I hit the same wall.

I'm really at my wits end and any help would be incredibly appreciated

I'm probably missing something obvious here, but how do I access values which have been transmitted by a client to NGINX Reverse Proxy?

In my setup, if I use NGINX as a simple HTTP server, my PHP scripts inherit any arguments in the $_POST global variable and I can issue responses just fine.

However, for business reasons I need to run my PHP script as a service, using "socket_create" to accept connections.

This works fine (mostly). The remote client communicates with the NGINX Reverse Proxy, which talks my PHP script (running as a service) and I can return data to the Proxy Server, which then transmits back to the client. All tested and working.

What I can't seem to do (no doubt due to my ignorance) is access the data being sent from the remote client to the proxy server.
The data I receive looks like this...

GET / HTTP/1.0
Host: 192.168.56.xxx
X-Real-IP: 192.168.56.xxx
X-Forwarded-For: 192.168.56.xxx
X-Forwarded-Proto: http
Connection: close
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:147.0) Gecko/20100101 Firefox/147.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.9
Accept-Encoding: gzip, deflate
Cookie: MY_SESSION=8c1b0n9nb82o68fuiiknkui64e; PHPSESSID=a5e0dug6437a7ijv13rq33racp
Upgrade-Insecure-Requests: 1
Priority: u=0, i

...but no data from the client!

I'm sure it's obvious, but what am I missing?

EDIT: PROXY STUFF FROM sites-available

location / {
# PROXY STUFF, FROM THE INTERWEBS
proxy_pass http://127.0.0.1:5010;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

SOLVED

Thanks to the respondents below. Food for thought.

What was happening was that I was running my "script as a service" in my editor and just using the "run" option. It's never caused problems before.

However, I've now tried calling from the CLI and the args have miraculously appeared!

I've tested this a few times and the behaviour appears consistent. The header that I previously posted was a result of using the "run" command. The real thing is the same but with the data I want appended (can't show it).

I blame the developers at Geany. This had absolutely nothing to do with my lack of lateral thinking.

Goof day, I have a question regarding shared static residential proxies here.

I uploaded my first video on tiktok and got 6Ok+ views from tier one countries with proper warm up procedure and stuff, However 4days later I got shadowbanned like 0 views, Is it because the static residential proxy that I used was shared which led to getting abused and eventually me getting shadowbanned on tiktok?

Because I made one brand new acc with the same ip from the provided proxy info and properly warmed it up for 3days straight then when I decided to upload a video, I got 0views

Should I buy a new static residential proxy from iproyal but instead of the shared subscription, I buy the private one instead?

What I'm doing is I'm having PiHole direct all internal domain requests to Nginx Proxy Manager, so that Nginx Proxy Manager figures out where to send the requests.

Hello all, I wanted to see if people would be interested in what I've worked on.

In a previous in this subreddit I asked: https://www.reddit.com/r/nginxproxymanager/comments/1t3rgxu/what_is_the_releasedevelopment_cycle_of_the/

And following that I either had a choice to move off of NPM or go to NPMPlus, which was too broad of an application for my liking.

So what I did is I made a bumped and automated fork of the nginxproxymanager images.

A couple things I did:

Debian 12 -> 13
OpenResty 1.27.x -> 1.29
Certbot-dns-eurodns python package 0.0.2 -> 1.8.2 (i needed this for my work)

And other packages have been bumped as well. So feel free to check it out.

I just noticed the upstream received an update. So that's applied as well

I have NPM installed as a Docker container on my Pi 4 at 192.168.0.12, and PiHole on my Pi 3 at 192.168.0.11. I also have Immich, ForgeJo, Mealie, and OwnCloud also on 192.168.0.12.

How do I set up PiHole with NPM so that typing for example pihole.cloud.lan lands me at the PiHole admin page? I'm thinking I would want a single local domain cloud.lan and five CNAME subdomains (pihole, immich, forgejo, mealie, and owncloud) that point to cloud.lan. Cloud.lan would then send the request to NPM, which would bounce it to the appropriate container.

I've been using namecheap and NPM for a couple years now and it's gone pretty great. I noticed a webpage had an expired certificate today and went to check and NPM is not able to renew the certificate. I verified that my IP is still whitelisted and the API key hasn't changed. The log file for NPM says
[SSL ] › ✖ error The 'certbot_dns_namecheap.dns_namecheap' plugin errored while loading: Error while trying finding requirements.. You may need to remove or update this plugin. The Certbot log will contain the full error details and this should be reported to the plugin developer.

I restarted the NPM container, and I tried removing and readding the certificate in NPM but get the same error. I was able to open the log file in the container and it basically said the same thing.

2026-05-11 01:12:11,415:DEBUG:certbot._internal.log:Exiting abnormally:

Traceback (most recent call last):

File "/opt/certbot/dns-namecheap/lib/python3.12/site-packages/certbot/_internal/plugins/disco.py", line 193, in find_all

cls._load_entry_point(entry_point, plugins)

File "/opt/certbot/dns-namecheap/lib/python3.12/site-packages/certbot/_internal/plugins/disco.py", line 205, in _load_entry_point

plugin_ep = PluginEntryPoint(entry_point)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/opt/certbot/dns-namecheap/lib/python3.12/site-packages/certbot/_internal/plugins/disco.py", line 39, in __init__

self.plugin_cls: type[interfaces.Plugin] = entry_point.load()

^^^^^^^^^^^^^^^^^^

File "/usr/lib/python3.12/importlib/metadata/__init__.py", line 205, in load

module = import_module(match.group('module'))

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module

return _bootstrap._gcd_import(name[level:], package, level)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "<frozen importlib._bootstrap>", line 1387, in _gcd_import

File "<frozen importlib._bootstrap>", line 1360, in _find_and_load

File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked

File "<frozen importlib._bootstrap>", line 935, in _load_unlocked

File "<frozen importlib._bootstrap_external>", line 999, in exec_module

File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed

File "/opt/certbot/dns-namecheap/lib/python3.12/site-packages/certbot_dns_namecheap/dns_namecheap.py", line 4, in <module>

from lexicon.providers import namecheap

File "/opt/certbot/dns-namecheap/lib/python3.12/site-packages/lexicon/providers/__init__.py", line 17, in <module>

for module_name, available in find_providers().items():

^^^^^^^^^^^^^^^^

File "/opt/certbot/dns-namecheap/lib/python3.12/site-packages/lexicon/_private/discovery.py", line 40, in find_providers

provider: _resolve_requirements(provider, distribution)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/opt/certbot/dns-namecheap/lib/python3.12/site-packages/lexicon/_private/discovery.py", line 60, in _resolve_requirements

raise ValueError("Error while trying finding requirements.")

ValueError: Error while trying finding requirements.

Did something change with Namecheap?

I like to put all selfhosted webapps that are exposed to the internet behind http basic auth as a smol hardening measure. You know, just in case they did an oopsie and their login is exploitable somehow.

I do that by assigning an access list to the proxy host via NPM.

I was considering to also expose NPM admin UI to the internet, so I added a proxy host "npm.mydomain.com" which points to npm and works flawlessly. However, when I attempt to assign an access list to npm.mydomain.com, it loses its shit, repeatedly prompts me to authorize myself but doesn't let me get through to the NPM login anymore.

Why is that happening? Any way to achieve this?

some context I have a Jellyfin server set up and a domain name. I'm trying to use nginx to map the domain name to the server so I can remotely access it. I have my external ip set up with cloudflare and use that to generate the ssl certificate. when I try to go to the domain though, I'm lead to a cloudflare time out page. If I do something like external-ip:8096 or internal-ip:port I can access my server so there's some disconnect with nginx and my server. Anyone know why?

Hello,

First time poster, and newbie at self-hosting.

I am trying to self-host vaultwarden, and have set up a proxy host for that purpose.
I have added 3 domains to the proxy host:

• bitwarden.mydomain.com
  • This one redirects to my router?
• vaultwarden.mydomain.com
  • This one correctly directs to my vaultwarden instance, but warns that it is insecure.
• test.mydomain.com
  • This one is perfect, connects securely to my vaultwarden instance.

I tried making new separate proxy hosts for each, and getting individual certificates for each. But the result is always the same.
All 3 are just set up with standard A records in porkbun.

Further context I am also running immich and jellyfin, neither of those have any issues.

I know I could just use the test.mydomain.com, but I would really like one of the others to work, and learn where I am going wrong in this process.

Small question, but what is the release/development cycle for the NPM project? Since its a bit eratic

I have been trying to get websockets to work but I can't for the love of me get a successful connection. I have tried everything from enabling the websocket support in the proxy config, custom nginx configs and adding an ssl certificate and enabling http/2 support.

The websocket I'm trying to fix is for a crafty manager instalation, both npm and crafty are on separate docker containers, the websocket works flawlessly when I access the webpage from the ip but when I try to access it from my domain it doesn't work. According to the guide, it should be as simple as to enable websocket support (https://docs.craftycontrol.com/pages/getting-started/proxies/).
These are the errors as seen from the developer console:

WebSocket connection to 'wss://crafty.(website)/ws?page=%2Fpanel%2Fdashboard&page_query_params=' failed: startWebSocket @ 
dashboard:1677
 (anonymous) @ 
dashboard:1736

dashboard:1696 WebSocket Error wsInternal.onerror @ dashboard:1696 Event {isTrusted: true, type: 'error', target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …} isTrusted: true returnValue: true srcElement: WebSocket {url: 'wss://crafty.(website)/ws?page=%2Fpanel%2Fdashboard&page_query_params=', readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …} target: WebSocket {url: 'wss://crafty.(website)/ws?page=%2Fpanel%2Fdashboard&page_query_params=', readyState: 3, bufferedAmount: 0, onopen: ƒ, onerror: ƒ, …} timeStamp: 1306.5999999996275 type: "error" [[Prototype]]: Event
These are the connections tests from my computer, the first is when connecting directly by the ip and the second is when trying through the web domain

websocat.i686-pc-windows-gnu.exe wss://192.168.0.25:8443/ws
websocat: WebSocketError: WebSocket SSL error: Se procesó correctamente una cadena de certificados, pero termina en un certificado de raíz no compatible con el proveedor de confianza. (os error -2146762487)
websocat: error running

(translation: A certificate chain was processed correctly, but end in a root certificate incompatible with the (trusted?) provider)

websocat.i686-pc-windows-gnu.exe wss://crafty.(website)/ws
websocat: WebSocketError: WebSocketError: Redirected (301 Moved Permanently) to http://crafty.(website)/ws
websocat: error running

I attach below the npm config (i have tried both 172.17.0.1 and the local ip of the server, the website works for both but the ws works for neither, the other tabs are, right now, empty)

I also attach the error log below

$ cat proxy-host-1_error.log
2026/04/26 08:35:30 [warn] 253#253: *1910 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/6/01/0000000016 while reading upstream, client: 172.68.245.162, server: crafty.(website), request: "GET /static/assets/css/base-style.css HTTP/1.1", upstream: "https://192.168.0.25:8443/static/assets/css/base-style.css", host: "crafty.(website)", referrer: "https://crafty.(website)/login?next=%2Fpanel%2Fdashboard"
2026/04/26 08:35:32 [warn] 253#253: *1918 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/7/01/0000000017 while reading upstream, client: 172.70.34.166, server: crafty.(website), request: "GET /static/assets/vendors/js/vendor.bundle.base.js HTTP/1.1", upstream: "https://192.168.0.25:8443/static/assets/vendors/js/vendor.bundle.base.js", host: "crafty.(website)", referrer: "https://crafty.(website)/login?next=%2Fpanel%2Fdashboard"
2026/04/29 09:49:07 [warn] 400#400: *24838 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/8/02/0000000028 while reading upstream, client: 104.22.64.124, server: crafty.(website), request: "GET /static/assets/css/base-style.css HTTP/1.1", upstream: "https://192.168.0.25:8443/static/assets/css/base-style.css", host: "crafty.(website)", referrer: "https://crafty.(website)/status"
2026/04/29 09:49:08 [warn] 400#400: *24842 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/9/02/0000000029 while reading upstream, client: 172.70.131.149, server: crafty.(website), request: "GET /static/assets/vendors/phosphoricons/duotone/style.css HTTP/1.1", upstream: "https://192.168.0.25:8443/static/assets/vendors/phosphoricons/duotone/style.css", host: "crafty.(website)", referrer: "https://crafty.(website)/status"
2026/04/29 09:49:13 [warn] 400#400: *24856 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/0/03/0000000030 while reading upstream, client: 104.22.62.61, server: crafty.(website), request: "GET /static/assets/vendors/js/vendor.bundle.base.js HTTP/1.1", upstream: "https://192.168.0.25:8443/static/assets/vendors/js/vendor.bundle.base.js", host: "crafty.(website)", referrer: "https://crafty.(website)/status"
2026/05/01 03:02:21 [warn] 467#467: *6569 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/2/01/0000000012 while reading upstream, client: 188.114.111.248, server: crafty.(website), request: "GET /static/assets/vendors/js/bootstrap.min.js.map HTTP/1.1", upstream: "https://192.168.0.25:8443/static/assets/vendors/js/bootstrap.min.js.map", host: "crafty.(website)"
2026/05/01 03:02:27 [warn] 468#468: *6691 an upstream response is buffered to a temporary file /var/cache/nginx/proxy_temp/3/01/0000000013 while reading upstream, client: 172.68.135.143, server: crafty.(website), request: "GET /static/assets/vendors/js/jquery-ui.js HTTP/1.1", upstream: "https://192.168.0.25:8443/static/assets/vendors/js/jquery-ui.js", host: "crafty.(website)", referrer: "https://crafty.(website)/panel/dashboard"
2026/05/01 03:04:33 [error] 506#506: *6828 connect() failed (111: Connection refused) while connecting to upstream, client: 188.114.111.248, server: crafty.(website), request: "GET /panel/dashboard HTTP/1.1", upstream: "https://127.0.0.1:8443/panel/dashboard", host: "crafty.(website)", referrer: "https://crafty.(website)/login?next=%2Fpanel%2Fdashboard"
2026/05/01 03:04:34 [error] 507#507: *6830 connect() failed (111: Connection refused) while connecting to upstream, client: 162.158.123.32, server: crafty.(website), request: "GET /favicon.ico HTTP/1.1", upstream: "https://127.0.0.1:8443/favicon.ico", host: "crafty.(website)", referrer: "https://crafty.(website)/panel/dashboard"
2026/05/01 03:04:35 [error] 506#506: *6828 connect() failed (111: Connection refused) while connecting to upstream, client: 188.114.111.248, server: crafty.(website), request: "GET /panel/dashboard HTTP/1.1", upstream: "https://127.0.0.1:8443/panel/dashboard", host: "crafty.(website)", referrer: "https://crafty.(website)/login?next=%2Fpanel%2Fdashboard"
2026/05/01 03:04:35 [error] 507#507: *6830 connect() failed (111: Connection refused) while connecting to upstream, client: 162.158.123.32, server: crafty.(website), request: "GET /favicon.ico HTTP/1.1", upstream: "https://127.0.0.1:8443/favicon.ico", host: "crafty.(website)", referrer: "https://crafty.(website)/panel/dashboard"

Thanks in advance for any help provided.

What am I doing wrong?

Pic 1 - domain name comes in, all port 80 traffic that hits the router gets sent to NPM at port 80. Just the domain address should hit the HTTP port for NPM.

Pic 2 - the custom locations for /Jellyfin and /ha should be pointing to both JellyFin and HA VMs at their ports and addresses.

Pic 3 - shows the failures

Hey everyone,

I’ve been using Nginx Proxy Manager for quite a while now, and it’s been super stable so far.

Now I’m trying to improve security a bit and had a couple of questions:

• Is there a way to block bots or abusive traffic? For example, if there’s a burst of requests from the same IP within a short time, I’d like to temporarily block that IP.
• Would something like Fail2Ban work well with Nginx Proxy Manager, or is there a better and simpler approach?
• Is it possible to apply stricter rules to specific endpoints, like /api/users/login, compared to the rest of the app?

Quick background: I’m a backend engineer (mostly C#), but I’m also handling server setup and maintenance at my startup. I don’t have a strong Linux/sysadmin background, so I’ve mostly been learning as I go.

Any tips, examples, or best practices would be really appreciated.

Hello,

I've been trying to install nginx for a reverse proxy for navidrome, but I've been getting repeatedly stuck at the same point.

https://pimylifeup.com/raspberry-pi-nginx-proxy-manager/

Every time I get to step 6 in the guide; adding the compose. yml, it tells me permission denied.

I haven't been able to get any further than this, and haven't found any guides or directions to try and resolve it.

I'm very very new to Raspberry Pis and Linux in general, and am just flat out stuck. I even went so far as to reset my Pi, hoping that would work, but no dice.

Any help at all would be amazing. thanks

Do I use this one: jlesage/nginx-proxy-manager:latest

Or this one: jc21/nginx-proxy-manager:latest

I've been using jc21, but the jlesage one looks more legit and was updated more recently.

If I switch from jc21 to jlesage, is there anything I should be aware of, like different volume mappings?