Wordpress Autoinstaller hangs after the Update 1.7.43

kevinstan

Works fine with the previous version, but will not complete with the new update. I had to downgrade just to allow WP autoinstaller again.

Writing database logins to wp-config.php Shuffling WordPress Salts in wp-config.php file Added mu-plugin to force HTTPS for wp-admin behind Varnish. Setting files permissions to '755' Setting files owner to 'useraccount' Set FS_METHOD 'direct' in wp-config.php file. PHP container is running and WP-CLI is functional, starting process.. Testing database connection.. mariadb container is healthy, proceeding with database operations.. Creating new MySQL database gl2cbfrq Creating new MySQL user wlirov1t with password mPwMGZYlWLCq Importing WordPress tables in the database

MixDelo

kevinstan From OpenAdmin > Settings > OpenPanel increase Max startup time for MySQL

Sources:

I get the same error on a new user, but just clicking the retry button works for me. Is it same in your case? Works fine on existing users..

From the OpenPanel error log, mysql is not responding to select 1; after 10sec - this Is configurable in OpenPanel settings, simply increase the timeout, restart openpanel and should work as expectted.

kevinstan

MixDelo

Thank you for the response. The retry button does not work in my case - it then says there is already an .htaccess file.

Also, I tried first increasing from 10sec to 30sec and even 60sec to see if the timeout was due to that, but it did not work either.

All was working fine with creating new users and using auto-install for WP until the new update, and then it completely stopped and started to hang like this.

I reverted back to the previous OpenAdmin/OpenPanel version and then it started working again, so I am not sure what is happening.

MixDelo

kevinstan strange, in my case that works - I'm using 1.7.44

if you can, tail the log at the time the error occurs: https://openpanel.com/docs/articles/support/how-to-troubleshoot-openpanel-error#dev-mode and report it to github or share here, so @stefan can reproduce and patch it in the next update