[GH-ISSUE #1273] invalid port in upstream "http:// 172.17.0.1:81" #1028

Closed
opened 2026-02-26 06:35:29 +03:00 by kerem · 1 comment
Owner

Originally created by @jackwan1 on GitHub (Jul 28, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1273

Checklist

  • Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker 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)?
    • No

Describe the bug

Nginx Proxy Manager Version
<2.9.6>

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error *15414 invalid port in upstream "http:// 172.17.0.1:81", client: 192.168.1.1, server: jackwan2.ddns.us, request: "GET /favicon.ico HTTP/1.1", host: "jackwan2.ddns.us", referrer: "http://jackwan2.ddns.us/"

Expected behavior
<set host name jackwan2.ddns.us in proxy manager should be redirected to nginx proxy manager on 172.17.0.1:81, instead it was not forwarded at all, default page from port 80 was reached>
proxyscreen

Screenshots

Operating System

Additional context

Originally created by @jackwan1 on GitHub (Jul 28, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1273 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker 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)? - No **Describe the bug** <!-- A clear and concise description of what the bug is. --> **Nginx Proxy Manager Version** <2.9.6> **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error *15414 invalid port in upstream "http:// 172.17.0.1:81", client: 192.168.1.1, server: jackwan2.ddns.us, request: "GET /favicon.ico HTTP/1.1", host: "jackwan2.ddns.us", referrer: "http://jackwan2.ddns.us/" **Expected behavior** <set host name jackwan2.ddns.us in proxy manager should be redirected to nginx proxy manager on 172.17.0.1:81, instead it was not forwarded at all, default page from port 80 was reached> ![proxyscreen](https://user-images.githubusercontent.com/86899995/127409625-0817128b-d329-4bf7-a385-701df4ceb44b.jpg) **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> **Operating System** <!-- Please specify if using a Rpi, Mac, orchestration tool or any other setups that might affect the reproduction of this error. --> **Additional context** <!-- Add any other context about the problem here, docker version, browser version, logs if applicable to the problem. Too much info is better than too little. -->
kerem 2026-02-26 06:35:29 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@jackwan1 commented on GitHub (Jul 29, 2021):

Nevermind, I think I ran docker-compose too many times and things got messed up. After I reinstalled everything it is working.

<!-- gh-comment-id:889377332 --> @jackwan1 commented on GitHub (Jul 29, 2021): Nevermind, I think I ran docker-compose too many times and things got messed up. After I reinstalled everything it is working.
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#1028
No description provided.