Closed karltriest closed 4 years ago
2020-05-20 15:04:43 - error - yii\web\HttpException:400
yii\web\BadRequestHttpException: Unable to verify your data submission. in /usr/share/nginx/vendor/yiisoft/yii2/web/Controller.php:190
Stack trace:
#0 /usr/share/nginx/vendor/craftcms/cms/src/web/Controller.php(134): yii\web\Controller->beforeAction(Object(yii\base\InlineAction))
#1 /usr/share/nginx/vendor/craftcms/cms/src/controllers/TemplatesController.php(69): craft\web\Controller->beforeAction(Object(yii\base\InlineAction))
#2 /usr/share/nginx/vendor/yiisoft/yii2/base/Controller.php(155): craft\controllers\TemplatesController->beforeAction(Object(yii\base\InlineAction))
#3 /usr/share/nginx/vendor/craftcms/cms/src/web/Controller.php(178): yii\base\Controller->runAction('render', Array)
#4 /usr/share/nginx/vendor/yiisoft/yii2/base/Module.php(528): craft\web\Controller->runAction('render', Array)
#5 /usr/share/nginx/vendor/craftcms/cms/src/web/Application.php(291): yii\base\Module->runAction('templates/rende...', Array)
#6 /usr/share/nginx/vendor/yiisoft/yii2/web/Application.php(103): craft\web\Application->runAction('templates/rende...', Array)
#7 /usr/share/nginx/vendor/craftcms/cms/src/web/Application.php(276): yii\web\Application->handleRequest(Object(craft\web\Request))
#8 /usr/share/nginx/vendor/yiisoft/yii2/base/Application.php(386): craft\web\Application->handleRequest(Object(craft\web\Request))
#9 /usr/share/nginx/html/index.php(48): yii\base\Application->run()
#10 {main}
@karltriest The MySQL docs have a whole page dedicated to that "MySQL server has gone away" message (https://dev.mysql.com/doc/refman/8.0/en/gone-away.html), but 9 times out of 10 when we see it, it's because you need to bump your MySQL server's max_allowed_packet and/or wait_timeout settings to higher values.
@angrybrad I changed the MySQL options to max_allowed_packet to 67108864 (64MB), (default/was 4MB) supposedly the default for wait_timeout on mysql is 28800 (8 hours), so i don't think that was an issue but I added in 28800 just in case.
Unfortunately the bug persists.
@karltriest did you verify the settings took? i.e. SHOW VARIABLES LIKE '%max_allowed_packet%';
If they did, the other setting I've setting that works is bumping innodb_log_file_size
higher.
@angrybrad turns out that it was the max_allowed_packet setting, and the server needed a reboot in order for the setting to take. thanks! really appreciate your help
@karltriest glad you're all sorted!
Description
making a draft of a table field then publishing that draft causes "An internal server error occurred."
Steps to reproduce
*note: publishing the exact same data without first making a draft works fine
Additional info
Error Log