Recent content by Polsys

The bucket name is hidden for privacy. Note that manual backups are working correctly with the same configuration. nslookup xxxxxx.s3.us-west-2.amazonaws.com Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: xxxxxx.s3.us-west-2.amazonaws.com canonical name =...

I tried, but nothing has been fixed (identical errors).

Thanks, I will try it, and I will post the result.

Hi, @Sebahat.hadzhi. I noticed these errors through email alerts from the Plesk panel, so the server was running. Yes, I have several cron tasks running periodically on this server, some from Plesk, others from some extensions, and a few more from user scripts (none simultaneously as the backup...

I have several servers with the same specs and the Backup to Cloud Pro+Amazon S3 Backup extension backing up to S3 seamlessly. However, one single server has problems with scheduled backups. For a few weeks, this is the error that has been found every day: Unable to create the remote backup...

Plesk staff is still looking into it. I will post any updates when available.

Thank you, Peter; I just opened a ticket with my reseller. I will post the result here if the result is successful (I hope so).

I'm attempting to convert a CentOS 7 server with Plesk to AlmaLinux 8 with the script GitHub - plesk/centos2alma: CentOS 7 to AlmaLinux 8 conversion tool. The server runs Plesk Obsidian v18.0.53_build1800230619.12, CentOS Linux 7.9.2009 (Core), and it's okay with the indicated requirements. I...

Thanks, @IgorG. I wonder if would be possible to get a hotfix file to solve the Network section temporarily.

Thanks @IgorG for your answer. This file doesn't fix the problem with deleting Networks (inside Access label) but for removing Users. I suppose it's a similar issue. Could you share a version for Networks? Besides, I have made another test trying to delete a Share and this problem also appears...

When I attempt to delete an existing Network or host address from the section "Access" in the File Server Extension, a 500 error appears and the Network remains activated. The Repair Kit doesn't help in any way.

Hi @Matric, thanks for your post: with SELinux disabled this problem disappears. Maybe @UFHH01 or @Peter Debik can help us a little more after this information :)

Ouch! In my case, the problem disappears with "PHP 5.3.3 by OS vendor"

Finally, We think the problem is originated by PHP7 + PHP-FPM. With the combo PHP 5.3.3 + PHP-FPM all is running right. @gennolo, are you in PHP7 too?

Hi @Peter Debik, thanks for commenting. Take a look at #43 where I explain a test in a server without WordPress or .htaccess