Can't upgrade to mysql8 linked with wordpress

Question

Can't upgrade to mysql8 linked with wordpress

Carrubbers 20

Hi - I'm trying to upgrade mySQL5.7 to 8.0 and when I chose to validate it comes up with the following errors belo..

For the first one, I did change my defauly char set in the database to be utf8mb4 in the parameter settings, and I did change wp-config.php to say the same, but still the same error.

For the second, I have no idea where to start or look of how to fix it.

How can I fix it?

Thanks

Warning: Usage of utf8mb3 charset

The following objects use the utf8mb3 character set. It is recommended to convert them to use utf8mb4 instead, for improved Unicode support.

projectxxxxxx_database - schema's default character set: utf8

Error: Usage of deprecated configurations.

ConfigName: sql_mode

ConfigValue: ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER

AllowedValues: ,ALLOW_INVALID_DATES,ANSI_QUOTES,ERROR_FOR_DIVISION_BY_ZERO,HIGH_NOT_PRECEDENCE,IGNORE_SPACE,NO_AUTO_VALUE_ON_ZERO,NO_BACKSLASH_ESCAPES,NO_DIR_IN_CREATE,NO_ENGINE_SUBSTITUTION,NO_UNSIGNED_SUBTRACTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,ONLY_FULL_GROUP_BY,PAD_CHAR_TO_FULL_LENGTH,PIPES_AS_CONCAT,REAL_AS_FLOAT,STRICT_ALL_TABLES,STRICT_TRANS_TABLES,TIME_TRUNCATE_FRACTIONAL

InvalidValue: NO_AUTO_CREATE_USER

Moderator: Moved from SQL Server Migration Assistant

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Carrubbers 20 Reputation points

2026-02-04T11:51:19.41+00:00

So this issue I have is that I'm not an Azure expert at all. I only used it to setup a wordpress site.

I recently got a communication from Azure that the Azure Database for MySQL – Flexible Server is running version 5.7 and needs to be upgraded to 8.0 , and then acutally 8.4 to get the latest.

I have the above issues that I need to fix to get the upgrade. However, I can't connect to the SQL database as that's set to only be connected to locally. I can't crate a local Azure VMachine as my subscription doesn't allow me to create one on the same region, which it needs to be in.

So, currently, even after lots of searches for many many hours; I am still stuck in the fact that I can't connect to the SQL database to even try to fix the issues and allow it to be upgraded.

Any ideas of how to get around this? As it stands, I can't think a way around this and will just have to delete my entire website.
Erland Sommarskog 133.7K Reputation points MVP Volunteer Moderator

2026-02-04T21:29:22.59+00:00

In my defence; this is an issue that came up under Azure using a service I pay for within Azure, hence why when I clicked help, it took me to this page. Thanks.

Sorry, that was not clear to me. I have changed the tag to the tag for MySQL in Azure. Hopefully, some support person who monitor this tag, will pick up your question.

(I also deleted our earlier posts, to reduce the noise in the thread.)
Carrubbers 20 Reputation points

2026-02-05T12:32:20.21+00:00

Hi @Manoj Kumar Boyini Thank you very much for the response.

I've changed the No User setting and when I go to validate I now only get the utf8mb3 error message, so I'm getting closer.

When you mention running "ALTER SCHEMA <your_database_name> DEFAULT CHARACTER SET utf8mb4;"

I'm not sure where or how I actually run this. I have read about creating a temporary local VM, but with my Azure subscription I cannot create one in the same region.

Is there another way to run the above command?

Thanks
Manoj Kumar Boyini 12,735 Reputation points Microsoft External Staff Moderator

2026-02-05T13:23:34.8833333+00:00

Hi Carrubbers,

You do not need to create a VM, either locally or in Azure, to run the following command:

ALTER SCHEMA <your_database_name> DEFAULT CHARACTER SET utf8mb4;

This command is executed the same way as any other MySQL statement by connecting to your Azure Database for MySQL using a MySQL client. Azure does not require a VM or a resource in the same region for this.

You can run the command from Azure Cloud Shell, which is the easiest option and does not require any infrastructure setup. Open the Azure Portal, click the Cloud Shell icon in the top-right corner, choose Bash, and connect to your MySQL server using the mysql client. Once connected, simply run the ALTER SCHEMA command.

If you prefer a graphical tool, you can also use MySQL Workbench or Azure Data Studio from your local machine. Create a connection to <server-name>.mysql.database.azure.com, use the username in the format <username>@<server-name>, ensure SSL is enabled, open a query window, and run the same SQL command.

You can also run the command from your local computer using the MySQL command-line client, as long as your public IP address is allowed in the server’s Connection Security (firewall) settings and SSL is enabled.

If your MySQL server is configured for private network access only (VNet-only), then Cloud Shell and local clients will not be able to connect. In that case, the command must be run from a machine that already has access to the VNet, such as an internal VM, a machine connected through VPN, or by asking a DBA or infrastructure administrator to run this one-time command for you.

