@DieterWerner That's clearer. Okay so you've not recompiled Nginx yourself (or via another supplier) using OpenSSL 1.1.1 which means the Nginx 1.14.1 bug present in Plesk 17.8.11 is very, very, unlikely to be the issue, but it was worth checking.
NO is the answer to your question about downgrading to 17.5.3. As mentioned ^^ 17.8.11 / Nginx 1.14.1 is very, very, unlikely to be the cause of your issue, so it would be pointless. The Nginx link we posted explains why, pretty clearly in your case.
As
@Monty correctly said in his earlier post, using the specific setup that you've posted, you are not, currently (and cannot anyway) run TLSv1.3. If we've read all your posts correctly, you initially added TLSv1.3 as an SSL Protocol within etc/httpd/conf.d/ssl.conf not realising or knowing this information, but, that action, then gave you the errors you've posted about. Plus, the errors have not been corrected
after you removed TLSv1.3 as an SSL Protocol within etc/httpd/conf.d/ssl.conf. That's how it reads so far (we think?)
Assuming that's ^^ correct, then some initial basic questions;
a) Do you run
# apachectl -t and receive a
# Syntax OK after changing things and before restarting Apache each time ? We ask because that would normally have allowed you to see / correct any errors like these, beforehand.
b) Using your corrected, latest version of etc/httpd/conf.d/ssl.conf what happens if you run a) now? If you're just referred back to
AH00526: Syntax error on line 220 of /etc/httpd/conf.d/ssl.conf: again, have you double-checked ALL the content of etc/httpd/conf.d/ssl.conf and ensured it's correct everywhere? Meaning; you've posted your SSLProtocols being within <IfModule mod_ssl.c> section of the conf file, but they could also be in the main .conf body for example. Unlikley, if the line number is as you've posted, but again, worth double-checking.
c) Have you tried creating a
fresh,
new (100% correct) etc/httpd/conf.d/ssl.conf, replacing the current one (having taken a back up copy etc) and then running a)? What happens then?
d) After b) or c) have you re-booted your server, just to iron that slim possibility out too?
From the info you've posted so far, it
appears to be nothing more than an initial misconfiguration via a typo in that conf file, so you should be able to correct it by backtracking / checking all the details / correcting it etc.
You've not mentioned that you made any TLSv1.3 related changes to Nginx (or indeed, that you're using Nginx as well as Apache) so at this point, we're assuming that you haven't and that you're not
Facebook
Twitter
