• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. A

    Issue 502 bad gateway error after migrating to alma linux and updating plesk

    systemd [4540] System daemons [3] Failed to canonicalize path '/usr/local/psa/admin/.config/systemd/user/systemd-exit.service.d': Permission denied getting this error... @Peter Debik
  2. A

    Issue 502 bad gateway error after migrating to alma linux and updating plesk

    Nope, not listed there. I even disabled Fail2Ban and checked the server shuts down showing 504 error after some 12-20 mins after running Plesk repair or restarting the server I disabled unsused FPM too... can you please help!
  3. A

    Issue 502 bad gateway error after migrating to alma linux and updating plesk

    Yes it is listed as trusted IP address @Peter Debik Either I have to restart the server or check/ repair the server to get the websites up again.
  4. A

    Issue 502 bad gateway error after migrating to alma linux and updating plesk

    When I restart it works but within some minutes its goes down again ..saying bad gateway.. but I can access the Plesk CP @Peter Debik
  5. A

    Issue 502 bad gateway error after migrating to alma linux and updating plesk

    I had migrated from cent os to alma linux and then updated plesk ...everything is up to date now I am getting 502 bad gateway error I am getting this error while repairing The operation failed with the following error: {"id":1,"cmd":"plesk repair installation...
  6. A

    Issue Failed to update Plesk. To solve this problem, you can send the update log to Plesk support.

    How do I remove the Centos 8 repo? as i also have alma linux repo. [root@vmi599832 ~]# dnf repolist repo id repo name AppStream CentOS-8 - AppStream BaseOS CentOS-8 - Base PLESK_17_PHP71 PHP 7.1...
  7. A

    Issue Failed to update Plesk. To solve this problem, you can send the update log to Plesk support.

    ERROR: Components and product validation detected at least one important issue: EPEL repository should be enabled for PHP 8.0 Error: No matching repo to modify: epel. Error: Failed to download metadata for repo 'AppStream': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All...
  8. A

    Issue Failed to update Plesk. To solve this problem, you can send the update log to Plesk support.

    I am still getting this error..... after updating to almalinux 8.6 [root@vmi599832 ~]# dnf -y update CentOS-8 - AppStream 12 kB/s | 282 B 00:00 Errors during downloading metadata for repository 'AppStream': - Status code: 404 for...
  9. A

    Issue Failed to update Plesk. To solve this problem, you can send the update log to Plesk support.

    Execution failed. Command: autoinstaller Arguments: Array ( [0] => --select-product-id [1] => plesk [2] => --select-release-current [3] => --upgrade-installed-components [4] => --include-components-from-class [5] => aspect=panel ) Details: Downloading file products.inf3...
Back
Top