Search results

Also confirming that "disabling" that option on Service Plans does not disable it on any of my customers. If someone has that option on, even when I'm synching the service plan, the Custom Error Documents remain ON until I manually disable it.

I would not be posting this if I didn't tried that before. No, disabling CUSTOM ERROR DOCUMENTS on the Service Plan does not fix the issue. If the customer creates a new site or I have to "tweak" the Service plan and unhooks from the service plan, that option will turn on again by itself, since...

This is not resolved. The option for Custom Error Documents is enabling by itself every time a plan is unsynced and it is re-enabling custom error documents. We need a permanent solution to this.

Username: TITLE NGINX only not working when Custom Error Documents is enabled on a WordPress installation PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Version 18.0.45 Update #2 CentOS Linux 7.9.2009 (Core) PROBLEM DESCRIPTION When the option Custom Error Documents is enabled...

Yes. It's freaking unbelievable. We are actually paying for a license of a software that should be friendly with us. This information must be stated not only within Plesk control panel but also on their official documentation. For starters, any person searching for this on their Issues here...

That article is TRULY LAME and poorly written. They only state that "This issue has been addressed in Plesk Obsidian 18.0.34 where new WordPress installations work with PHP-FPM served by nginx". But they do not state the obvious. Which is: For the new PHP-FPM served by nginx configuration...

No, you do not need to add that. Just go site by site and be sure to disable (uncheck) Custom Error Documents and everything will start working again.

I've duplicated this information from another post because I am sure more than one people will realize they had this dreaded option turned on by default without knowing it. It should be working out of the box as long as you DO NOT HAVE THE CUSTOM ERROR DOCUMENTS enabled. I've literally burn my...

It should be working out of the box as long as you DO NOT HAVE THE CUSTOM ERROR DOCUMENTS enabled. I've literally burn my head off trying to make it work until I found out that the "checkbox" for Custom Error Documents was enabled by default. Be sure to disable Custom Error Documents from your...

Does anyone know how to to turn off the proxy mode server-wide?. I have more than 300 domains. I do not want to go one by one.

Can you please explain why this is not working on 95% of my sites?. I can only make it work if I create a new WordPress site, older sites are still broken. On top of that, if a newly created site that is working with NGINX working as native is changed to Apache and then switched back to NGINX...

They said they fixed it in the last update but it only works for newly created sites AFTER the update was implemented. For older sites it's still not working!!!

This is not fixed. Permalinks are NOT working in the last version of Plesk when FPM is selected with NGINX and the Proxy mode is not enabled. I only get 404 errors in everything except the homepage. If you implemented this it would be good to explain HOW so we can check why it's not working.

Yes but that solution will work if you just want to use Apache as webserver and nginx as a simple proxy. It does not fix the issue for when you have proxy mode disabled and NGINX is the only one serving the content.

I've been using nginx as a native webserver for well over a year without ZERO issues on WordPress sites and I manage more than 300 sites over several Plesk servers. They've changed the nginxvirtualdomain templates and now I cannot get my custom rules to work again. Your reply although true in...

This topic should be pinned. I've search months for this. I did not knew why it wasn't working.

Sadly I need this server online tomorrow so installing Centos 7. I'm so sad :(

I would try it if there was a way. But the installer won't allow me.

Oh man that's a real bummer. I've just installed Centos 8 on my shiny new server and the new Cockpit view is amazing. Now you're telling me that I need to go back to 7 just to install Plesk and then do an upgrade when Plesk supports it. That's bad, I can't reinstall the whole server. Isn't...

According to Anna from Plesk support It was a Plesk bug #PPPM-8078, that is going to be fixed in future updates.