After running the command, the database schema’s default character set will be updated to utf8mb4. This clears the utf8mb3 validation warning and allows the MySQL 8.0 upgrade validation to complete. Existing tables are not modified by this change.

Hope this helps, Please let us know if you have any questions and concerns.

If this solution helped resolve your issue, please consider clicking ‘Accept Answer’ to help others find it easily.
Erland Sommarskog 133.7K Reputation points MVP Volunteer Moderator

2026-02-05T21:33:54.07+00:00

I note on my own MySQL database in Azure (which I only use for very occasional testing), that I am required to upgrade from 8.0 to 8.4 before some date later this year. I guess Carrubbers also will see this, once the upgrade to 8.0 has completed. (My own upgrade is rolling now.)
Carrubbers 20 Reputation points

2026-02-05T21:35:19.66+00:00

Hi @Manoj Kumar Boyini

Thanks for the help. The mysql server was configured for private network access only as that was done automatically.

Through a whole stuggle of thinsg I managed to create a VPN gateway into Azure and connect in, but when I try connecting to the database with MySQL workbench, it can't connect.

Is there some VPN gateway to Vnet connection to make in Azure?

Thanks
Manoj Kumar Boyini 12,735 Reputation points Microsoft External Staff Moderator

2026-02-05T22:40:12.9033333+00:00

Hi Carrubbers,

When Azure Database for MySQL Flexible Server is configured for private network access, creating a VPN gateway by itself is not enough. Your client must be able to route traffic into the correct virtual network and resolve the MySQL server name to its private IP address.

First, confirm that your Point-to-Site VPN connects you to the same virtual network where the MySQL Flexible Server is deployed, or to a peered virtual network that has connectivity to it. No additional gateway-to-gateway configuration is required beyond this.

The most common missing piece is DNS resolution. MySQL Flexible Server continues to use the hostname <server-name>.mysql.database.azure.com. From your local machine, while the VPN is connected, run:

nslookup <server-name>.mysql.database.azure.com

This must resolve to a private IP address in the 10.x, 172.x, or 192.168.x range. If it resolves to a public IP or does not resolve at all, MySQL Workbench will not be able to connect.

To fix this, make sure the Private DNS zone used by MySQL Flexible Server (mysql.database.azure.com) is linked to the virtual network that your VPN gateway is connected to. You can verify this in the Azure Portal under Private DNS zones → mysql.database.azure.com → Virtual network links.

Once DNS resolution is correct, you can connect from MySQL Workbench using the server name <server-name>.mysql.database.azure.com, the username in the format <admin-user>@<server-name>, port 3306, and SSL set to Required. Do not use the private IP directly, as SSL certificate validation will fail.

You already have the VPN in place. The remaining step is ensuring proper DNS resolution over the VPN to the MySQL server’s private IP. Once that is working, the connection from MySQL Workbench should succeed.

References:
https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-networking-vnet
https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-networking-private-link
https://techcommunity.microsoft.com/blog/adformysql/how-to-resolve-dns-issues-with-azure-database-for-mysql/4047706

Hope this helps, Please let us know if you have any questions and concerns.
Manoj Kumar Boyini 12,735 Reputation points Microsoft External Staff Moderator

2026-02-06T17:12:40.46+00:00

Hi Carrubbers,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Carrubbers 20 Reputation points

2026-02-06T21:45:27.6566667+00:00

Hi @Manoj Kumar Boyini

Thanks. I did find the VPN was connecting to the wrong virtual network, so I deleted it and created a new one. Now getting trouble connecting into that one, so will need some time to work out what's going on. I'll come back to you...
Carrubbers 20 Reputation points

2026-02-07T00:04:48.6033333+00:00

Hi @Manoj Kumar Boyini

Editing this response... again.

OK I'm in to the database - still had DNS issues, but I found the IP address of the database and it seemed to work with MySQL Workbench.

I just ran the Alter Schema command and it seemed to upgrade the database to version 8.0. Now upgrading to 8.4 to keep it up to date.

Upgrade complete - thank you Manoj for you amazing support. You have saved me a lot of pain. I am truely grateful to you for you patience and knowledge.

Regards.
Manoj Kumar Boyini 12,735 Reputation points Microsoft External Staff Moderator

2026-02-07T00:32:06.64+00:00

Hi Carrubbers,

That’s fantastic news - well done!

Answer accepted by question author

Answer recommended by moderator

0 additional answers

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Carrubbers 20 Reputation points

2026-02-04T11:51:19.41+00:00

So this issue I have is that I'm not an Azure expert at all. I only used it to setup a wordpress site.

I recently got a communication from Azure that the Azure Database for MySQL – Flexible Server is running version 5.7 and needs to be upgraded to 8.0 , and then acutally 8.4 to get the latest.

I have the above issues that I need to fix to get the upgrade. However, I can't connect to the SQL database as that's set to only be connected to locally. I can't crate a local Azure VMachine as my subscription doesn't allow me to create one on the same region, which it needs to be in.

So, currently, even after lots of searches for many many hours; I am still stuck in the fact that I can't connect to the SQL database to even try to fix the issues and allow it to be upgraded.

