SSL Ports 443 Kills Apache?

[Jayster]

Forget about commenting Listen 443 in default Apache2 folder files
"/etc/apache2/ports.conf_disabled_by_sentora"

I installed Sentora on Ubuntu 14.04 all default settings and the SSL runs normal using the Module Admin>>Apache Config>>Select VHOST.

Using "server.mydomain.tld" is redirected to SSL port 443 automatically with no problem.

[Cantalupo]

Yes, truth
Apache fails when:

Code:

root@host:~# sudo service apache2 restart
* Restarting web server apache2                                                (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
                                                                         [fail]
* The apache2 instance did not start within 20 seconds. Please read the log files to discover problems
root@host:~#

The problem is when you add "Listen 443" in the httpd-vhosts.conf.

Code:

################################################################
# Apache VHOST configuration file
# Automatically generated by Sentora 1.0.0
# Generated on: 23:50 10th Feb 2015 BRST
#==== YOU MUST NOT EDIT THIS FILE : IT WILL BE OVERWRITTEN ====
# Use Sentora Menu -> Admin -> Module Admin -> Apache config
################################################################

Listen 80
Listen 443

Solution?

[Jayster]

Ok it's like this Cantalupo,

Forget about what I've mentioned by adding extra Listen 443, coz this will be generated what ever you do in Ubuntu, Its different from CentOS settings anyway.
Just try using those generated 443 by default and add your ssl certs by using Module Admin>>Apache Config>>Select VHOST.

I' just tried the default SSL setup by Sentora and it works just fine, I 've installed 3 VM Ubuntu servers and all of them works fine with SSL.

[Cantalupo]

But when you add or remove domains or subdomains, the problem will come back.
For the file httpd-vhosts.conf will be updated.

Porting "Listen 443" will be added and apache will crash again ...

[alexus]

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