-
-
Notifications
You must be signed in to change notification settings - Fork 782
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
Access to database is denied with MariaDB #2493
Comments
Hello, SHOW grants; |
You could also try with SQLite, PostgreSQL, or MySQL |
I found that my default setting of MariaDB 10 package is not the same as usual, which is So there are two options for my case.
I tried both and both of them works fine. The tricky thing is that during the installation, the hostname Anyway, thanks for your hint! |
Thanks for the feedback @binalloy |
Thanks for the tip! |
This happens when either IPv4 or IPv6 is not correctly set up, or when the database is not listening on IPv4 or IPv6. Everything defaults more and more to IPv6, but there are sometimes elements that are lagging behind. |
I'm using very basic default setup on my NAS regarding network, so I would be surprised this could be the root cause
Looks like, on my NAS, MariaDB is only listening on IPv4, that could be the explanation:
I not sure if reinstalling from scratch would be a good idea for me. |
No need to reinstall @gpion , the new code would only catch the problem earlier. |
No need to reinstall to use the "reworked install procedure" ? Sorry I dont understand. |
I just meant that if your current deployment works, you can just keep it as it is :-) |
Anyway, I've just found why MariaDB was only listening on IPv4 and not IPv6
|
I am trying to run FreshRSS with MariaDB 10 on my NAS. Everything was fine while the installation until I tried to log in. I got the following error:
and the content in
/data/users/username/log.txt
I run the script given in #1243 (comment), and get the following:
The connection to the database seems fine. I can't figure out what's wrong.
The text was updated successfully, but these errors were encountered: