413 Request Entity Too Large by phpmyadmin

Started by ali118, January 22, 2017, 07:54:04 AM

Previous topic - Next topic

ali118

413 Request Entity Too Large
When I upload a database.sql I get this error.

nginx
this problem by phpmyadmin

Gogo

Try to use mysql dumpers to import/export large databases and any kind of large entities. eg. mysqldumper.net
Or if you are familiar with shell you can simply use mysql -uUSER -pPASSWORD database_name < file_name.sql

I had same problem but I didn't even try to find solution to fix that because I used shell cmd to import fajl, it's easier than searching for a solution.

Sandeep

#2

client_max_body_size 500M;


Add this line in /usr/local/cwpsrv/conf/cwpsrv.conf under http {

then restart the cwp
systemctl restart cwpsrv.service



you can increase or decrease client_max_body_size - 500M to the desired value according to your needs

also applied to rouncube and phpmyadmin

Sandeep

#3
to increase php upload limit modify php.ini memory limit :
/usr/local/cwp/php71/php.ini

then restart the cwp and  cwp php
systemctl restart cwpsrv.service
systemctl restart cwp-phpfpm.service

also applied to rouncube and phpmyadmin

OfficePlus NC

#4
Thank you,

I encountered the same problem with a 1.8MB SQL file and CentOS 7

The solution solved my problem

client_max_body_size 500M;

Administrator

if this is centos 7 then try

yum -y remove cwpsrv
yum -y install cwpsrv
/scripts/restart_cwpsrv

problemao

Quote from: pauliakas on January 31, 2017, 03:35:31 PM
Not helping for me.
I change this line but still cant import SQL 1MB

Same here... any1 find a solution to fix the import database at phpmyadmin?


joeey

After trying the above suggestions I kept getting the 413 error on my file upload. I related this to a timeout issue, maybe server slow to read files so I changed the following line

keepalive_timeout  65;

to

keepalive_timeout  650;

File location /usr/local/cwpsrv/conf/cwpsrv.conf under http {

That seemed to do the trick. Now my files upload ok.

Remember to restart services especially apache.

overseer

I haven't actually encountered this myself, probably because I use the CLI for larger DB loading & backup tasks. But thanks for resurfacing this thread! I'll enact it on my servers for the sake of clients who live & die by phpMyAdmin.