Any ideas of how to get around this? As it stands, I can't think a way around this and will just have to delete my entire website.
Erland Sommarskog 133.7K Reputation points MVP Volunteer Moderator

2026-02-04T21:29:22.59+00:00

In my defence; this is an issue that came up under Azure using a service I pay for within Azure, hence why when I clicked help, it took me to this page. Thanks.

Sorry, that was not clear to me. I have changed the tag to the tag for MySQL in Azure. Hopefully, some support person who monitor this tag, will pick up your question.

(I also deleted our earlier posts, to reduce the noise in the thread.)
Carrubbers 20 Reputation points

2026-02-05T12:32:20.21+00:00

Hi @Manoj Kumar Boyini Thank you very much for the response.

I've changed the No User setting and when I go to validate I now only get the utf8mb3 error message, so I'm getting closer.

When you mention running "ALTER SCHEMA <your_database_name> DEFAULT CHARACTER SET utf8mb4;"

I'm not sure where or how I actually run this. I have read about creating a temporary local VM, but with my Azure subscription I cannot create one in the same region.

Is there another way to run the above command?

Thanks
Erland Sommarskog 133.7K Reputation points MVP Volunteer Moderator

2026-02-05T21:33:54.07+00:00

I note on my own MySQL database in Azure (which I only use for very occasional testing), that I am required to upgrade from 8.0 to 8.4 before some date later this year. I guess Carrubbers also will see this, once the upgrade to 8.0 has completed. (My own upgrade is rolling now.)
Carrubbers 20 Reputation points

2026-02-05T21:35:19.66+00:00

Hi @Manoj Kumar Boyini

Thanks for the help. The mysql server was configured for private network access only as that was done automatically.

Through a whole stuggle of thinsg I managed to create a VPN gateway into Azure and connect in, but when I try connecting to the database with MySQL workbench, it can't connect.

Is there some VPN gateway to Vnet connection to make in Azure?

Thanks
Manoj Kumar Boyini 12,735 Reputation points Microsoft External Staff Moderator

2026-02-06T17:12:40.46+00:00

Hi Carrubbers,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
Carrubbers 20 Reputation points

2026-02-06T21:45:27.6566667+00:00

Hi @Manoj Kumar Boyini

Thanks. I did find the VPN was connecting to the wrong virtual network, so I deleted it and created a new one. Now getting trouble connecting into that one, so will need some time to work out what's going on. I'll come back to you...
Carrubbers 20 Reputation points

2026-02-07T00:04:48.6033333+00:00

Hi @Manoj Kumar Boyini

Editing this response... again.

OK I'm in to the database - still had DNS issues, but I found the IP address of the database and it seemed to work with MySQL Workbench.

I just ran the Alter Schema command and it seemed to upgrade the database to version 8.0. Now upgrading to 8.4 to keep it up to date.

Upgrade complete - thank you Manoj for you amazing support. You have saved me a lot of pain. I am truely grateful to you for you patience and knowledge.

Regards.
Manoj Kumar Boyini 12,735 Reputation points Microsoft External Staff Moderator

2026-02-07T00:32:06.64+00:00

Hi Carrubbers,

That’s fantastic news - well done!

Answer 1

Hi Carrubbers,

This is expected behavior when upgrading from MySQL 5.7 to MySQL 8.0, and both findings come from documented MySQL 8.0 compatibility requirements.

The utf8mb3 warning appears because your database schema was originally created with the legacy utf8 character set (which maps to utf8mb3). Changing the server default or wp-config.php does not update existing schema metadata. Although this warning does not block the upgrade, it is recommended to update the schema default to utf8mb4 so the validator recognizes it correctly. You can do this by running:

ALTER SCHEMA <your_database_name> DEFAULT CHARACTER SET utf8mb4;

The upgrade-blocking error is caused by the SQL mode NO_AUTO_CREATE_USER. This mode was removed in MySQL 8.0, and if it is still configured, the MySQL 8.0 server cannot start. Azure therefore prevents the upgrade until it is removed.

To fix this, go to Azure Portal → MySQL Flexible Server → Server Parameters, locate sql_mode, and remove NO_AUTO_CREATE_USER from the list. Save the change and allow the server to restart if prompted. After that, rerun the upgrade validation.

Once NO_AUTO_CREATE_USER is removed and the schema charset is updated (recommended), the MySQL 8.0 upgrade validation should complete successfully.

Hope this helps, Please let us know if you have any questions and concerns.

Answer 2

For anyone reading this...

There were steps to follow and I had a more complicated time as for some rason I had 2 virtual networks.
Although I still had DNS issues despite checking my private DNS zone, etc; I found I could get the IP address of the MySQL server and I could ping that through my VPN connection. Applying that to workbench let me in to the database.

Finding the IP of the server, I went to the Private DNS zone of the server, then clicked on the Record Sets, then on the next screen I saw 2 entries; one showing the IP address of the server.
User's image

Superb help from Manoj on this one. What a hero.

Share via

Can't upgrade to mysql8 linked with wordpress

0 additional answers

Your answer