Problem with AutoSSL messing with my nginx vhosts settings

Hello,

New user here, hope I'm posting in the right forum and all that.

I have a problem with SSL in CWP, using nginx as my main Web server. Each time a certificate is renewed, be it manually from CWP's appropriate page or automatically using AutoSSL, my per-vhosts nginx conf files are modified.

Indeed, in /etc/nginx/conf.d/vhosts, I have several vhosts conf files that contain, among other things, the following lines:

Code: [Select]

server {
listen *:443 ssl http2;
the "listen *" is necessary because my server is NATed by my cloud provider. Listening only via the public IP does not work.

It also contains some specific config lines necessary for Drupal's "clean URLs" to work.

 Yet, each time a certificate is renewed, the corresponding vhost config files are regenerated to their default settings, with these lines reverted to :

Code: [Select]

server {
listen 51.xx.xx.xx:443 ssl http2;

(where 51.xx.xx.xx is the public IP of my server). Thus, nginx stops listening properly for the corresponding domain/subdomain and everything falls apart. Plus I have to reenter the Drupal-compatibility workaround lines in each vhost.

Is there a way to fix that?

Thanks in advance!

Open a ticket to developers with detailed information about the issue.

using * is a bad config, you need to set up NAT networking in cwp and that will give you a properly configured server.

http://wiki.centos-webpanel.com/default-page-displayed-for-all-domains

using * is a bad config, you need to set up NAT networking in cwp and that will give you a properly configured server.

http://wiki.centos-webpanel.com/default-page-displayed-for-all-domains

Even if I solved this part, it would still remove my drupal-specific lines of config each time, making most of my websites unaccessible due to non-functioning clean URLs.

you need to use templates, you can't do manual edit.... all this is on cwp wiki:
http://wiki.centos-webpanel.com/webservers-vhost-templates

Oh wow! So I need to make a handful dozens of templates, each used once, and also there's a conf editor but it should never be used because any change made in there will be overwritten at the first occasion anyway.

Is it really just me, or is it less than ideal, as far as straightforwardness is concerned?

Oh wow! So I need to make a handful dozens of templates, each used once, and also there's a conf editor but it should never be used because any change made in there will be overwritten at the first occasion anyway.

Is it really just me, or is it less than ideal, as far as straightforwardness is concerned?

that is why we've template option to retain any changes when vhost rebuilded