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

    wordpress toolkit and php 8

    Username: camaran TITLE wordpress toolkit and php 8 PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE php 8 debian PROBLEM DESCRIPTION with wordpress in php 8 env toolkit give error STEPS TO REPRODUCE set php 8 in wordpress installation, wordpress toolkit broken ACTUAL...
  2. N

    Input Support for PHP 8.0 in Plesk

    PHP Fatal error: Uncaught TypeError: implode(): Argument #2 ($array) must be of type ?array, string given in /opt/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wp-cli/php/WP_CLI/DocParser.php:75 Stack trace: #0...
  3. N

    Input Support for PHP 8.0 in Plesk

    i think broken also wordpress extension
  4. N

    Issue Wildcard Lets Encrypt

    umh the problem is domain example.org i assign *.example.org to the main domain i go to sub.example.org hosting setting and i see only the certificate issued for sub.example.org and not *.example.org certificate
  5. N

    Issue Wildcard Lets Encrypt

    Now let's encrypt extension work with wildcard certificate bug the problem is i cannot use the wildcard in subdomain
  6. N

    Issue Wildcard Lets Encrypt

    Hi, i select Issue a wildcard SSL/TLS certificate but the certificare have nomeDominio and not *.nomeDominio ad i can use only in the main domain and not in subdomain.
  7. N

    Question wildcard certificate

    i can see wildcard option but when i generate the certificate in domain name i have "domainName" and not "*.domainName" and i cannot use in *.domainName, i use also CAA record: xxx.pro. CAA (iodef) mailto:[email protected] xxx.pro. CAA (issue) letsencrypt.org
  8. N

    Let's Encrypt extension

    i can see wildcard option but when i generate the certificate in domain name i have "domainName" and not "*.domainName" and i cannot use in *.domainName, i use also CAA record: xxx.pro. CAA (iodef) mailto:[email protected] xxx.pro. CAA (issue) letsencrypt.org
  9. N

    Question Mobile Subdomain m.domain.tld (CNAME) in Plesk

    You not use a mobile dedicated URL but use a responsive website, SEO say thankyou Inviato dal mio iPhone utilizzando Tapatalk
  10. N

    Question Nginx (TLS 1.3 + Pagespeed) - Updating cipher list

    but tls 1.3 work with plesk?
  11. N

    Plesk Onyx 17.8 Preview

    I have also an other problem: MySQL access denied for root@localhost but I see permission of user root and bind-address in my.cnf and I not see problem. I see because I have an email of error of logrotate task. /etc/cron.daily/logrotate: mysqladmin: connect to server at 'localhost' failed...
  12. N

    Plesk Onyx 17.8 Preview

    Hi, yes there is ssl_cert = </.... ssl_key = </... but not work Jan 15 07:26:02 plesk178 dovecot: imap-login: Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY Jan 15 07:26:02 plesk178 dovecot: master: Error...
  13. N

    Plesk Onyx 17.8 Preview

    Under debian 9 if I set certificate for email I cannot login to my inbox and I see error in log file 'ssl key error'. I use postfix and dovecot dovecot: imap-login: Fatal: Couldn't parse private ssl_key
  14. N

    Resolved plesk panel http/2

    It's possibile to enable http/2 also for panel? i set [webserver] nginxHttp2 = true in panel.ini but not work still in http1.1
  15. N

    Resolved TLS 1.3 support

    and i only set ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; or here is a specific cipers also?
  16. N

    Resolved TLS 1.3 support

    Hi, TLS 1.3 is supported in plesk 17.5.3 and debian 8?
  17. N

    Resolved plesk http2 ciphers

    ok if now use plesk sbin sslmng --services=nginx --custom...
  18. N

    Resolved plesk http2 ciphers

    good now work thank you
  19. N

    Resolved plesk http2 ciphers

    after i edited the file i must nginx -s reload or i must donw other action?
  20. N

    Resolved plesk http2 ciphers

    yes yes for the file syntax not problem, the problem is for ciphers i not now whats are the best
Back
Top