Skip to content
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

Closed
PontusTideman opened this issue Feb 24, 2022 · 6 comments
Closed

Comments

@PontusTideman
Copy link

PontusTideman commented Feb 24, 2022

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".

nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/sites-enabled/somedomain.TLD.conf:2
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/sites-enabled/somedomain.TLD.conf:42
nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/sites-enabled/somedomain.TLD.conf:56

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

@MattIPv4
Copy link
Contributor

MattIPv4 commented Feb 24, 2022

👋 The tool does not include the ssl directive in a final config -- part of the setup instructions briefly include setting the directive to off to ensure that SSL is completely disabled, even for older setups, while SSL certs are generated.

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?

@MattIPv4
Copy link
Contributor

MattIPv4 commented Apr 8, 2022

No response, closing. This intentional behaviour that is temporary during the setup steps and emits a warning, not a failure.

@MattIPv4 MattIPv4 closed this as completed Apr 8, 2022
@henno
Copy link

henno commented Jun 15, 2022

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.

@klevvit
Copy link

klevvit commented Nov 18, 2023

Hi! Now it became a problem for me: [emerg] 11883#11883: unknown directive "ssl"

nginx version: nginx/1.25.3
built with OpenSSL 3.1.3 19 Sep 2023 (running with OpenSSL 3.1.4 24 Oct 2023)
TLS SNI support enabled

@MattIPv4
Copy link
Contributor

👋 @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.

@klevvit
Copy link

klevvit commented Dec 16, 2023

👋 @klevvit Would you mind filing a new issue capturing the fact this is now resulting in an NGINX failure?

@MattIPv4 Done! #458

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants