[GH-ISSUE #2996] Admin-Panel not showing up after successful start #2046

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

Originally created by @Ferrea-96 on GitHub (Jun 12, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2996

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'm trying to get started with nginx-proxy-manager. I'm running several docker-images in one single docker-compose file.
On startup (docker-compose up -d) everything works fine. All my other docker-images work on their port. Even the default screen shows up on localhost:81:

_Congratulations!

You've successfully started the Nginx Proxy Manager.

If you're seeing this site then you're trying to access a host that isn't set up yet.

Log in to the Admin panel to get started._

The Problem is. No Admin panel is showing up...

Nginx Proxy Manager Version
No Login-Page for me =(

To Reproduce
Steps to reproduce the behavior:
See docker-compose file in "additional context

Expected behavior
The Login-Page should be there by the get-go.

Screenshots
image
image

Operating System
Docker Host: Ubuntu 18.04
Docker Version 24.0.2
Docker Compose Version 1.25.5

Additional context
fallback_error.log
docker-compose.txt

Originally created by @Ferrea-96 on GitHub (Jun 12, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2996 <!-- 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)? - Yes **Describe the bug** I'm trying to get started with nginx-proxy-manager. I'm running several docker-images in one single docker-compose file. On startup (docker-compose up -d) everything works fine. All my other docker-images work on their port. Even the default screen shows up on localhost:81: _Congratulations! You've successfully started the Nginx Proxy Manager. If you're seeing this site then you're trying to access a host that isn't set up yet. Log in to the Admin panel to get started._ The Problem is. No Admin panel is showing up... **Nginx Proxy Manager Version** No Login-Page for me =( **To Reproduce** Steps to reproduce the behavior: See docker-compose file in "additional context **Expected behavior** The Login-Page should be there by the get-go. **Screenshots** ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/61230079/7d500057-3308-4f24-b5ae-755b59887d9d) ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/61230079/7d2f874a-3c59-4e30-a12b-302288f69661) **Operating System** Docker Host: Ubuntu 18.04 Docker Version 24.0.2 Docker Compose Version 1.25.5 **Additional context** [fallback_error.log](https://github.com/NginxProxyManager/nginx-proxy-manager/files/11726773/fallback_error.log) [docker-compose.txt](https://github.com/NginxProxyManager/nginx-proxy-manager/files/11726834/docker-compose.txt)
kerem 2026-02-26 07:33:49 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@jrd2017 commented on GitHub (Jun 13, 2023):

Are you using port 81? Port 80 is the frontpage

<!-- gh-comment-id:1589813438 --> @jrd2017 commented on GitHub (Jun 13, 2023): Are you using port 81? Port 80 is the frontpage
Author
Owner

@Ferrea-96 commented on GitHub (Jun 13, 2023):

@jrd2017 jup you nailed it. I always checked the incoming ports 80 and 81 and not the ones I port forward to...
Thanks

<!-- gh-comment-id:1589885290 --> @Ferrea-96 commented on GitHub (Jun 13, 2023): @jrd2017 jup you nailed it. I always checked the incoming ports 80 and 81 and not the ones I port forward to... Thanks
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#2046
No description provided.