• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Get WWW and HTTPS Redirects working together for HSTS Preload

LRLD

New Pleskian
Hi,

can Plesk please fix these two so they work properly together and you can add your domains to the hsts preload list.
It would be very easy to fix, simply remove the www redirect from the http section so it only gets added to the https section.

http://domain.com doesn't need redirecting to http://www.domain.com, it just needs to be redirected to https://domain.com and then redirected to https://www.domain.com.
At the moment, I have set preferred domain to none, and have put the www redirect in the Additional directives for HTTPS in Plesk and added my domain to the preload list.

I hope this can get fixed soon, it's obviously been a while!
Kind regards

LD
 
Hello, @LRLD. There's an existing UserVoice idea for improving this behavior. Please consider voting for it here to increase its popularity. We are glad to hear you already found a workaround to the issue, just for the sake of the rest of the users who might come across the undesirable redirect, it's possible to either change the preferred domain settings or manually add HSTS header to location / of the domain's Nginx vhost file. Use the server { section where it's assigned to :80. For example on /etc/nginx/plesk.conf.d/vhosts/example.com.conf:

CONFIG_TEXT:server {
listen 203.0.113.2:80;
...
...
...
location / {
return 301 https://$host$request_uri;
add_header strict-transport-security: max-age=15552000;
}

I hope that helps.
 
Back
Top