• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

HTTP/2 & Let’s Encrypt for WordPress

S

Sergey Lystsev

Guest
dev-blog-migration.png

Our web blog is now meeting the latest security standards and making it HTTP2-ready is easier than you think. Here’s how we switched our web blog (https://devblog.plesk.com) running on Plesk + NGINX to HTTPS and made it HTTP/2-ready with a free, SSL certificate from Let’s Encrypt. Before we get into the details a few things […]

Continue reading...
 
You must log in or register to reply here.

Similar threads

learning_curve
Resolved SSL It! / Let's Encrypt installs incomplete Generation Y RSA certificate chain (YR1/YR2 → Root YR) without Root YR cross-sign to ISRG Root X1
Replies
6
Views
6K
learning_curve
learning_curve
kristobal1969
Resolved Error messages with let's Encrypt when 1 serveur for main domain and another serveur for subdomain or mails
Replies
12
Views
7K
NataliaA
N
AmaZili Communication
Error in let's encrypt certificate generation
Replies
3
Views
6K
Sebahat.hadzhi
Sebahat.hadzhi
K
Resolved Plesk Obsidian – Let’s Encrypt certificate does not include domain aliases in SAN
Replies
7
Views
6K
kicoes
K
G
Issue Issue with duplicate SSL Certificate
Replies
9
Views
8K
Gerardo Fernandez
G
Back
Top