[GH-ISSUE #2445] Issue using extra-hosts with nginx proxy manager proxy hosts #1718

Closed
opened 2026-02-26 07:32:12 +03:00 by kerem · 2 comments
Owner

Originally created by @Rdonn on GitHub (Dec 2, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2445

I need to be able to define hosts in the docker compose file and proxy to them using nginx proxy manager using extra-hosts.

I have added the names and ips to the docker compose file and verified that they exist in /etc/hosts inside of the running container.

I have verified that they are reachable inside the running container using curl and ping. The server is pinging and curl is delivering the requested HTML.

After adding the proxy host, I am getting a 404. Am I misunderstanding that my custom name entries should be taken into account when proxying?

Originally created by @Rdonn on GitHub (Dec 2, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2445 I need to be able to define hosts in the docker compose file and proxy to them using nginx proxy manager using extra-hosts. I have added the names and ips to the docker compose file and verified that they exist in /etc/hosts inside of the running container. I have verified that they are reachable inside the running container using curl and ping. The server is pinging and curl is delivering the requested HTML. After adding the proxy host, I am getting a 404. Am I misunderstanding that my custom name entries should be taken into account when proxying?
kerem 2026-02-26 07:32:12 +03:00
  • closed this issue
  • added the
    stale
    bug
    labels
Author
Owner

@github-actions[bot] commented on GitHub (Feb 3, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:1925010975 --> @github-actions[bot] commented on GitHub (Feb 3, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Mar 20, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2738872163 --> @github-actions[bot] commented on GitHub (Mar 20, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1718
No description provided.