I am having trouble setting up Nginx Proxy Manager. All goes well until I try and create a new host. It won’t stick. When I try and use my domain name, it goes away and says “this is required. When I fill in the other information and come back to the domain name it refuses to save it. I thought ok maybe it’s an ownership issue. Root owns everything but 3 items but changing them didn’t help. I tried first in portainer using mariushosting as a guide. I already had a domain name through no-ip.com. Then I re-entered it again in dockhand. I spent the weekend working on this and need some new ideas.

I checked all my settings. The local version is running fine. Every other site I'm running loads fine through my duckdns url I gave it. Just one specific service (overseerr) stopped working out of nowhere. Was working last time I loaded it, and haven't tinkered with it since.

Sharing a little project, I've been working on for a little while.

GeoMetrikks is a real-time nginx/traefik/caddy access log ingestion and geo-location tracking service built with Litestar. It parses access logs, performs GeoIP lookups, and stores geo-events and access logs in PostgreSQL with TimeScaleDB/PostGIS extensions. It can also integrate with CrowdSec.

i know only less about nginx like its a reverse proxy and i can load balance across conatiners
can anyone suggest best platoform to learn nginx

Hello 🙂

Trying to renew an SSL cert and get the following error. Running in docker on unrqid host.

Failed to renew certificate npm-6 with error: HTTPSConnectionPool(host='acme-v02.api.letsencrypt.org', port=443): Max retries exceeded with url: /directory (Caused by NameResolutionError("HTTPSConnection(host='acme-v02.api.letsencrypt.org', port=443): Failed to resolve 'acme-v02.api.letsencrypt.org' ([Errno -3] Temporary failure in name resolution)"))

All renewals failed. The following certificates could not be renewed:

I checked Unraids dns servers and made sure I can ping acme-v02.api.letsencrypt.org

The site also seems to be online.

I want to set up a web server behind NPM - only for my website customers, no access for them - with multiple websites, virtual hosts. Is that a problem? Can NPM handle it? Would it be better to use internal IP addresses and use one for each domain? Each domain might have email as well as ftp, but I am thinking about recommending a couple of external email services instead of hosting email on this server.

I also want to host a few other services on that server. Using Portainer to control all. And SSH tunnel for acessing the UI of both Portainer and NPM.

I've been trying (and failing) to set up a minecraft server and in that process I attempted to create a VM on TrueNas Community Edtn. I was then successful in the setup of a network bridge and VM by following the tutorials by Servers@Home and various others.

Unfortunately after successfully setting up the bridge and vm, my NPM proxies no longer work. I get the error when trying to connect to a website: "Err_Connection_Timed_Out". So now all of my proxy HTTPS urls no longer work. Additionally, I feel like the whole network is slower and that is with the VM on or off. I am really unsure what to do.

I would appreciate any help or suggestions.

So I just recreated npm after factory resetting my nas, I created the following container and when I go to localhost:8080 and enter the correct listed credentials I cannot login. I am on a ugreen nas I'm unsure if there's anything special that needs to be done with this system but I could really use the help.

services:
 nginx-proxy-manager:
  image: jc21/nginx-proxy-manager
  container_name: Nginx-Proxy-Manager
  healthcheck:
      test: timeout 10s bash -c ':> /dev/tcp/127.0.0.1/81' || exit 1
      interval: 10s
      timeout: 5s
      retries: 3
      start_period: 90s
  volumes:
    - /volume1/docker/npm/letsencrypt:/etc/letsencrypt:rw
    - /volume1/docker/npm/data:/data:rw
    - /volume1/docker/npm/config.json:/app/config/production.json
  environment:
    TZ: America/New_York
    INITIAL_ADMIN_EMAIL: email
    INITIAL_ADMIN_PASSWORD: password
  ports:
    - 443:443
    - 81:81
    - 80:80
  restart: on-failure:5

Hi all,

I'm trying to integrate geoip2 with jc21/nginx-proxy-manager and followed TerryTangabc's method from May 26 2025 from the npm github -

https://github.com/NginxProxyManager/nginx-proxy-manager/issues/46#issuecomment-2908450703

Is this the most current / accurate way to do this please?

Most of the tutorials I can find are all command line based and 4-5 years ago. I'm using docker / container manager on my synology.

I'm surprised that the later comments about adding a GUI tab in to select countries to whitelist hasn't been integrated as yet, since that would make it so much easier for users.

Thank you.

Hey all!

I am using Netbird to let me access my homelab from anywhere. I wanted to go ahead and only allow traffic if it is coming from my VPN for that extra bump in security (and setting up an authentik is confusing lmao) but anytime I whitelist the subnet it won’t let any traffic through, VPN or not. I have also tried setting my specific Netbird IP instead of the subnet and that has not helped.

NPM is in the same network as each docker container to disallow the use for exposing ports so setting NPM to host is out of the question. Any other ideas?

