• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/

Search results

  1. Polsys

    Issue Unable to create the remote backup to s3: Transport error

    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 =...
  2. Polsys

    Issue Unable to create the remote backup to s3: Transport error

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

    Issue Unable to create the remote backup to s3: Transport error

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

    Issue Unable to create the remote backup to s3: Transport error

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

    Issue Unable to create the remote backup to s3: Transport error

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

    Issue centos2alma interrupted

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

    Issue centos2alma interrupted

    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).
  8. Polsys

    Issue centos2alma interrupted

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

    Issue Unable to delete a Host/Network in File Server extension

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

    Issue Unable to delete a Host/Network in File Server extension

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

    Issue Unable to delete a Host/Network in File Server extension

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

    Plesk 12.5.30: nginx gives 403 forbidden on images after upgrade from 11.x

    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 :)
  13. Polsys

    Plesk 12.5.30: nginx gives 403 forbidden on images after upgrade from 11.x

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

    Plesk 12.5.30: nginx gives 403 forbidden on images after upgrade from 11.x

    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?
  15. Polsys

    Plesk 12.5.30: nginx gives 403 forbidden on images after upgrade from 11.x

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

    Plesk 12.5.30: nginx gives 403 forbidden on images after upgrade from 11.x

    Hi @gennolo, I think we haven't any package from Atomic: # yum -v repolist S'està carregant el connector "fastestmirror" Config time: 0.013 Yum Version: 3.2.29 Loading mirror speeds from cached hostfile * base: centos.mirror.xtratelecom.es * extras: centos.mirror.xtratelecom.es * updates...
  17. Polsys

    Plesk 12.5.30: nginx gives 403 forbidden on images after upgrade from 11.x

    Hi @gennolo and @UFHH01, some news about this. Last evening I launched a new cloud server with a fresh Plesk 12.5.30 ‪and CentOS 6.8. All 100% from scratch with the default configurations, without WordPress. A programmer from my team has hand-written a tiny PHP script to upload files to the...
  18. Polsys

    Plesk 12.5.30: nginx gives 403 forbidden on images after upgrade from 11.x

    Sorry @UFHH01 & @gennolo, the answer is so obvious! I've added nginx to psacln group, nginx & apache services restarted and the problem persists.
  19. Polsys

    Plesk 12.5.30: nginx gives 403 forbidden on images after upgrade from 11.x

    A walk to a file with problems (httpdocs/wp-content/uploads/2016/08/test1.jpg) drwxr-x--- <domain-system-user> psaserv httpdocs drwxr-xr-x <domain-system-user> psacln wp-content drwxr-xr-x <domain-system-user> psacln uploads drwxr-xr-x <domain-system-user> psacln 2016 drwxr-xr-x...
  20. Polsys

    Plesk 12.5.30: nginx gives 403 forbidden on images after upgrade from 11.x

    Some more tests and notes about this: To discard problems with a migrated websites, I have installed a fresh, blank WordPress instance into a new Plesk vhost. The error persists. With images uploaded with the browser non-ajax method, the error also appears. Is not an exclusive problem with the...
Back
Top