-
-
Notifications
You must be signed in to change notification settings - Fork 26
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] All red Xs for database with mariadb docker #46
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
for the container, you need to be using host wildcard, not local host when creating the user: |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
as j0nny stated, OP has restricted the user to only login from mariadb itself, not from projectsend. for the tag-along user, they put localhost implying projectsend is the database, which it is not. Closing this as the solution to OP was provided but no response. |
Is there an existing issue for this?
Current Behavior
New to setting up / using databases and new to projectsend. I am using unraid to run linuxserver's projectsend docker container. Using mariadb docker for database. I created a new database 'projectsenddb' and given user 'projectsend' full access to it. I tried to input this information to projectsend for database setup and am seeing all red x's.
Expected Behavior
Database should connect with green checks.
Steps To Reproduce
CREATE DATABASE projectsenddb; CREATE USER 'projectuser'@'localhost' IDENTIFIED BY 'password'; GRANT ALL PRIVILEGES ON projectsend.* TO 'projectuser'@'localhost'; FLUSH PRIVILEGES;
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: