# MySQL logs "Please use caching\_sha2\_password instead" after upgrade to MySQL 8.0/Xibo 4

**URL:** https://community.xibo.org.uk/t/mysql-logs-please-use-caching-sha2-password-instead-after-upgrade-to-mysql-8-0-xibo-4/30689
**Category:** The Xibo CMS
**Created:** [December 6, 2023, 11:09am UTC](https://community.xibo.org.uk/t/mysql-logs-please-use-caching-sha2-password-instead-after-upgrade-to-mysql-8-0-xibo-4/30689 "2023-12-06T11:09:15Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![alex](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/alex/32/5782_2.png) [@alex](https://community.xibo.org.uk/u/alex)
#### Post date: [December 6, 2023, 11:09am UTC](https://community.xibo.org.uk/t/mysql-logs-please-use-caching-sha2-password-instead-after-upgrade-to-mysql-8-0-xibo-4/30689/1 "2023-12-06T11:09:15Z")

</div>

When you upgrade a self-hosted installation from MySQL 5.7 to MySQL 8.0 as part of the upgrade to Xibo version 4, you may find the following logged in your MySQL logs repeatedly.

> [Warning] [MY-013360] [Server] Plugin mysql\_native\_password reported: ‘‘mysql\_native\_password’ is deprecated and will be removed in a future release. Please use caching\_sha2\_password instead’

The following will update the user record for your `cms` database user to use the newer password format and clear the warning.

```auto
docker-compose stop
docker run --rm -ti -v /opt/xibo/shared/db:/var/lib/mysql mysql:8.0 bash
cd /tmp
echo "ALTER USER cms IDENTIFIED WITH caching_sha2_password BY 'password';" > init.txt
mysqld --init-file=/tmp/init.txt &

```

**Note:**  
If you use `cms_custom-ports.yml` or `cms_remote-mysql.yml` then be sure to add the `-f` parameter to the `docker-compose` commands as you would normally. Substitute `/opt/xibo/shared/db` for the correct path to the `shared/db` directory for your installation. **Substitute `password` with the password for your `cms` user as shown in `config.env`.**

Wait for the MySQL server to start fully and report that it’s ready to start acceping connections, then hit the `Enter` key and type

```auto
exit

```

Then bring the containers back up

```auto
docker-compose up -d

```

The warning should be gone from the logs.