• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. A

    HTTP/2 support released

    I was propably not specific enough here: the above Cipher configuration are all TLS1.2 ciphers, still plesk leaves ssl_protocols TLSv1 TLSv1.1 TLSv1.2; as default when switching to HTTP2, suggesting v1.0 and 1.1 would still work - which they don't because there aren't any ciphers they support...
  2. A

    ERROR: Firewall configuration

    I just had the same issue with Plesk 12.5.30 #28 and my permissions on /usr/local/psa/admin/sbin/mod_wrapper were wrong: ---x--x--- 1 root psaadm 23K 10. Apr 13:08 /usr/local/psa/admin/sbin/mod_wrapper chmod 4510 /usr/local/psa/admin/sbin/mod_wrapper and now they are -r-s--x--- 1 root psaadm...
  3. A

    HTTP/2 support released

    I would like to note that enabling HTTP/2 sets the following ciphers in /etc/nginx/conf.d/ssl.conf : ssl_ciphers EECDH+AESGCM+AES128:EECDH+AESGCM+AES256:EECDH+CHACHA20:EDH+AESGCM+AES128:EDH+AESGCM+AES256:EDH+CHACHA20; Testing my server afterwards with SSLLabs showed that this configuration...
Back
Top