• 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

    Resolved sslit error getScheme() must be compatible with...

    I chose to migrate from the affected server with Centos 7 to one with Alma Linux 9 as I had few accounts on it and so I already use a more recent OS. If anyone can contact Plesk support so they can access it and see what it could be, that would be great, as I have other servers with Centos 7...
  2. A

    Resolved sslit error getScheme() must be compatible with...

    It seems some issue in /usr/local/psa/admin/plib/modules/sslit/vendor/guzzlehttp/psr7/src/Uri.php but even correnting some things like public function getScheme(): string adding the "string" the page open after correct several things like that but not create new certificates.
  3. A

    Resolved sslit error getScheme() must be compatible with...

    Or even by the 8443/modules/sslit/index.php/index/certificate/id/50
  4. A

    Resolved sslit error getScheme() must be compatible with...

    When try to access 8443/modules/sslit/index.php/main-page/index that resuts in: ERROR: Declaration of PleskSslIt\GuzzleHttp\Psr7\Uri::getScheme() must be compatible with Psr\Http\Message\UriInterface::getScheme(): string (Uri.php:346) I did not find any information in google to solve that. I...
  5. A

    Resolved Could not issue a Let's Encrypt SSL/TLS certificate for

    Solved. It was a Lets Encrypt ip block. I contacted then and they removed the ip block
  6. A

    Resolved Could not issue a Let's Encrypt SSL/TLS certificate for

    Hello, the acme-v02.api.letsencrypt.org seems operational but the error persist. And I am not finding much information of how solve that.
  7. A

    Resolved Could not issue a Let's Encrypt SSL/TLS certificate for

    When I try to add a Let's Encrypt SSL/TLS certificate the plesk returns that: I did read a lot of others posts, some very olds, but I am not able to solve. I am runing: Plesk Obsidian Web Pro Edition Version 18.0.37 Update #2 VPS with Centos 7 from ovh templates.
Back
Top