[GH-ISSUE #3379] After I installed it, I couldn't access it by entering the internal network IP and port number #2267

New issue

Closed

opened 2026-02-26 07:34:47 +03:00 by kerem · 2 comments

kerem commented 2026-02-26 07:34:47 +03:00

Owner

Copy link

Originally created by @1254565651 on GitHub (Dec 10, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3379

Checklist

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

Nginx Proxy Manager Version

2.10.4

stderr: sed: can't read /etc/nginx/conf.d/dev.conf: No such file or directory
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/assets.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/block-exploits.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/force-ssl.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ip_ranges.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/proxy.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ssl-ciphers.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/resolvers.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/production.conf[0m
stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/data/nginx[0m
stderr: nginx: [emerg] open() "/etc/nginx/conf.d/dev.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:75
stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/etc/nginx/conf.d[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/default.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/dev.conf[0m
stderr: sed: can't read /etc/nginx/conf.d/dev.conf: No such file or directory
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/assets.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/block-exploits.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/force-ssl.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ip_ranges.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/proxy.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ssl-ciphers.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/resolvers.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/production.conf[0m
stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/data/nginx[0m
stderr: nginx: [emerg] open() "/etc/nginx/conf.d/dev.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:75
stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/etc/nginx/conf.d[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/default.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/dev.conf[0m
stderr: sed: can't read /etc/nginx/conf.d/dev.conf: No such file or directory
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/assets.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/block-exploits.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/force-ssl.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ip_ranges.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/proxy.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ssl-ciphers.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/resolvers.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/production.conf[0m
stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/data/nginx[0m
stderr: nginx: [emerg] open() "/etc/nginx/conf.d/dev.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:75
stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/etc/nginx/conf.d[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/default.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/dev.conf[0m
stderr: sed: can't read /etc/nginx/conf.d/dev.conf: No such file or directory
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/assets.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/block-exploits.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/force-ssl.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ip_ranges.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/proxy.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ssl-ciphers.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/resolvers.conf[0m
stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/production.conf[0m
stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/data/nginx[0m
stderr: nginx: [emerg] open() "/etc/nginx/conf.d/dev.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:75

Originally created by @1254565651 on GitHub (Dec 10, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3379 <!-- 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? - No - 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** <!-- A clear and concise description of what the bug is. --> **Nginx Proxy Manager Version** <!-- What version of Nginx Proxy Manager is reported on the login page? -->2.10.4 stderr: sed: can't read /etc/nginx/conf.d/dev.conf: No such file or directory stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/assets.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/block-exploits.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/force-ssl.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ip_ranges.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/proxy.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ssl-ciphers.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/resolvers.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/production.conf[0m stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/data/nginx[0m stderr: nginx: [emerg] open() "/etc/nginx/conf.d/dev.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:75 stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/etc/nginx/conf.d[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/default.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/dev.conf[0m stderr: sed: can't read /etc/nginx/conf.d/dev.conf: No such file or directory stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/assets.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/block-exploits.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/force-ssl.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ip_ranges.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/proxy.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ssl-ciphers.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/resolvers.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/production.conf[0m stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/data/nginx[0m stderr: nginx: [emerg] open() "/etc/nginx/conf.d/dev.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:75 stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/etc/nginx/conf.d[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/default.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/dev.conf[0m stderr: sed: can't read /etc/nginx/conf.d/dev.conf: No such file or directory stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/assets.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/block-exploits.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/force-ssl.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ip_ranges.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/proxy.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ssl-ciphers.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/resolvers.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/production.conf[0m stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/data/nginx[0m stderr: nginx: [emerg] open() "/etc/nginx/conf.d/dev.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:75 stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/etc/nginx/conf.d[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/default.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/dev.conf[0m stderr: sed: can't read /etc/nginx/conf.d/dev.conf: No such file or directory stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/assets.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/block-exploits.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/force-ssl.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ip_ranges.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/proxy.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/ssl-ciphers.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/include/resolvers.conf[0m stdout: [1;34m❯ [1;33m/etc/nginx/conf.d/production.conf[0m stdout: [1;34m❯ [1;36mEnabling IPV6 in hosts: [1;33m/data/nginx[0m stderr: nginx: [emerg] open() "/etc/nginx/conf.d/dev.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:75

kerem 2026-02-26 07:34:47 +03:00

• closed this issue
• added the
  stale
  bug
  labels

kerem commented 2026-02-26 07:34:48 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Jul 16, 2024):

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

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

kerem commented 2026-02-26 07:34:48 +03:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Aug 7, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:3162192973 --> @github-actions[bot] commented on GitHub (Aug 7, 2025): Issue was closed due to inactivity.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

develop

dependabot/npm_and_yarn/backend/liquidjs-10.25.7

dependabot/npm_and_yarn/frontend/prod-minor-updates-2a16bf3987

dependabot/npm_and_yarn/frontend/dev-patch-updates-754666cf41

dependabot/npm_and_yarn/backend/basic-ftp-5.3.0

dependabot/npm_and_yarn/test/follow-redirects-1.16.0

dependabot/npm_and_yarn/test/axios-1.15.0

dependabot/npm_and_yarn/frontend/lodash-4.18.1

dependabot/npm_and_yarn/backend/lodash-4.18.1

dependabot/npm_and_yarn/test/lodash-4.18.1

dependabot/npm_and_yarn/frontend/vite-7.3.2

dependabot/npm_and_yarn/backend/prod-minor-updates-5ec19a7f21

dependabot/npm_and_yarn/frontend/lodash-es-4.18.1

dependabot/npm_and_yarn/frontend/happy-dom-20.8.9

dependabot/npm_and_yarn/backend/path-to-regexp-8.4.0

dependabot/npm_and_yarn/frontend/picomatch-4.0.4

dependabot/npm_and_yarn/backend/picomatch-2.3.2

dependabot/npm_and_yarn/frontend/yaml-1.10.3

dependabot/npm_and_yarn/test/flatted-3.4.2

dependabot/npm_and_yarn/test/tar-7.5.11

dependabot/npm_and_yarn/frontend/immutable-5.1.5

master

dependabot/npm_and_yarn/test/glob-10.5.0

dependabot/npm_and_yarn/frontend/mdast-util-to-hast-13.2.1

dependabot/npm_and_yarn/test/form-data-4.0.4

v3-abandoned

bump-freedns

openidc

ssl-passthrough-hosts

static-content

v2.14.0

v2.13.7

v2.13.6

v2.13.5

v2.13.4

v2.13.3

v2.13.2

v2.13.1

v2.13.0

v2.12.6

v2.12.5

v2.12.4

v2.12.3

v2.12.2

v2.12.1

v2.12.0

v2.11.3

v2.11.2

v2.11.1

v2.11.0

v2.10.4

v2.10.3

v2.10.2

v2.10.1

v2.10.0

v2.9.22

v2.9.21

v2.9.20

v2.9.19

v2.9.18

v2.9.17

v2.9.16

v2.9.15

v2.9.14

v2.9.13

v2.9.12

v2.9.11

v2.9.10

v2.9.9

v2.9.8

v2.9.7

v2.9.6

v2.9.5

v2.9.4

v2.9.3

v2.9.2

v2.9.1

v2.9.0

v2.8.1

v2.8.0

v2.7.3

v2.7.2

v2.7.1

v2.7.0

v2.6.2

v2.6.1

v2.6.0

v2.5.0

v2.4.0

v2.3.1

v2.3.0

v2.2.4

v2.2.3

v2.2.2

v2.2.1

v2.2.0

v2.1.2

v2.1.1

v2.1.0

2.0.14

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.0

v2.0.0

1.1.2

1.1.1

1.0.1

Labels

Clear labels   

awaiting feedback

  

bug

  

cannot reproduce

  

dns provider request

  

duplicate

  

enhancement

  

enhancement

  

enhancement

  

good first issue

  

help wanted

  

invalid

  

need more info

  

no certbot plugin available

  

product-support

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

stale

  

troll

  

upstream issue

  

v2

  

v2

  

v2

  

v3

  

wontfix

No labels

awaiting feedback

bug

cannot reproduce

dns provider request

duplicate

enhancement

enhancement

enhancement

good first issue

help wanted

invalid

need more info

no certbot plugin available

product-support

pull-request

question

stale

troll

upstream issue

v2

v2

v2

v3

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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

No description provided.