Try it for yourself and see. It is related to let’s encrypt
we've already tested and provided the solution, whats in nginx error log ?
-- Unit nginx.service has begun starting up.
Jun 18 07:24:55 wp04.refreshserver.nl nginx[301557]: nginx: [emerg] SSL_CTX_set_cipher_list("EECDH~~@@~~ECDSA~~@@~~AESGCM:EECDH~~@@~~aRSA~~@@~~AESGCM:EECDH~~@@~~ECDSA~~@@~~SHA384:EECDH~~@@~~ECDSA~~@@~~SHA256:EECDH~~@@~~aRSA~~@@~~SHA384:EECDH~~@@~~aRSA~~@@~~SHA256:EECDH~~@@~~aRSA!RC4:EECDH:!RC4:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS") failed (SSL: error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command error:140E6118:SSL routines:ssl_cipher_process_rulestr:invalid command)
Jun 18 07:24:55 wp04.refreshserver.nl nginx[301557]: nginx: configuration file /etc/nginx/nginx.conf test failed
Jun 18 07:24:55 wp04.refreshserver.nl systemd[1]: nginx.service: Control process exited, code=exited status=1
Jun 18 07:24:55 wp04.refreshserver.nl systemd[1]: nginx.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support:
https://access.redhat.com/support--
-- The unit nginx.service has entered the 'failed' state with result 'exit-code'.
Jun 18 07:24:55 wp04.refreshserver.nl systemd[1]: Failed to start The nginx HTTP and reverse proxy server.
-- Subject: Unit nginx.service has failed
-- Defined-By: systemd
-- Support:
https://access.redhat.com/support--
-- Unit nginx.service has failed.
--
-- The result is failed.