mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #199] Failed to connect to db: ER_NOT_SUPPORTED_AUTH_MODE #174
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#174
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 @Daemach on GitHub (Sep 12, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/199
I did docker-compose up and waited for something to happen. Went to 127.0.0.1 and got this: https://www.screencast.com/t/spSzAm4Fb (making the words admin panel a link would be most useful)
127.0.0.1:81 (admin port from docker compose) said connection reset.
Running docker-compose up without -d yields this: https://www.screencast.com/t/YoNCnL0cr1 Maybe there is an error?
Looking forward to trying this - looks great from the screenshots!
@Daemach commented on GitHub (Sep 12, 2019):
More info https://www.screencast.com/t/fXqjk5sLr
@Daemach commented on GitHub (Sep 12, 2019):
MySQL https://www.screencast.com/t/3aR239vQ
@jc21 commented on GitHub (Nov 7, 2019):
Looks like your DB isn't initializing. What docker image are you using for it?
@chaptergy commented on GitHub (Dec 1, 2021):
The admin panel port is documented in both the quick setup in step 4 and in the docker container logs when starting the image. Though we can add even more information about that.
The actual issue also had nothing to do with the title, it was about the database connection not working, and it was opened a while ago, and a lot has changed since then. Also there were no further responses, thus it was closed.