MySQL Authentication Fix

services:
nginx:
image: nginx:latest
container_name: ot-nginx
ports:
– "3800:80"
networks:
– ot-app-network
volumes:
– ./nginx:/etc/nginx/conf.d
– ./applications/dndw-test:/var/www/dndw-test
depends_on:
– php

php:
build:
context: ./php
container_name: ot-php
volumes:
– ./applications/dndw-test:/var/www/dndw-test
expose:
– "9000"
working_dir: /var/www
networks:
– ot-app-network

ottmysql:
image: mysql:8.0
container_name: ot-mysql
environment:
MYSQL_ROOT_PASSWORD: rootpassword
MYSQL_DATABASE: site_db
MYSQL_USER: user
MYSQL_PASSWORD: userpassword
volumes:
– ./mysql/data:/var/lib/mysql
ports:
– "3308:3306"
networks:
– ot-app-network

adminer:
image: adminer
container_name: ot-adminer
restart: always
ports:
– '3801:8080'
networks:
– ot-app-network
depends_on:
– ottmysql

networks:
ot-app-network:
driver: bridge

Warning: mysqli_real_connect(): The server requested authentication method unknown to the client [caching_sha2_password] in /var/www/dndw-test/site/web/wp/wp-includes/wp-db.php on line 1753

Warning: mysqli_real_connect(): (HY000/2054): The server requested authentication method unknown to the client in /var/www/dndw-test/site/web/wp/wp-includes/wp-db.php on line 1753
The server requested authentication method unknown to the client

Error establishing a database connection
This either means that the username and password information in your wp-config.php file is incorrect or we can’t contact the database server at ottmysql. This could mean your host’s database server is down.

Are you sure you have the correct username and password?
Are you sure you have typed the correct hostname?
Are you sure the database server is running?

To fix this issue, you can either:

### Option 1: Change MySQL Authentication Method
You can change the authentication method for the MySQL user to `mysql_native_password`, which is compatible with older clients.

1. Access the MySQL container:

docker exec -it ot-mysql mysql -u root -p

2. Log in with the root password you set (`rootpassword`).

3. Run the following SQL command to change the authentication method for the MySQL user (`user` in your case):

ALTER USER 'user'@'%' IDENTIFIED WITH mysql_native_password BY 'userpassword';

4. Exit MySQL:

exit

5. Restart your MySQL container:

docker restart ot-mysql

After making this change, the WordPress installation should be able to connect to the database without issues.

### Option 2: Update PHP MySQL Client
Ensure that your PHP MySQL client supports `caching_sha2_password`. You can update your PHP container to include the necessary MySQL client libraries.

1. Add the following to your `Dockerfile` in the `php` service to install the necessary MySQL extensions:

RUN apt-get update && apt-get install -y libmysqlclient-dev && docker-php-ext-install mysqli

2. Rebuild your PHP container:

docker-compose build php
   docker-compose up -d

After this, check if the connection works with the `caching_sha2_password` method.

Choose one of the above options based on your setup. The first one is typically the easiest to implement and should resolve the issue.

Warning: include(/var/www/dndw-test/site/web/app/uploads/cache/4f354e9f1ae1e3423bbf2edb38f55032436c7cbf.php): failed to open stream: No such file or directory in /var/www/dndw-test/site/web/app/themes/dndw-ls/vendor/illuminate/view/Engines/PhpEngine.php on line 43

Warning: include(): Failed opening '/var/www/dndw-test/site/web/app/uploads/cache/4f354e9f1ae1e3423bbf2edb38f55032436c7cbf.php' for inclusion (include_path='.:/usr/local/lib/php') in /var/www/dndw-test/site/web/app/themes/dndw-ls/vendor/illuminate/view/Engines/PhpEngine.php on line 43

To fix this issue, you can try the following steps:

### 1. **Ensure the Cache Directory Exists**
The error indicates that the cache directory or the specific cache file does not exist. Make sure the `uploads/cache` directory is present and writable.

1. **Create the missing directories:**
If the directory `/var/www/dndw-test/site/web/app/uploads/cache/` does not exist, create it manually:

mkdir -p /var/www/dndw-test/site/web/app/uploads/cache

2. **Set the correct permissions:**
Ensure that the web server user (e.g., `www-data` or `nginx`) has permission to write to this directory:

sudo chown -R www-data:www-data /var/www/dndw-test/site/web/app/uploads
   sudo chmod -R 775 /var/www/dndw-test/site/web/app/uploads/cache

### 2. **Clear the Cache**
After ensuring the directory exists and has the correct permissions, clear the cache to regenerate the necessary files.

For Laravel-based projects (or WordPress with Laravel-style caching), run the following commands inside the PHP container to clear the cache:

docker exec -it ot-php bash
php artisan cache:clear
php artisan view:clear

If this is for WordPress, clearing the cache might involve deleting the contents of the cache directory manually or through a plugin depending on your caching setup.

### 3. **Check for File Permissions**
Ensure that all files inside the `uploads/cache` directory have proper permissions. Sometimes a specific PHP script might not have access to create or write files if the permissions are too restrictive.

### 4. **Review Nginx and PHP Logs**
If the issue persists, check the Nginx and PHP logs for additional details on why the file isn't being written. It might provide more context about missing or incorrect configurations.

After performing these steps, the issue should be resolved if it's related to missing directories or file permission issues. Let me know if you still encounter problems after trying these fixes.

### Steps to Resolve

1. **Ensure Required Dependencies are Installed**
Ensure your Docker container has all the required build tools for `node-sass`. In your PHP container's `Dockerfile`, add:

RUN apt-get update && apt-get install -y build-essential python3

Then rebuild your Docker container:

docker-compose build php
   docker-compose up -d

2. **Manually Rebuild `node-sass`**
If the error persists, you may need to manually rebuild `node-sass`:

yarn install
   yarn add node-sass@5.0.0

Or rebuild only `node-sass`:

yarn rebuild node-sass

3. **Ensure Compatibility with Node.js Version**
`node-sass@5.0.0` is compatible with Node.js versions up to 16. If you're using a newer Node.js version (e.g., 18 or 21), consider upgrading to `node-sass@6.x` or switching to `dart-sass` (preferred).

– To upgrade `node-sass`, run:

yarn add node-sass@latest

– To switch to `dart-sass`:

yarn remove node-sass
     yarn add sass

Then, update your build configuration (e.g., in `webpack` or `vite.config.js`) to use `sass` instead of `node-sass`.

4. **Clean Yarn Cache**
Corrupted or outdated Yarn cache may also cause issues. Clear it by running:

yarn cache clean

Then reinstall dependencies:

yarn install

5. **Verify and Debug**
If the problem persists:
– Check the Node.js version in your Docker container:

node -v

– Verify that all dependencies match the supported Node.js version.

### If All Else Fails
If you still encounter the issue, post the exact error or log details so I can help debug further.