NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Host not working when using container's name with Podman
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image?- Yes
- Are you sure you're not using someone else's docker image?
- Yes
- Have you searched for similar issues (both open and closed)?
- Yes
Describe the bug
I'm trying to add a host using the name of the container, and when I open the URL, a 502 bad gateway appears. I tried using Docker, and it worked, but with Podman, it only works with container's IP.
Nginx Proxy Manager Version
v2.9.18
To Reproduce
Steps to reproduce the behavior:
- Create the container to forward: podman run --name web --network nginx-proxy-manager_default -d nginx:latest
- Add the host with:
-Forward Hostname / IP: web
-Port: 80 - Try to access service.
Expected behavior
The Nginx welcome page should appear
Screenshots





Operating System
Tried on
- Ubuntu 20.04 - Podman 3.2.2
- Ubuntu 22.04 - Podman 3.2.2 and Podman 4.2
- Fedora 36 - Podman 4.1
Additional context
docker-compose.yml
version: '3'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '80:80'
- '81:81'
- '443:443'
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported setup with Podman 3.2.2 or 4.x, using the exact web container command and nginx-proxy-manager network. Compare hostname forwarding with the working Docker behavior and trace why web returns a 502. Done means the Nginx welcome page loads when the host uses the container name, without requiring its IP.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100