mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 09:55:51 +03:00
[GH-ISSUE #536] Bad Gateway, ECONNREFUSED #456
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#456
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 @thehedgefrog on GitHub (Aug 1, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/536
Checklist
jc21/nginx-proxy-manager:latestdocker image?Yes
Yes
N/A
Describe the bug
Will not connect to the database, error ECONNREFUSED and then it times out. Tried multiple ways. I can ping db just fine from the app console.
v2.3.1
config.json
docker-compose.yml
DB Logs
App log
Operating System
QNAP with latest QTS, Portainer 1.24.1
Additional context
At a loss here, tried everything.
@codeagencybe commented on GitHub (Sep 19, 2020):
@wschlotter
I got it working!
db_1 | 2020-09-19 12:31:16 0 [ERROR] InnoDB: The Auto-extending innodb_system data file './ibdata1' is of a different size 0 pages than specified in the .cnf file: initial 768 pages, max 0 (relevant if non-zero) pages!All I did was delete the .ibdata1 file that shows 0kb
And then re-deploy the whole setup. Now it generates a new clean .ibdata file that is around 12Mb size
@Iron-Merlin-2000 commented on GitHub (Sep 26, 2020):
@codeagencybe
due to the fact that if have the same issue with my installation and I'm not too deep into docker, I'd like to ask how to delete the .ibdata1 file ? Can this be done when the container is up an running ?
@codeagencybe commented on GitHub (Sep 27, 2020):
@Iron-Merlin-2000
If you do the Docker-compose up command, it will generate all those files in your volume the first run.
When that's done, ssh into server (or use SFTP) and go to the mount where you specified the app volume.
From there delete it and then redeploy again.
That's all I did and it works but this is not a permanent fix whatsoever.
It still requires a patch/fix so this doesn't happen on new deployments.
@cxlso commented on GitHub (Feb 24, 2021):
Hey! I'm a noob and I encounter the same problem. What do you type into your terminal to access the .ibdata1 file?