mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #2407] BUG submission, sorry, my English is poor, I hope you can understand my content #1692
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1692
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @chccl on GitHub (Nov 17, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2407
主要问题就是:
The main problems are:
1:我在docker ,pull Nginx Proxy Manager :latest。
1: I'm in docker, pull Nginx Proxy Manager: latest.
2:安装成功后,我立马去登陆,
2: After the installation is successful, I immediately log in,
出现Bad Gateway 错误, 但是不做任何操作,静静的等到2-3分钟, 就可以正常登陆进入后台,如果重启了Nginx Proxy Manager container,又是这个问题,
A Bad Gateway error occurs, but no action is taken. Wait for 2-3 minutes quietly, and you can log in to the background normally. If you restart the Nginx Proxy Manager container, this is the problem again,
4:总结:只要重启了 Nginx Proxy Manager container,又是这个问题,Bad Gateway 错误!
4: Conclusion: As long as the Nginx Proxy Manager container is restarted, this problem occurs again. Bad Gateway is wrong!
5:希望您能回答我这是什么问题呢,谢谢您, 祝你平安健康
5: I hope you can answer my question. Thank you. I wish you a safe and healthy life
@github-actions[bot] commented on GitHub (Feb 5, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Mar 21, 2025):
Issue was closed due to inactivity.