• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

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

afuego
Question http://website.com:443 - 400 Bad Request
Replies
4
Views
1K
afuego
afuego
S
Issue Docker // The plain HTTP request was sent to HTTPS port
Replies
2
Views
4K
sabietzki
S
kaw.one
Question (VPS) Cloudflare, Gmail and Other Plesk Panel 8443 (2 minutes - slow read)
Replies
1
Views
586
kaw.one
kaw.one
P
Resolved "502 Bad Gateway" with nginx reverse proxy for openhab cloud
Replies
10
Views
3K
Maarten.
M
S
Issue Plesk Control Panel search and specific pages/actions are extremely slow, while website works fine.
Replies
3
Views
775
SirAdams
SirAdams
Back
Top