SSL certificate installation problem [SOLVED]

[zn23per]

EDIT: i found a way to solve the problem, e manually inserted the keyfile path on httpd-vhosts.conf

sorry for the spam



---------------

Hi guys, i have a problem that i can't find the answer by search, i was installing Let's Encrypt certificates on my domains, all sub-domains worked fine, but when i was installing it on the panel domain i got an problem, after e changed the port from 80 to 443, the daemon runned itself before i could insert the paths to the certificate files (the port and the keyfiles paths are set on diferent pages) now i cant acess the panel to insert the certificates (apache complains that there are no certificates inserted), i tried placing it manually but with no sucess.

Is there any way to fix it without reinstalling the whole panel ?
Thanks, and sorry for any english mistakes

[TGates]

manually edit /etc/sentora/configs/apache/httpd-vhosts.conf and either add them there and restart apache, then add them inside custom vhost override so they will always be re-written to the httpd-vhosts.conf file.

[robinsouthchina]

manually edit /etc/sentora/configs/apache/httpd-vhosts.conf and either add them there and restart apache, then add them inside custom vhost override so they will always be re-written to the httpd-vhosts.conf file.

If somebody finds that when they try to go to their control panel and they get forwarded to one of their normal domains (and NOT the panel which one has just tried to encrypt): this may be the problem.  I had lost access to the control panel.

I just had a problem that this post helped me solve.  In a nutshell, I found that the installation of the ssl certificate using letsencrypt did not save the port to 443 but 80.  That is when I looked in this file:

 /etc/sentora/configs/apache/httpd-vhosts.conf 

I saw that the port was 80 not 443. I was having the problem that when i went to my control panel it would forward me to my normal domain.  

I thought I saved it as 443 inside the control panel ... i was very very very careful in following the instructions so i'm sure that I had already set the port to 443 and saved it.  ... but anyways ... 

If somebody finds that when they try to go to their control panel and they get forwarded to one of their normal domains (and NOT the panel which one has just tried to encrypt): this may be the problem.  I had lost access to the control panel.