-
Notifications
You must be signed in to change notification settings - Fork 545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker-compose mysql connection refused #302
Comments
@juzhiyuan hello, can u help me to have a look? Thanks. |
Hi, this may be related to a issue we found those days, and it will be fixed this weekend. Once it’s fixed, I will notify you here. |
OK, thanks. @juzhiyuan |
Please have a try in the new Dashboard :) |
+1 for same issue. @juzhiyuan May I ask which pull request fixed this or what the cause was? Thanks. |
I hava tried again in master branch, but it is the same. @juzhiyuan |
@juzhiyuan @TikWind For your information, the mysql connection error has gone with the latest code and everything worked in my case. My environment is: Operating system: macOS |
ok |
Feel free to reopen this issue when the error occurred again |
@juzhiyuan many thanks. |
@TikWind Good catch. Thanks for your work. While I have one more question that, everything is fine with my macOS docker desktop environment, is this bug OS dependent? Thanks. |
Descripe
Hi everyone, I follow https://github.com/apache/incubator-apisix-dashboard/blob/master/compose/README.md to deploy this project, but when I visit http://127.0.0.1/dashboard/ in the browser, it redirect http://127.0.0.1/dashboard/setting :
When I use
docker logs
to look image name "dashboard_manager" and container name "dashboard_manager_1" :Question
There is a error
panic: fail to connect to DB: dial tcp 192.17.5.14:3306: connect: connection refused for root:123456@tcp(192.17.5.14:3306)/manager?charset=utf8&parseTime=True&loc=Local
. Why? How to solve this problem? Thanks.Environment
System: CentOS Linux release 7.8.2003 (Core)
CPU: 4 core
Memory: 8G
The text was updated successfully, but these errors were encountered: