Sentora SSL install problem

[Ubiquitous]

Take a look at this article.
http://blogs.tanertemel.co.uk/2015/04/en...ecure.html

That was indeed a very clear and useful post. But the httpd fails to restart and complains about the port is busy. I have encountered this before when 2 configs on the system were both listening on port 443,

Code:

-- Unit httpd.service has begun starting up.
May 24 15:53:26 panel.xxxxxxxx.net httpd[4420]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:443
May 24 15:53:26 panel.xxxxxxxx.net systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
May 24 15:53:26 panel.xxxxxxxx.net kill[4421]: kill: cannot find process ""
May 24 15:53:26 panel.xxxxxxxx.net systemd[1]: httpd.service: control process exited, code=exited status=1
May 24 15:53:26 panel.xxxxxxxx.net systemd[1]: Failed to start The Apache HTTP Server.

But now I can't figure out what is causing this problem. netstat -tulpn does not show port 443 open when httpd service is stopped (duh), so somehow it must be trying to open the port twice. The httpd service spins up when I bring back the original httpd-vhost.conf file and fail again when overwriting it from the Sentora Apache module.

Sentora is installed in panel.mydomain.com, and the SSL-cert is for mydomain.com, which I also choose to "Override a Virtual Host setting". I have tried to point to the SSL-cert in the httpd's ssl.conf, but then it fails to go to the correct home dir of the domain. Port 80 goes fine to mydomain.com/index.html but the SSL on port 443 only goes to the Apache default page.  

Any ideas?

UPDATE:
I commented out the listening on port 443 in /etc/httpd/conf.d/ssl.conf and it stopped complaining about open ports, and instead gave me this quite plain error message

Code:

May 24 16:51:51 panel.xxxxxxxx.net systemd[1]: Starting The Apache HTTP Server...
May 24 16:51:51 panel.xxxxxxxx.net systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
May 24 16:51:51 panel.xxxxxxxx.net kill[5412]: kill: cannot find process ""
May 24 16:51:51 panel.xxxxxxxx.net systemd[1]: httpd.service: control process exited, code=exited status=1
May 24 16:51:51 panel.xxxxxxxx.net systemd[1]: Failed to start The Apache HTTP Server.
May 24 16:51:51 panel.xxxxxxxx.net systemd[1]: Unit httpd.service entered failed state.

UPDATE 2:
Ok I just discovered that https://www.mydomain.com brings the browser to the correct public_html, but https://mydomain.com brings up the Apache default page. This is so wierd.