-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[warn] the "ssl" directive is deprecated, use the "listen ... ssl" #333
Comments
👋 The tool does not include the The deprecation notice emitted by NGINX while the directive is present is only a warning, and should not cause any actual issues with NGINX during the setup stage that has this directive present? |
No response, closing. This intentional behaviour that is temporary during the setup steps and emits a warning, not a failure. |
I landed on this page looking for a fix to this "problem". I'm sure there are people who have come here before me, just as me, and will come after me. There should be an appropriate line somewhere, so that people would not worry and would not come here to seek solution to this "problem". Saves time for lots of people. |
Hi! Now it became a problem for me:
|
👋 @klevvit Would you mind filing a new issue capturing the fact this is now resulting in an NGINX failure? I imagine more recent versions have now completely dropped support, so we'll probably have to drop the backwards compatibility and remove this directive. |
Details
Description
Putting up a new VPS with nginx 1.18 and the confs fails due to [warn] the "ssl" directive is deprecated, use the "listen ... ssl".
Steps to reproduce
Create a new config, and when you paste the first line to fix the SSL, that oneliner will mess it up because it adds outdated stuffs to the configs.
https://futurestud.io/tutorials/nginx-how-to-fix-ssl-directive-is-deprecated-use-listen-ssl
Expected behavior
The form needs to be fixed to solve this, until then you need to manually go in and fix it by your self!
Screenshots
The text was updated successfully, but these errors were encountered: