Possible Causes:
Incorrect Credentials: The username or password in the .env file does not match the credentials configured in the database server.
Insufficient Privileges: The user solvrcyi_admin does not have the necessary privileges to access the database or perform the DELETE operation.
Database Server Configuration:
Password Encoding Issue: If the password contains special characters, they may need to be escaped or quoted in the .env file.
MySQL/MariaDB Authentication Method: The user might be using an authentication method that is not compatible with the application (e.g., caching_sha2_password).
How to Resolve:
Verify Credentials: Ensure that the username and password in the .env file match the credentials used to access the database manually (via a MySQL client or command line).
Check Database User Privileges: Log in to the database as a root or admin user and verify the privileges:
SHOW GRANTS FOR 'solvrcyi_admin'@'localhost';
If privileges are missing, grant them:
GRANT ALL PRIVILEGES ON your_database_name.* TO 'solvrcyi_admin'@'localhost' IDENTIFIED BY 'your_password'; FLUSH PRIVILEGES;
Use the Correct Host: If the application runs on the same server as the database, use DB_HOST=127.0.0.1 or DB_HOST=localhost in the .env file. If on a different server, set DB_HOST to the database server's IP address or hostname.
Escape Special Characters: If the password contains special characters, enclose it in quotes in the .env file:
DB_PASSWORD="your_complex_password!"
Verify Authentication Method: Ensure the user solvrcyi_admin is using a compatible authentication method (e.g., mysql_native_password):
ALTER USER 'solvrcyi_admin'@'localhost' IDENTIFIED WITH mysql_native_password BY 'your_password';
Test the Connection: Try connecting manually using the same credentials as in the .env file:
mysql -u solvrcyi_admin -p -h 127.0.0.1