SSL Issue, again (but I've read the other threads)

I'm seeing similar behaviour... Upgrading an old 1.1.2 box tonight. I have a wildcard SSL from COMODO (not self-signed) with a bundle file that has been working fine on the 1.1.2 release. Its used:

• On the Panel on this box
• For Services on this box
• For a secured subdomain on a website
• On a separate i-MSCP server panel
• on the separate i-MSCP server services

I could upgrade this machine to 1.1.5 without a problem, then every upgrade I tried afterwards buggered my Panel SSL and services (a few of the releases failed to restart SSL entirely, and one died with a DB upgrade error...). Re-adding the SSL to panel has left Apache unable to start

I have disabled the ssl on the panel for now, and am on 1.1.10 for now but no SSL (and self-signed services) leaves me less than happy. I cant seem to upgrade to 1.1.12 because every time I've tried it, no matter what I do Apache is not happy after (wont start). thankfully, this box is a VM and I just unwind the snapshot and try something different...

root@apollo:/home/nisadmin/imscp-1.1.10# apache2ctl -V
Server version: Apache/2.2.22 (Debian)
Server built: Jun 16 2014 03:51:45
Server's Module Magic Number: 20051115:30
Server loaded: APR 1.4.6, APR-Util 1.4.1
Compiled using: APR 1.4.6, APR-Util 1.4.1
Architecture: 64-bit
Server MPM: Worker
threaded: yes (fixed thread count)
forked: yes (variable process count)
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/worker"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_SYSVSEM_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=128
-D HTTPD_ROOT="/etc/apache2"
-D SUEXEC_BIN="/usr/lib/apache2/suexec"
-D DEFAULT_PIDLOG="/var/run/apache2.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="mime.types"
-D SERVER_CONFIG_FILE="apache2.conf"

root@apollo:/home/nisadmin/imscp-1.1.10# apache2ctl -M
Loaded Modules:
core_module (static)
log_config_module (static)
logio_module (static)
version_module (static)
mpm_worker_module (static)
http_module (static)
so_module (static)
actions_module (shared)
alias_module (shared)
auth_basic_module (shared)
authn_file_module (shared)
authz_default_module (shared)
authz_groupfile_module (shared)
authz_host_module (shared)
authz_user_module (shared)
autoindex_module (shared)
cgi_module (shared)
cgid_module (shared)
deflate_module (shared)
dir_module (shared)
env_module (shared)
mime_module (shared)
fastcgi_module (shared)
proxy_module (shared)
proxy_http_module (shared)
reqtimeout_module (shared)
rewrite_module (shared)
setenvif_module (shared)
ssl_module (shared)
status_module (shared)
suexec_module (shared)
Syntax OK

How can I get all my services and panel back up and running with my Wildcard Cert??

Quote from gOOvER

Whats the Error Message, when Apache won't start??

Sorry - I dont have the exact error messages handy. (yes, I know - bad admin... I was time crunched on a production machine, but that was no excuse)

In some cases, the restart of services would outright fail, leaving me with no system running. Apache would not restart, and I just rolled back the VM to the latest snapshot and tried the next upgrade.

In one instance that comes to mind, there was a short error message that popped up indicating an SSL configuration error. Again, this is a running system. so I needed to get things working again - so I rolled back to the VM snapshot and tried next upgrade.

If I get a chance later today, I'll spin up a new VM and try to replicate.