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

Resolved Plesk Panel 17.5 | 400 Bad Request The plain HTTP request was sent to HTTPS port

WebHostingAce

WebHostingAce

Silver Pleskian
Hi,

Since upgrade to Plesk 17.5 from 17.0,

I get this error,

400 Bad Request
The plain HTTP request was sent to HTTPS port
nginx

Servers running CentOS 7 and 6.9

Plesk login no loger redirect to HTTPS.

Possibly a Bug.
 
Hi AusWeb,

pls. use the HTTPS version, instead of HTTP, when you try to login into your Plesk Control Panel:

Example ( recommended URLs ):
Code: 
https://servername.hosting-provider-FQDN.com:8443
https://servername.YOUR-DOMAIN.com:8443


If you desire to use the HTTP port of your Plesk Control Panel, then you would choose the URLs:
Code: 
http://servername.hosting-provider-FQDN.com:8880
http://servername.YOUR-DOMAIN.com:8880
 
Hi AusWeb,

pls. check the "sw-cp-server" configuration files and the corresponding logs at "/var/log/sw-cp-server" for further investigations.
 
UFHH01 said:
Hi AusWeb,

pls. use the HTTPS version, instead of HTTP, when you try to login into your Plesk Control Panel:

Example ( recommended URLs ):
Code: 
https://servername.hosting-provider-FQDN.com:8443
https://servername.YOUR-DOMAIN.com:8443


If you desire to use the HTTP port of your Plesk Control Panel, then you would choose the URLs:
Code: 
http://servername.hosting-provider-FQDN.com:8880
http://servername.YOUR-DOMAIN.com:8880
Click to expand...

Why is HTTP not redirecting to HTTPS?
 
Hi Kingsley,
Hi AusWeb,

before you speculate further, you really should consider to post the corresponding configuration files and log - files, so that people willing to help you are actually able to investigate the issue/error/problem. ;)
 
Hi, i am having the same problem on 3 ! different server after upgrading to the latest version. no http to https redirection. Plesk was upgraded from 12.5 and i never had this before nor changed any config files. Error, access, sw-engine logs are empty. Redirecting was working properly before. vServers are running on ubuntu 14.04. I tried to fix this bug with the tipps for 11.5 plesk version but that did not work. would be great to fix that! thanks and best, c--
 
Same issue here. Not sure what's going on, but here's the error log in /var/log/sw-cp-server/

2017/04/25 11:20:07 [error] 10193#0: *989 empty URI in redirect to named location "@err" while reading client request line, client: REMOVED, server: , request: "

and from the sw-engine log:

[25-Apr-2017 18:03:28] NOTICE: Terminating ...
[25-Apr-2017 18:03:28] NOTICE: exiting, bye-bye!
[25-Apr-2017 18:03:28] NOTICE: fpm is running, pid 14301
[25-Apr-2017 18:03:28] NOTICE: ready to handle connections
[25-Apr-2017 18:03:28] NOTICE: systemd monitor interval set to 10000ms
[25-Apr-2017 18:04:26] NOTICE: Terminating ...
[25-Apr-2017 18:04:26] NOTICE: exiting, bye-bye!
[25-Apr-2017 18:04:26] NOTICE: fpm is running, pid 23740
[25-Apr-2017 18:04:26] NOTICE: ready to handle connections
[25-Apr-2017 18:04:26] NOTICE: systemd monitor interval set to 10000ms
[25-Apr-2017 18:18:38] NOTICE: Terminating ...
[25-Apr-2017 18:18:38] NOTICE: exiting, bye-bye!
[25-Apr-2017 16:18:38] NOTICE: fpm is running, pid 503
[25-Apr-2017 16:18:38] NOTICE: ready to handle connections
[25-Apr-2017 16:18:38] NOTICE: systemd monitor interval set to 10000ms
[25-Apr-2017 16:26:26] NOTICE: Terminating ...
[25-Apr-2017 16:26:26] NOTICE: exiting, bye-bye!
[25-Apr-2017 16:26:26] NOTICE: fpm is running, pid 7198
[25-Apr-2017 16:26:26] NOTICE: ready to handle connections
[25-Apr-2017 16:26:26] NOTICE: systemd monitor interval set to 10000ms
[25-Apr-2017 16:59:15] NOTICE: Terminating ...
[25-Apr-2017 16:59:15] NOTICE: exiting, bye-bye!
[25-Apr-2017 16:59:15] NOTICE: fpm is running, pid 22668
[25-Apr-2017 16:59:15] NOTICE: ready to handle connections
[25-Apr-2017 16:59:15] NOTICE: systemd monitor interval set to 10000ms
 
I think this issue is on every server running Plesk17.5. Im not sure if it is CentOS related since all my servers are running different versions of CentOS

Hopefully Plesk Team will fix this issue as soon as possible.:)
 
Personally I do not think it is a bug. It is a behavior, but not a bug. The response that Nginx delivers is correct. A request without SSL data is coming in on the SSL port. Why should Nginx forward this to an SSL encrypted connection?
 
Last edited by a moderator:
Good point. It seems a bit like a philosophy issue. I understand that
a) The error_page directive does not work - and that is a bug, o.k.
b) It is a function that was there before, and that should not be taken away from users - 2 points for a bug, zero for correct behavior.
but
c) It can make sense to not auto-redirecting from non-SSL to SSL, maybe to make users aware that their initial request was unsecure? Give 1 point against the bug.
= result is +2 for a bug, +1 for not-a-bug.
o.k., agree that it should be considered as a bug.
 
You must log in or register to reply here.

Similar threads

A
Question Plesk Admin - Bad Bot protection
Replies
4
Views
429
Alban Staehli
A
afuego
Question http://website.com:443 - 400 Bad Request
Replies
4
Views
2K
afuego
afuego
S
Issue Docker // The plain HTTP request was sent to HTTPS port
Replies
2
Views
6K
sabietzki
S
D
Question Service Unavailable port 8443 Plesk Not Working
Replies
1
Views
7K
Kaspar@Plesk
Kaspar@Plesk
T
Resolved Error E: Conflicting values set for option Signed-By regarding source http://autoinstall.plesk.com/PMM_1.0.0/
Replies
8
Views
2K
unsuwe0
U
Back
Top