400 Bad Request on panel login

[AlexeiV]

I have upgraded from 11.0.9 update 55 to 11.5.30 this morning but now when I go to Mydomain.com:8443 i get this message:

400 Bad Request

The plain HTTP request was sent to HTTPS port
nginx


It used to automatically redirect but it now does not appear to.

does anyone know how to fix this?

 

[InderS]

What error are you getting in the plesk error logs file ?

 

[AlexeiV]

What error are you getting in the plesk error logs file ?

I have checked the panel.log file and there is no errors listed in there

 

[PedroV.]

I try to update this morning 11.0.9 update 55 to 11.5.30 and I get the same message... Everything stops working, mysql failed to start... I have to reinstall Parallels Plesk Panel 11.0.9 and restore the backup.

 

[Nikolay.]

I try to update this morning 11.0.9 update 55 to 11.5.30 and I get the same message... Everything stops working, mysql failed to start... I have to reinstall Parallels Plesk Panel 11.0.9 and restore the backup.

http://forum.parallels.com/showthread.php?288439-patch-55-problems ?

 

[LinqLOL]

Any update about the "The plain HTTP request was sent to HTTPS port" message?

The 11.0.9 behaviour is to redirect www.domain.org:8443 to https://fqn.servername.com:8443 and thus make it possible to use a central SSL certificate for all customers.

 

[MisterU]

This feature is unavailable in PP11.5 because PP was switched from lighthttpd to nginx webserver.

 

[LinqLOL]

Could it be added again then? This should be possible also with nginx . Most of your customers use an SSL certificate to protect the control panel and it's uselless now.

 

[AlfaAlfa]

I have upgraded from 11.0.9 update 55 to 11.5.30 this morning but now when I go to Mydomain.com:8443 i get this message:

400 Bad Request

The plain HTTP request was sent to HTTPS port
nginx


It used to automatically redirect but it now does not appear to.

does anyone know how to fix this?

I have fallen into the same trap today following the panel update. Everything seems to run fine, but access to the panel results in "400 Bad Request; The plain HTTP request was sent to HTTPS port; nginx".

Help!!!!

 

[DLopez]

I've been having the same issue. The solution for this issue is to add "error_page 497 https://$host:$server_port$request_uri;" to the end of the file "/etc/sw-cp-server/conf.d/plesk.conf".

It'd great if this can be added to the next Plesk update.

 

[BernhardE]

Okay, it works, thanks a lot DLopez!

 

[DLopez]

Glad I could help.

Let's hope that it's included in the next Plesk update.

 

[MisterU]

I hope it will be fixed soon, bug#140973

 

[DanTron]

I've been having the same issue. The solution for this issue is to add "error_page 497 https://$host:$server_port$request_uri;" to the end of the file "/etc/sw-cp-server/conf.d/plesk.conf".

It'd great if this can be added to the next Plesk update.

At the end of the file? below the " } " ?

or inside like this?

server {
listen 8443 ssl;
listen 8880;
include conf.d/*ipv6_ports.inc;


ssl_certificate /usr/local/psa/admin/conf/httpsd.pem;
ssl_certificate_key /usr/local/psa/admin/conf/httpsd.pem;

include conf.d/*plesk.inc;
include conf.d/*wpb.inc;
include conf.d/*cbm.inc;
include conf.d/*sso.inc;
error_page 497 https://$host:$server_port$request_uri;
}
​

 

[DLopez]

Inside, like you put it.

 

[burnley]

A better way to do it, with significantly fewer risks to get your custom changes overwritten by Parallels during their (in)famous upgrades/patches is to use a custom file for this, say conf.d/zzz_mycustomconfig-plesk.inc with:

# Force http to https for the panel
error_page 497 https://$host:$server_port$request_uri;

# Optional. Force sitebuilder 8880/http to 8443/https
if ($server_port = 8880) {
rewrite ^ https://$host:8443$request_uri permanent;
}

Of course, all of this subject to future sudden, unexpected, unannounced and unwanted changes from Parallels :-/

 

[hintzsche]

A better way to do it, with significantly fewer risks to get your custom changes overwritten by Parallels during their (in)famous upgrades/patches is to use a custom file for this, say conf.d/zzz_mycustomconfig-plesk.inc with:

# Force http to https for the panel
error_page 497 https://$host:$server_port$request_uri;

# Optional. Force sitebuilder 8880/http to 8443/https
if ($server_port = 8880) {
rewrite ^ https://$host:8443$request_uri permanent;
}

Of course, all of this subject to future sudden, unexpected, unannounced and unwanted changes from Parallels :-/

Also ich habe die plesk.conf soweit geändert aber wenn ich dann serverip:8443 aufrufe kommt der Fehler weiterhin. Weis jemand was ich falsch mache ?

 

[Teslaman]

The quickest (and correct) fix: # echo ‘error_page 497 https://[B]panel.provider.com[/B]:$server_port$request_uri;’ > /etc/sw-cp-server/conf.d/zzz-myhost.conf

Replace panel.provider.com with your panel login URL

This way your changes will not get overwritten or broke your future panel upgrades.

Got the fix from here: http://cloudishvps.com/plesk/plain-http-request-sent-https-port-nginx/