starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #2163] Address already in use #1549

New issue

Closed

opened 2026-02-26 07:31:31 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 07:31:31 +03:00

Owner

Originally created by @axldroid on GitHub (Jul 20, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2163

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)?
- Yes

Describe the bug
I cant start it with docker

Operating System
Ubuntu 20.04

Error
root@ns5009505:/# docker-compose up -d
Creating default_app_1 ...
Creating default_app_1 ... error

ERROR: for default_app_1 Cannot start service app: driver failed programming external connectivity on endpoint default_app_1 (9e61ae547efaa671fce34be29bdbdac2a056f3fe26a10c4f579c0b195ea27cc5): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use

ERROR: for app Cannot start service app: driver failed programming external connectivity on endpoint default_app_1 (9e61ae547efaa671fce34be29bdbdac2a056f3fe26a10c4f579c0b195ea27cc5): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use
ERROR: Encountered errors while bringing up the project.

Originally created by @axldroid on GitHub (Jul 20, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2163 **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)? - Yes **Describe the bug** I cant start it with docker **Operating System** Ubuntu 20.04 **Error** root@ns5009505:/# docker-compose up -d Creating default_app_1 ... Creating default_app_1 ... error ERROR: for default_app_1 Cannot start service app: driver failed programming external connectivity on endpoint default_app_1 (9e61ae547efaa671fce34be29bdbdac2a056f3fe26a10c4f579c0b195ea27cc5): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use ERROR: for app Cannot start service app: driver failed programming external connectivity on endpoint default_app_1 (9e61ae547efaa671fce34be29bdbdac2a056f3fe26a10c4f579c0b195ea27cc5): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use ERROR: Encountered errors while bringing up the project.

kerem

2026-02-26 07:31:31 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 07:31:32 +03:00

Author

Owner

@the1ts commented on GitHub (Jul 21, 2022):

it appears you already have something listening on port 443, have nginx or apache already running?

@the1ts commented on GitHub (Jul 21, 2022): it appears you already have something listening on port 443, have nginx or apache already running?

kerem commented

2026-02-26 07:31:32 +03:00

Author

Owner

@axldroid commented on GitHub (Jul 21, 2022):

it appears you already have something listening on port 443, have nginx or apache already running?

Yes, I have NGINX running already on my machine. Do you know any way I could have both of them running simultaneously?

@axldroid commented on GitHub (Jul 21, 2022): > it appears you already have something listening on port 443, have nginx or apache already running? Yes, I have NGINX running already on my machine. Do you know any way I could have both of them running simultaneously?

kerem commented

2026-02-26 07:31:32 +03:00

Author

Owner

@the1ts commented on GitHub (Jul 21, 2022):

one will have to use another port or another IP on the same machine. Only one process can bind to an IP:port at time.

@the1ts commented on GitHub (Jul 21, 2022): one will have to use another port or another IP on the same machine. Only one process can bind to an IP:port at time.

kerem commented

2026-02-26 07:31:32 +03:00

Author

Owner

@axldroid commented on GitHub (Jul 22, 2022):

one will have to use another port or another IP on the same machine. Only one process can bind to an IP:port at time.

If I change the ports that NGINX Proxy Manager uses (443 and 80) will it still work?

@axldroid commented on GitHub (Jul 22, 2022): > one will have to use another port or another IP on the same machine. Only one process can bind to an IP:port at time. If I change the ports that NGINX Proxy Manager uses (443 and 80) will it still work?

kerem commented

2026-02-26 07:31:32 +03:00

Author

Owner

@the1ts commented on GitHub (Jul 22, 2022):

That is a big question, most people in this situation will change the ports to something that doesn't clash, but forward 80 -> new port 80 and 443 -> new port 443 from their router. That works fine for NPM hosted sites such as https://www.domain.com and https://app.domain.com since they are hit on port 80 and 443 on the router outside

@the1ts commented on GitHub (Jul 22, 2022): That is a big question, most people in this situation will change the ports to something that doesn't clash, but forward 80 -> new port 80 and 443 -> new port 443 from their router. That works fine for NPM hosted sites such as https://www.domain.com and https://app.domain.com since they are hit on port 80 and 443 on the router outside

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#1549

No description provided.

Rows
Columns