-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
[BUG] Doctrine\DBAL\Exception: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[HY000] [2002] Host is unreachable in /app/www/public/lib/private/DB/Connection.php:167 #468
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
That's saying it's unable to connect to your database, if you're running mariadb or postgres, I would check they're working. |
Yes, apparently. Only thing, that happened, was a server restart. Any way to get more detailed logs? |
Just noticed you're using br0 - you really shoudn't be using that network mode nor do we recommend it. by default that network mode blocks communication for the container from the rest of the host. Seems like your issue is how you've configured your containers on unraid. |
I had it working absolutely fine for weeks with br0, so it gets an own IP adress and nginx proxy to it. Where else would you place it? It requires ports 80/443, so Host or Bridge network is a no-go. |
So something would've changed in your unraid system which would be blocking this. There is no need to use br0 networking. While yes you do get port conflicts (just use different port numbers) when using docker networking, you can still use the normal ports when the containers are communicating via the docker network so that traffic stays within your host. With what you've currently done, traffic is leaving and entering your server. |
eth0 is bridged to br0, so that's not a problem (and it used to work). Any way to get more detailed logs on what's happening exactly? |
Your container is unable to talk with your database container, your host is blocking it. I would suggest not using br0 network to test. |
And in terms of getting more details of logs, no. |
Got it working again - host traffic pointed me in the right direction. You'll find posts on it at least since Unraid 6.8.2: That is also why I did not check networking when showing no change and being on Anyhow, if you suffer from the same issue, go to settings and without changing anything, just stop and start docker service, and host access will work again, until the next reboot. Case closed, thanks! |
Is there an existing issue for this?
Current Behavior
Use nextcloud as you would usually - after a timeout run into this error:
Expected Behavior
I can use nextcloud normally again
Steps To Reproduce
Try to use/connect to nextcloud
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: