System: Ubuntu 18.04 Web Server: nginx/1.15.8 ISPConfig 3.1.13 Because of this warning: Code: nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/sites-enabled/000-ispconfig.vhost:4 I've changed the following directive ssl on; into listen 443 ssl; After restarting the nginx server the ISPConfig's Control panel was not accessible anymore through https and the browser was giving the SSL_ERROR_RX_RECORD_TOO_LONG error. I mention that I have a self signed certificate at the moment of ISPConfig installation. After switching back to ssl on; the Control Panel is accessible again through https. No other modification was necessary. Any advice? Thanks!
The original config was correct as you noticed by your failure when altering it, so leave it as it is. When you access a non-ssl web server with https, then you will get the error SSL_ERROR_RX_RECORD_TOO_LONG
Thank you for reply. All I wanted to do was to get rid of the nginx's warning message and I followed its suggestion. For a better understanding the ISPConfig is not prepared yet to work with listen 443 ssl; directive? On my server all vhosts are working fine with listen 443 ssl. I want to understand why ISPConfig's Control Panel is not accessible through https with the new directive per nginx's suggestion. It doesn't make sense to me. Thanks!
When you setup the listen directive correctly, then it will work for sure as that's not ispconfig specific.
What is the correct setup for the listen directive in order to avoid this warning message Code: nginx: [warn] the "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /etc/nginx/sites-enabled/000-ispconfig.vhost:4
Code: server { listen 8080 ssl; listen [::]:8080 ssl ipv6only=on; #ssl on; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; works flawlessly.
