Database too large import failure 502 Bad Gateway error solution

If your website database is too large when restoring a backup, it usually fails to import, prompting 502 Bad Gateway. The solution can be to increase PHP timeout; a more stable solution is to directly use server commands to import. Usually, we rely on the phpMyAdmin interface to import databases, but if the database is too large, it may exceed the server processing time and report a 502 error. Increasing the timeout can solve part of the problem. However, if the database is too large, even modifying the timeout may still fail to import. Below, Naiba shares a commonly used method in work, which is to directly use commands to import from the server.

mysql -u用户名 -p密码 数据库名 < 数据库名.sql #mysql -uroot -p123 abc < abc.sql

Using commands and demonstration as above, directlyconnect to the VPS, then use the mysql command to import. Another method is to import in volumes, which can be done when previously exportingdatabase backupYou can directly split and package it into volumes, but Naiba hasn't used it yet. If you're interested, you can search for related articles yourself.