Facebook
Twitter
-
Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products ! WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
Join the pilot program today!
Resolved Plesk Panel 17.5 | 400 Bad Request The plain HTTP request was sent to HTTPS port
- Thread starter WebHostingAce
- Start date
Laughing Steam
New Pleskian
Mine I think is a bug as I don't have Nginx even on! I'm new still so I can submit it
U
UFHH01
Guest
Hi Laughing Steam,
The Plesk Control Panel IS a combination of NGINX and LiteSpeed ( compairable with apache ) and is named "sw-cp-server". It has got absolutely nothing to do with your very own nginx version and apache version installed on your server to serve your domain(s).
We're all users, not Plesk team members. Plesk team members, Plesk support and Plesk developers are separate. This forum is a user forum. You and us can file a bug report equally well. We've been reflecting and discussing whether it is a bug, because before filing a report with Plesk, it is simply nice behavior to only cause work if it is really a bug.
Oh sorry, I saw "Plesk Guru" tag then I think you are developer team. I want to thank you because you are discussing trying to find solution.
WSNHosting
Basic Pleskian
old version can redirect to https://server:8443
but new version not redirect
and i found slow process
but new version not redirect
and i found slow process
I had same thing after upgrading to 17.5. However similar issue was in Plesk 11.
So - I have added to:
/etc/sw-cp-server/conf.d/plesk.conf
below line:
error_page 497 https://$host:$server_port$request_uri;
restarted sw-cp-server and issue has been fixed.
I have followed this article.
So - I have added to:
/etc/sw-cp-server/conf.d/plesk.conf
below line:
error_page 497 https://$host:$server_port$request_uri;
restarted sw-cp-server and issue has been fixed.
I have followed this article.
WSNHosting
Basic Pleskian
server_names_hash_bucket_size 64;
server {
listen 8443 ssl;
listen 8880;
listen 127.0.0.1:8880 default_server;
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;
error_page 497 https://$host:$server_port$request_uri;
}
work !!
server {
listen 8443 ssl;
listen 8880;
listen 127.0.0.1:8880 default_server;
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;
error_page 497 https://$host:$server_port$request_uri;
}
work !!
Kingsley
Silver Pleskian
Where are we making this change?
Kingsley
Silver Pleskian
Kingsley
Silver Pleskian
here i wrote a guide, you might find it useful 400 Bad Request: The plain HTTP request was sent to HTTPS port Plesk
You have already asked the same question in the other thread. The answer is the same, too: It does not matter. Just leave things in place as they are on your system. If the update thinks it must update the file, it will overwrite it, but then it will still work. If the update does not overwrite it, it will continue to work. Either way, it will work.
