Troubleshooting·2024-03-07·4 min read

MySQL Error 2013: Lost Connection During Query (Import Fix)

Imports failing with ERROR 2013? The connection is dropping mid‑query. Here's how to stabilize it.

ERROR 2013 means MySQL dropped the connection while processing a long or heavy query.

Common triggers

Split the dump into smaller chunks and import them sequentially. This reduces query time per request.

Related: How to Fix phpMyAdmin Import Timeout Errors and MySQL Error 2006: Server Has Gone Away.

Avoid connection drops

Split your dump into smaller, safer files.

They’re related. Both indicate the connection died during a heavy query.

Yes. MySQL CLI is more resilient, but splitting still helps.

Adminer is lighter than phpMyAdmin, but imports can still time out. Here’s how to fix it.

Your import dies with 'MySQL server has gone away'. Here's what's happening and how to fix it.

Getting 'Script timeout passed' when importing SQL files? Here's how to actually fix it without touching server settings.

Imports that freeze mid‑way are usually caused by big statements or timeouts. Split the dump.