Is there a way to debug auto renew? My certificates are also not updated automatically, as if there is a missing cronjob.
If I set the state to "torenew" in the database, certs are renewed.
Edit: I've found this:
Edit2:
Commenting out "iMSCP::Service->getInstance( )->isRunning( 'mysql' ) or exit;" fixes the problem temporarily.
Edit3:
I've created an issue for that: https://youtrack.i-mscp.net/issue/IP-1774
Display MoreIs there a way to debug auto renew? My certificates are also not updated automatically, as if there is a missing cronjob.
If I set the state to "torenew" in the database, certs are renewed.
Edit: I've found this:
Code
- [DEBUG] iMSCP::Bootstrapper::boot: Booting backend....
- [DEBUG] iMSCP::LockFile::acquire: Acquiring exclusive lock on /var/lock/imscp.lock
- [DEBUG] iMSCP::EventManager::_init: Loading /etc/imscp/listeners.d/00_postfix_sendgrid.pl listener file
- [DEBUG] iMSCP::EventManager::_init: Loading /etc/imscp/listeners.d/10_apache2_dualstack.pl listener file
- [DEBUG] iMSCP::EventManager::_init: Loading /etc/imscp/listeners.d/10_named_zonetransfer.pl listener file
- [DEBUG] iMSCP::Service::_detectInit: Systemd init system has been detected
- [DEBUG] iMSCP::Execute::execute: /bin/systemctl --system is-active mysql.service <-- MySQL is not running as a local server but as an external service, it seems that the script exits here.
- [DEBUG] iMSCP::Provider::Service::Sysvinit::_exec: inactive
- [DEBUG] iMSCP::LockFile::release: Releasing exclusive lock on /var/lock/imscp-letsencrypt-pending.lock
- [DEBUG] iMSCP::LockFile::release: Releasing exclusive lock on /var/lock/imscp.lock
Edit2:
Commenting out "iMSCP::Service->getInstance( )->isRunning( 'mysql' ) or exit;" fixes the problem temporarily.
Edit3:
I've created an issue for that: https://youtrack.i-mscp.net/issue/IP-1774
Should it work to change:
iMSCP::Service->getInstance( )->isRunning( 'mysql' ) or exit;
to
iMSCP::Service->getInstance( )->isRunning( 'mariadb' ) or exit;
couse
/bin/systemctl --system is-active mariadb.service
active
root@web4you-server-02:/home/juerg#
??
iMSCP::Service->getInstance( )->isRunning( 'mysql' ) or exit;
to
iMSCP::Service->getInstance( )->isRunning( 'mariadb' ) or exit;
Of course yes, but only if your SQL server is local 
Basically, there are two issues:
To resume
The first issue is a bug in our letsencrypt plugin while the second is a bug in systemd that has been addressed lately by Lennart Poettering, following my report. See https://github.com/systemd/systemd/issues/7875
For the second issue, a fix has been added in our systemd provider because of course, the fix in systemd is not made available in systemd versions currently shipped with our favorite distributions and I've no idea whether or not it will be backported by the systemd Debian package maintainer. To workaround the issue in systemd versions prior the fix, our systemd provider will now resolve the unit aliases prior acting. Thus, even if in the cron task we're querying the mysql.service, which in the case of the MariaDB server is an unit alias, our provider will query the mariadb.service unit instead, that is, the unit that define the mysql.service unit alias. This fix will be part of i-MSCP 1.6.0.
See also: https://github.com/i-MSCP/imsc…s/Service/Systemd.pm#L295
<p>Hi,</p><p>I am user of this plug-in but I am not clear how to renew the certificates. Can you please give me a simple guide how I should renew them or what I should do to renew them?<br></p>
Hello Omi Azad,
You can Revoke and Re-create the certificate easily via the panel! (Screenshot)
Best regards.
So you are suggesting, I can revoke and create from the panel and it will do the renewal process, right?
Good evening!
Yes, there will be created a new certificate, with new 90 days validation!
Best regards
