How to Increase MySQL max_allowed_packet Size • WP STAGING

TL;DR — To increase max_allowed_packet size permanently, add max_allowed_packet=1G under [mysqld] in my.cnf and restart MySQL. For an immediate fix without a restart, run SET GLOBAL max_allowed_packet=1073741824; in a MySQL client. Confirm the change with SHOW VARIABLES LIKE 'max_allowed_packet';.

Contents

What max_allowed_packet Controls
Which Method Should I Use?
How to Set max_allowed_packet Permanently
How to Set max_allowed_packet Temporarily
What to Do If the Fix Does Not Take Effect
Related Articles

Visual representation: Increase max_allowed_packet Size in MySQL. Image created by Dali.

When MySQL receives a query with a data packet larger than the max_allowed_packet value, it throws a "Packet too large" error and closes the connection. This is a common MySQL error in WordPress environments — it surfaces during MySQL packet size errors during push, packet too large during cloning, large database imports, and site migrations. The default value is set low relative to what large WordPress sites need, but increasing it is straightforward once you identify the right method for your hosting environment.

For example, if the WP STAGING backup restore fails because of a too-small packet size, the error message shows the size of the offending query so you can adjust max_allowed_packet accordingly. In the current version of WP STAGING, the plugin throttles and executes database queries dynamically based on your server’s maximum allowed packet size, but the underlying MySQL limit still applies to direct imports and third-party tools.

You have two options to change the MySQL max_allowed_packet size: a permanent change in the MySQL configuration file, and a temporary change via SQL — both covered below.

What max_allowed_packet Controls

The max_allowed_packet system variable sets the maximum size of a single communication packet between the MySQL client and server. When a query, result row, or stored routine definition exceeds this limit, MySQL terminates the connection and logs an error.

Common symptom patterns:

"Packet too large" — MySQL rejects the query immediately.
"MySQL server has gone away" — the connection drops during a long-running import.
Push or restore failures in WP STAGING when the site contains large post revisions, serialized option values, or image metadata stored as post meta.
Errors during mysqldump restoration or phpMyAdmin import.

In our support queue, the most common trigger is a WP STAGING push that includes large image libraries or post revisions stored as post meta. We have also seen this block increase max_allowed_packet before migrating to a new host — catching the limit before a migration avoids failed imports mid-transfer.

Which Method Should I Use?

Your environment	Best method
VPS or dedicated server with SSH access	Edit `my.cnf` — permanent
Shared hosting (no SSH)	Contact your host; phpMyAdmin can inspect the current value but not change it permanently
AWS RDS for MySQL	Modify a DB parameter group in the AWS console
DigitalOcean Managed MySQL	Set via the "Configuration" tab in the control panel
Need an immediate fix without a restart	`SET GLOBAL` SQL command — temporary, resets on restart

If you are unsure which config file MySQL is reading, run mysql --verbose --help | grep my.cnf in a terminal to see the full search order.

How to Set max_allowed_packet Permanently

A permanent change survives MySQL server restarts. The method depends on your hosting environment.

VPS or Dedicated Server: Edit my.cnf

Open my.ini (Windows) or my.cnf (Linux/macOS) in the MySQL server installation directory. On most Linux systems the file is at /etc/mysql/my.cnf or /etc/my.cnf. For MySQL server configuration via the command line, verify the exact path first with mysql --verbose --help | grep my.cnf.
Locate the [mysqld] section. The directive must go under [mysqld], not [mysql] or [client] — placing it in the wrong section is the most common reason the fix appears to work but has no effect.
Find or add the max_allowed_packet line. To set the value to 1 GB:

[mysqld]
max_allowed_packet=1G

Save the file, then restart MySQL:

sudo systemctl restart mysql

Verify the new value:

SHOW VARIABLES LIKE 'max_allowed_packet';

Shared Hosting: Inspect via phpMyAdmin

On shared hosting without SSH access, you can check the current max_allowed_packet value by navigating to phpMyAdmin → Variables and searching for max_allowed_packet. To increase it permanently, contact your hosting provider — this is a server-level setting that requires administrative access outside the shared control panel.

Managed Databases: AWS RDS and DigitalOcean

Cloud-managed MySQL services expose the variable through their control panels rather than a config file:

AWS RDS for MySQL — open the DB instance in the AWS console, navigate to its associated parameter group, and set max_allowed_packet. Apply the updated parameter group and reboot the instance for the change to take effect.
DigitalOcean Managed MySQL — navigate to your database cluster’s Configuration tab and update max_allowed_packet there.

For both platforms, set the value before running a large import or migration. See increase max_allowed_packet before migrating for a migration pre-flight checklist.

How to Set max_allowed_packet Temporarily

The max_allowed_packet variable can be set globally by running a SQL command. This takes effect immediately — no restart required — but the value resets when the MySQL server restarts. Always follow up with the permanent my.cnf edit if you need the change to persist.

However, if you do not change it in the my.ini file, the value will always reset when the server restarts, even if you set it globally.

To change the max allowed packet for everyone to 1 GB until the server restarts:

SET GLOBAL max_allowed_packet=1073741824;

Verify immediately:

SHOW VARIABLES LIKE 'max_allowed_packet';

This method is useful for unblocking max_allowed_packet errors on restore in progress, or for testing the correct value before committing it to the config file.

What to Do If the Fix Does Not Take Effect

If SHOW VARIABLES LIKE 'max_allowed_packet'; still returns the old value after your change, work through this checklist:

Wrong config section. The directive must be under [mysqld]. Open the file and confirm the section header directly above the max_allowed_packet line.
Wrong config file. MySQL reads multiple files in a specific order and the last matching value wins. Check the actual search path:

mysql --verbose --help | grep my.cnf

MySQL was not restarted. Confirm the service restarted successfully:

sudo systemctl status mysql

File not saved or not readable. Verify the file was saved and that MySQL has read permission on it.
Replica nodes. In a replicated environment, SET GLOBAL applies only to the node you connected to. Each replica requires its own config file update.
Client-side limit. Some database clients set max_allowed_packet at connection time. If the client value is lower than the server value, the client limit applies regardless of the server setting.

We have seen the fix fail silently when the [mysqld] section header was missing from a freshly provisioned my.cnf that contained only [mysql] entries — MySQL parses the file without errors but ignores the directive.

For related server memory limit errors that appear alongside MySQL packet errors in log files, the same config-section rules apply. For other MySQL and PHP server limits, a similar approach to editing the server config file resolves the issue.

Increase max_allowed_packet Size in MySQL