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

    Forwarded to devs Laravel Toolkit generates Laravel Exception whenever used

    Username: TITLE Laravel Toolkit generates Laravel Exception whenever used PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Laravel Toolkit, Version 1.4.2-221, AlmaLinux 8.7 (Stone Smilodon) PROBLEM DESCRIPTION Whenever an action within the Laravel Toolkit is triggered e.g...
  2. M

    Issue Amazon S3 Backup - Backup Failed - Harness not finished running Error

    Recieved the following error from one a couple of our servers which are using Amazon S3 Backup Extension Harness not finished running at /usr/local/psa/PMM/agents/shared/Storage/ArchiveStorage.pm line 196. This has occured on 2 seperate servers. On one of the servers all subsequent backups...
  3. M

    Question How to set Nginx try_files directive on a domain?

    We have an issue with a Joomla website that is being hosted on CentOS Linux 7.3.1611 with Plesk Onyx Version 17.5.3 - the site is displaying issues when using nginx as a proxy - when we try tro access the domain https://example.com/administrator we are receiving a nginx 502 Bad Gateway error...
  4. M

    Resolved Unable to access login page - due to failed update?

    We are unable to access the Plesk login page for our server (https://77.68.11.162:8443/) running Plesk Onyx on CentOS 7 eventually receiving a 504 Gateway timeout - this was working correctly up to yesterday. All the Plesk Services are running #systemctl status sw-engine #systemctl status...
Back
Top