Recent content by ip00

@Sebahat.hadzhi The issue is that python-requests is a generic library, not a specific bot. Following this logic, Plesk should also block curl, wget, and Go-http-client, as they are also used by 'many bots and scanners'. By blocking the default library UA, you aren't stopping sophisticated...

The bot protection rule lists "python-requests" in its user agent blocklist. This is far too broad as python-requests is a generic Python HTTP library used by countless legitimate applications: open data portals (CKAN), monitoring tools, data integrations, government services, etc. In our case...

I've tried this and it works but there is a big issue, I'm not able to set "Path". I can only send backups to bucket's root directory, path must be "/". Anything else (eg. /subdirectory/) results in "Path does not exists." I've experienced similar issue with Scaleway Object Storage and was...

Explanation from your FAQ is boilerplate like. Sure you're constantly upgrading and fixing your product, but that's why we pay monthly/yearly fees. But you are also increasing the price of your legacy products (Plesk 10/11, Confixx, etc.) that you are not upgrading anymore. @HHawk already wrote...

@HHawk yes, I've read it. I wasn't sure where to post my reply, here or in that post, and caused a mixup for @IgorG when I deleted my post from there to put it here.

Here is Plesk's FAQ about this price increase: Plesk Price Adjustment 2021 - FAQ Online Customers We are also baffled by this latest price hike announcement by cPanel and Plesk. I don't want to go through the process of explaining to our clients why we must increase prices. We did it only a few...

@Xawier thank you Panel.ini change helped me and it works with Scaleway now. I've tested with two smaller backup tasks (subscription backups of 500 MB and 1.800 MB), now also a 10.100 MB backup task finished without errors (multivolume 4 part backup). I will try full server backup later tonight...

That's what I tried to do and was pretty sure it would solve this issue. But, it didn't. Maybe the "upgrader_process_complete" isn't the right hook in this case. This is the code I used: function do_rewrites() { flush_rewrite_rules(); } add_action( 'after_switch_theme', 'do_rewrites' )...

This is also happening on our Plesk servers and it gave us a lot of headaches. I thought it was related to one of the plugins we use, made a list of suspects but over time that list shrunk to zero because it was happening on sites that do not share the same plugins. Then I noticed it doesn't...

We have been using DigitalOcean Spaces (S3) as a remote location for server backups with Amazon S3 Backup extension for a few years. There was no problem setting it up or using it. Now, we have also started using Scaleway Object Storage (also S3 compatible) for backups storage and static files...

Today WP 4.4 was released. When I update a site it partially disappears from Wordpress Toolkit list. There is an item/line: "! /httpdocs" with a message "A Wordpress installation was previously detected at this path, but it is not operating properly now." Plesk for Linux 12.5.30 Update #14...

Yes, that's why it's weird.

I'm also having the same issue in Plesk Panel 11.5.30, and have no idea how to solve it.

Hopped that #15 will resolve this, but it didn't. Same mail every day...

I'm running 11.5.30 Update #14, last updated at Sept 7, 2013 03:36 AM