Is it compatible Certbot with Sentora SSL module

[franmm25]

I am used to using Certbot and that it automatically updates all the Certificates with a command line, in fact, it updates everything in such a way that even the emails are encrypted with Sentora, which I am currently having problems with since the new version 2.0.2, I wanted know if it is possible to use Certbot, despite having the Sentora Let's Encrypt SSL module active or not, greetings

[TGates]

I am used to using Certbot and that it automatically updates all the Certificates with a command line, in fact, it updates everything in such a way that even the emails are encrypted with Sentora, which I am currently having problems with since the new version 2.0.2, I wanted know if it is possible to use Certbot, despite having the Sentora Let's Encrypt SSL module active or not, greetings

I don't see an issue thinking about how they work. You just need to use a different location for your certbot certs in case you remove the Sencrypt module.

[joanlowachicago]

I've been facing issues with Sentora 2.0.2 as well. Does anyone have tips on configuring Certbot to work smoothly with Sentora's SSL module? __  __color block jam

[TGates]

I've been facing issues with Sentora 2.0.2 as well. Does anyone have tips on configuring Certbot to work smoothly with Sentora's SSL module? __  __color block jam

Sentora's SenCrypt SSL module works just fine on v2.0.2
I would not suggest using Certbot since SenCrypt is integrated into Sentora's core. (File paths, vhosts configs, etc.)
What issues are you having with Sentora v2.0.2 and SenCrypt?

[Sophiasmith]

I have an error when SenCrypt creates a new SSL but does not automatically update the vhost file, so the website still reports that it is not secure even though the cert has been issued - do you have any way to fix it? 

[TGates]

I have an error when SenCrypt creates a new SSL but does not automatically update the vhost file, so the website still reports that it is not secure even though the cert has been issued - do you have any way to fix it? 

It should re-write the vhost and reload apache on the next daemon run (Every 5 mins). Check the httpd-vhosts.conf file to make sure it updated it (after the 5  minutes). If it isn't updating, then we will have to help you sort it out.