(02-11-2015, 02:57 AM)Jayster Wrote: You do not comment the 443 that was created in Sentora VHOST coz that will be re-generated if there will be a new entry and after the daemon runs.
I am referring to SSL.CONF Listen Port created by the default open SSL not the one with Sentora VHOST.
(See SSL default configuration in CentOS path)
/etc/httpd/conf.d/ssl.conf
Code:LoadModule ssl_module modules/mod_ssl.so
#
# When we also provide SSL we have to listen to the
# the HTTPS port in addition.
#
Listen 443
##
## SSL Global Context
If you comment that default Listen 443, there will be no issue on adding another port 443 entry on Sentora VHOST that will be created inside Sentora settings.
Tnx a lot, i did not notice reply. I think it should work for me on CentOS
I just upgrded to 1.0.x had same issue, but now i see that file you pointed out I think I should be good.
I do noticed another potential bug though.
SSL configured, website exceeds bandwidth limitation. VM hostrecord gets updated pointing site to error page BUT something wrong with logic and HTTPd start complaining that there suppoed to be SSL configured and whole server can not restart after demon update
I will try to do more testing in the future
