Search results

Open Lite Speed hands down beat the hell out of nginx + apache in the way they are setup in Plesk. Same identical server that hold 200 domains on Plesk (most of them on NGINX) were hitting 50% of the CPU on a Ryzen 5 5600. Same identical server with those 200 domains on Webuzo with Open Lite...

I've migrated over to Webuzo, the same guys behind Softaculous WordPress Manager. Licenses are much cheaper and fair. I get to install the whole system with Open Lite Speed (We were asking for Open Lite Speed in Plesk for years, and they never cared to implement it, being so similar to Apache...

There are a lot of super consistent and stable solutions that work as good (if not better) than Plesk and doesn't cost an arm an a leg.

I am soooo glad that I am currently "moving" out of plesk my last server. I hope to never touch this piece of software ever again. what they are doing is beyond awful and completely unjustified. I'm so happy that I am going to leave this forever since next month. I've imagined they will keep...

Will give you some facts for you. Perfectly optimized server, Ryzen 5 5600 - 64GB RAM - 2 TB RAID1 SSD. (used identical servers for Plesk based and competing control panel) Plesk based server - 96 domains active - 18.3GB RAM used, 3.6 load Competing panel running under Open Lite Speed - 125...

Not true. There are still good people out there. Softaculous hasn't increased their prices and their Webuzo control panel is an excellent alternative. I've already built a service based on Webuzo and plan on moving more servers to this. Cheaper license, more streamlined control panel, less...

I'm done with this BS. Every price increase is "justified" as "we are working hard" and then when we see the new changes, it's in the form of a new paid plugin, so, WHY am I paying a permanent price increase every year so they could develop more paid plugins?!?!. Also, since WHEN working hard...

Username: TITLE When moving a domain outside of a plan owned by the same customer the WP-Toolkit get stuck on the wrong plan PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Almalinux 9 PROBLEM DESCRIPTION When moving a domain outside of a plan into a new plan, both owned by the...

It's full of bugs and things that they DON'T FIX and are STILL BROKEN and that you have to take your personal time to fix it, otherwise your business would be screwed. Example, the nginx rewrites completely break if you have "Custom Error Documents" and your default webserver is NGINX. I've...

I get that they pretty much don't care about the current state of the world and frankly, it is starting to sound like they WANT the world to explode. I am starting to consider moving away from Plesk, this is unsustainable in the long run, we are contributing to an artificial inflation that...

You can check my post were I uploaded the fix. It was tested 100% and will just skip custom error documents altogether so even if it auto enable itself it won't break your sites...

No. It is not official. It is what our Engineer did to fix the issue on our servers. This should NOT break any update or the server itself or any migration. What the file does is just change the order in which the rules are loaded, giving priority to the "404" rules for the WP Toolkit...

The fix is here. Just add this file into: /usr/local/psa/admin/conf/templates/custom/domain/nginxDomainVirtualHost.php Then do: plesk repair web And Custom Error Pages will no longer present a problem to NGINX native servers as the option is going to be ignored.

If we could do it, I'm sure Plesk could a little more than just putting this as a Bug and not doing anything for well over a month now.

This is a note from our Engineer at our company on how we fixed this issue. The problem is that WordPress Toolkit is using error_page directives in the config file to handle the permalinks - if the site visitor requests a non-existent file and nginx generates a 404 error or similar, with...

Our Engineer at our company found a fix for this issue. I will past the information here for your devs. The problem is that WordPress Toolkit is using error_page directives in the config file to handle the permalinks - if the site visitor requests a non-existent file and nginx generates a 404...

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...