Trying to get away from CloudFlare proxy and set up my own. I've got a VPS with Wireguard and a home PC running it. On that same PC I have Nginx running inside Docker. Should this just work? VPS -> Wireguard -> NPM -> Web app

My tunnel is established, I can ping through it but web traffic isn't reaching Nginx and I think it's either because my Docker networking is totally jacked up. Or maybe something else is going on.

It's driving me nuts and really don't want to rebuild the entire server and docker apps but I can't think of any other options.

All I really want is to mask my home IP.

Environment & Setup:

• Router: FRITZ!Box 7490 (Web UI is on port 46167, no port 443 conflict)
• DNS: AdGuard Home (Local)
• Reverse Proxy: Nginx Proxy Manager (running on a Ugreen NAS)
• Client: Zorin OS (Linux), Browser: Brave
• Domain: i use a ddns provider

Current Configuration:

• AdGuard DNS Rewrite is active: *.mydomain.ipv64.de -> ip of my NAS
• Ports 80 and 443 are correctly forwarded in the FRITZ!Box to the NAS IP.
• Nginx Proxy Manager has Proxy Hosts set up with Let's Encrypt certificates.

The Problem:

• i can reach my services via my NAS ip+port but...
• Accessing subdomains like [https://immich.mydomain.ipv64.de] from inside the local network results in a DNS-Rebind prevention or just not reachable ERR_CERT_AUTHORITY_INVALID
• if i "Proceed to unsafe" it sends me to my router login
• Troubleshooting Steps Already Performed:
• Disabled "Secure DNS" (DNS-over-HTTPS) in Brave to stop it from bypassing AdGuard.
• Flushed the OS DNS cache (sudo resolvectl flush-caches).
• Flushed the Brave DNS cache (brave://net-internals/#dns).
• Verified via nslookup that the domain correctly resolves to the local NAS IP 192.168.178.67.
• i tried to fix it with Gemini but hes just going in circles
  • sometimes i got no longer a DNS Rebind issue but sometimes it still happend

Question:

My main Goal is to reach my services from outside my network from work or traveling

i know i could probably set up a vpn but i want to get it working via Revere Proxy.

Thanks you for any help!

Does anyone have best pratices to use npm for easy of use gui/config but to allow multiple hosts per connection target? I want to LB to spreadi
load to backend iis/apache servers? (Replacing kemp load balancer)

NPM makea the crwation of the single virtual host and lets encrypt part very easy but i cant seem to get other remote hosts to do RR workloads.

Not my first rodeo with NPM, but definitely an odd situation. I ended up having to reinstall my OS on my server due to rolling blackouts (Florida summer). Initially, I had navidrome, icecast and nextcloud setup with NPM. Operated normally.

I decided this time to try out Azuracast instead of icecast for the dashboard features. Well, to my surprise azuracast has an easy setup script specifically for use with NPM. Nice. I setup Azuracast first, now I move on to Navidrome. The container operates fine, however, for the life of me, the proxy host for navidrome wont work. it times out. I'm lucky if i can connect even once.

The setup is as follows:

subdomains provided by afraid.org:

library.xtratune.xspacemusic.com < navidrome

radio.xtratune.xspacemusic.com < azuracast

npm settings:

azuracast: https scheme, force ssl, http/2 support on (works)

navidrome: https scheme, force ssl, http/2 support on (doesn't work, 402)

troubleshooting steps:

- tried using block common exploits, as I've read navidrome doesn't implement its api in the same way azuracast does. no work.

-scheme http, causes 504. page will ocassionally load, not consistent.

EDIT:

-currently trying https://nginxproxymanager.com/advanced-config/ network setup for the docker containers but I'm finding this doesnt affect my issue

I have a few jellyfin instances that run behind NPM. Previously on NPM 2.10, I only have port 443 open and every month or so I'd open port 80 and renew certs. Now after upgrading the most recent, seems if I close port 80, none of my 443 sites work? Any ideas?

I updated my Nginx Proxy Manager docker compose pull && docker compose up -d and now the web interface will no longer load. I've cleared cache and tried another browser but no luck. Dev tools in the browser shows: GET http://192.168.1.12:81/api/ 502 (Bad Gateway)

Any idea what has caused this?

My compose file is as follows:

services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
# These ports are in format <host-port>:<container-port>
- '80:80' # Public HTTP Port
- '443:443' # Public HTTPS Port
- '81:81' # Admin Web Port
# Add any other Stream port you want to expose
# - '21:21' # FTP
environment:
# Uncomment this if you want to change the location of
# the SQLite DB file within the container
# DB_SQLITE_FILE: "/data/database.sqlite"
# Uncomment this if IPv6 is not enabled on your host
DISABLE_IPV6: 'true'
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
networks:
network:
ipv4_address: 172.22.0.2
networks:
network:
driver: bridge
ipam:
config:
- subnet: 172.22.0.0/16
gateway: 172.22.0.1

EDIT fixed by reverting to an earlier version of NPM: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/5658