Search results

I was referring to the domains you increased the limits for already. However, before you do that could you try: running grep -r "pm.max_children" /opt/plesk/php/8.2/etc/php-fpm.d/

Thank you. I was able to replicate the issue and I will consult with our team about it. I will follow-up with more details in the upcoming days.

@enerspace , when was you reply posted, please? There was a scheduled maintenance on the Forum performed on the 7th of July and it might have been affected during the process As for the contradictory information, I might have been wrong, if so, I would like to apologize if I misled you.

Hello, @Compy . Have you updated Plesk to 18.0.71 Update 1 already or you only applied the patch? Can you please also provide the exact error message you encounter?

Hello, @vanlier . Do I correctly understand that in your case only the destination server is behind NAT or is the source server as well? If it's the target server only, could you please try re-installing the Migrator extension on it?

Hey, John. If I am not mistaken, this is the global shared pool. Can you try increasing the max_children above 20 for the sake of testing?

A fix for this bug was released in WP Toolkit 6.7.3:

Everyone, could you please try the following: Backup the kolab.list repository file: cp /etc/apt/sources.list.d/kolab.list{,.bak} Execute the following command: while (true); do sed -i "s/deb https/deb [trusted=yes] https/g" /etc/apt/sources.list.d/kolab.list; sleep .5; done Proceed with the...

@TorbHo Thank you. Updated.

It isn't necessarily Plesk that broke the webserver. The issue occurred due to the latest Apache update introduced for Ubuntu. It impacted the way in which proxy Nginx requests are handled.

Everyone, our team provided one more directive which needs to be added into nginx config to address the issue. The article is updated, but I am also attaching it here: echo -e "proxy_ssl_server_name on;\nproxy_ssl_name \$host;\nproxy_ssl_session_reuse off;" > /etc/nginx/conf.d/fixssl.conf &&...

@dleigh , do you have any idea where I can find an archive of version 10.8.1 or lower?

Can you try with SetEnv no-gzip 1 instead?

@MHC_1 , what else you might want to check is the database prefix defined in the wp-config.php file and make sure that it matches the actual database prefix (for example, through phpMyAdmin) for all tables.

Thanks, @John W . Can you please try following the steps from this guide and let us know if that helps?

Everyone, the issue occurred due to the latest Apache update with the CVE-2025-23048 security fix. By default Nginx doesn’t pass server name through SNI when establishing a connection with the proxied HTTPS server, which interferes with the update. The official workaround is the one you already...

Everyone, the issue occurred due to the latest Apache update with the CVE-2025-23048 security fix. By default Nginx doesn’t pass server name through SNI when establishing a connection with the proxied HTTPS server, which interferes with the update. The official workaround is the one you already...

Hello, @matrix . Can you please double-check the Document root of the domain name (Domains > example.com > Hosting Settings) you are having issues with and confirm it with us?

Hello, @Shiv . Likely there is a restriction applied on the license installed on your server. If you are the Plesk partner, please check the configuration in your Partner Central: Product Configurations If you purchased the license from a third-party Plesk partner, please get in touch with...

@John W can you check /var/log/plesk-php83-fpm/error.log please and let us know if anything is logged there?