mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #140] Having issues getting admin panel to load #121
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#121
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 @emarschang on GitHub (May 10, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/140
Just installed this tool using docker compose. Container created just fine. I can reach localhost/80 and localhost/443 just fine. When looking at the docker container health it claims unhealthy. An I see and a snip from the docker logs are below.
Last output % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 502 Bad Gateway
[5/10/2019] [3:20:43 PM] [Global ] › ✖ error Config file /app/config/production.json cannot be read Error: Config file /app/config/production.json cannot be read,
@jc21 commented on GitHub (May 12, 2019):
Have you read this?
@lishine commented on GitHub (Jul 8, 2019):
Same here.
Why it just not runs as described - docker-compose ...
The config is there, so what is the problem?
@george-viaud commented on GitHub (Aug 7, 2019):
Similar problem here - things look fine but I am not certain how to dig deeper unfortunately. I suspect there are some pre-flight things I've done wrong (creating DB, User, etc) - not sure where to look for logs to see what's failing. Any direction on what to check would be greatly appreciated.
I use this tool via HASSIO regularly and would love to get it working stand-alone for use on AWS
@doughnet commented on GitHub (Jan 4, 2020):
Same issue. Funny thing is it works fine on a KVM virtual machine but on a OpenVZ 7 virtual machine it does not. Not sure if that coincidence or not ...
@chaptergy commented on GitHub (May 10, 2021):
Since this issue is fairly old I will close this. I anyone encounters this problem again, please open a new issue with as much information as possible, so logs, docker-compose files, etc