Any Updates on the Maintenance Release Thought it was suppose to be end of April ?
Finalization stage 
Posts by Nuxwin
-
-
THe version ist 3.5.0
No.
The code from the renew.pl script you showed above is not the one from the 3.5.0 version. Please upload the 3.5.0 version again.
Thec code should look as follows:
Display MorePerl- #!/usr/bin/perl
- # i-MSCP LetsEncrypt plugin
- #
- # @author Laurent Declercq <l.declercq@nuxwin.com>
- # @copyright (C) 2016-2018 Laurent Declercq <l.declercq@nuxwin.com>
- # @license i-MSCP License <http://www.i-mscp.net/license-agreement.html>
- use strict;
- use warnings;
- use FindBin;
- use lib "$FindBin::Bin/../../../../engine/PerlLib", "$FindBin::Bin/../../../../engine/PerlVendor";
- use Class::Autouse qw/ :nostat iMSCP::Database iMSCP::DbTasksProcessor iMSCP::Service /;
- use File::Basename;
- use iMSCP::Bootstrapper;
- use iMSCP::Debug;
- use iMSCP::Getopt;
- use JSON;
- # This script responsible for automatic renewal of SSL certificate which are
- # due for renewal, according the renewal policy. It is automatically added
- # as a cron job in the i-MSCP core cron file (e.g. /etc/cron.d/imscp).
- #
- # This script can also be run manually by administrator.
- sub getConfig
- {
- my ($db) = @_;
- my $dbi = $db->getRawDb();
- local $dbi->{'RaiseError'} = 1;
- my $config = $dbi->selectrow_hashref( "SELECT plugin_config FROM plugin WHERE plugin_name = 'LetsEncrypt'" );
- $config or die( "Couldn't find LetsEncrypt plugin configuration in database" );
- JSON->new()->decode( $config->{'plugin_config'} );
- }
- my $bootstrapper = iMSCP::Bootstrapper->getInstance();
- exit unless $bootstrapper->lock( '/var/lock/imscp-letsencrypt-renew.lock', 'nowait' );
- eval {
- newDebug( 'letsencrypt-plugin-renew.pl.log' );
- iMSCP::Getopt->parseNoDefault( sprintf( 'Usage: perl %s [OPTION]...', basename( $0 )) . qq{
- Process renewal tasks.
- OPTIONS:
- -d, --debug Enable debug mode.
- -v, --verbose Enable verbose mode.},
- 'debug|d' => \&iMSCP::Getopt::debug,
- 'verbose|v' => \&iMSCP::Getopt::verbose
- );
- setVerbose( iMSCP::Getopt->verbose );
- iMSCP::Bootstrapper->getInstance()->boot( {
- config_readonly => 'yes',
- norequirements => 'yes'
- } );
- my $db = iMSCP::Database->factory();
- my $qrs = $db->doQuery(
- 'u',
- "
- UPDATE letsencrypt
- SET letsencrypt_status = 'torenew', letsencrypt_previous_status = NULL, letsencrypt_status_date = UNIX_TIMESTAMP()
- WHERE letsencrypt_status = 'ok'
- AND letsencrypt_expires <= UNIX_TIMESTAMP() + ?
- ",
- getConfig( $db )->{'renewal_policy'} // 1814400
- );
- ref $qrs eq 'HASH' or die( $qrs );
- iMSCP::DbTasksProcessor->getInstance( mode => 'backend' )->process();
- };
- if ( $@ ) {
- error( sprintf( "Couldn't process Let's Encrypt renewal tasks: %s", $@ ) );
- exit 1;
- }
- END { $bootstrapper->unlock( '/var/lock/imscp-letsencrypt-renew.lock' ); }
- 1;
- __END__;
-
should the used plugins at i-mscp panel, always be disabled at i-mscp re-install or i-mscp upgrade to newer release ?
It is preferable
Then once after, you check for latest plugin release and you update them prior re-enabling them. -
dieses Problem liegt schon seit 2 Monaten bei mir rund vor - eine Lösung konnte ich auch noch nicht finden - vom Entwickler ist es als kosmentisches Problem mit low Prio eingestuft - k.a. wie lange es dauern wird, bis das behoben ist - es nervt sehr, weil ständig E-Mails kommen mit dem Fehler
aufgetaucht ist es, seit dem letzten pkg update, davor ohne ProblemeThis is a bug in SA, not i-MSCP plugin.
-
Da Du nach dem Dist Upgrade i-MSCP neu installieren musst, empfehle ich Dir vor dem Dist-Upgrade alle Plugins im Panel zu deaktivieren.
Dann hast Du bei der Installation von i-MSCP keine Probleme damit.
Auch empfehle ich Dir beim Upgrade immer die Maintainer Versionen (Konfigdateien) zu übernehmen. Dort hat sich einiges geändert
Not really a reinstallation
This is just like an upgrade. Basically put, i-MSCP will rerun the installation steps using layout for Debian Stretch but this will not remove customers' data. I prefer clarify the situation because some users could be affraid by the reinstallation term (they could think about a restinstallation from scratch). Of course, you're right from the internal implementation details point of view -
[WARN] (eval): Use of uninitialized value in addition (+) at /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/renew.pl line 63.
Good evening,
The version of your LE plugin (as showed in the plugin interface) is?
You could maybe show us the relevant line because it seem you're not really using latest LE plugin version. On my copy, there is not such addition (+)... The only addition (+) is done in the SQL query. Please post us the full content of the renew.pl script.
Regarding the package, it's surely because you use an old version of the LE plugin. in the CHANGELOG of the latest version (3.5.0), you can read:
-
No fix. This is the expected behavior. You cannot redirect a specific page ATM.
-
auch nach spamassassin reinstallation funktioniert es nicht.
Ich finde es seltsam dass mit netstat -tlpen | grep spam nichts kommt. Wo könnte ich da ansetzen?Maybe because SpamAssassin listen on UDS (Unix Domain Socket) which is not TCP
- Please result of the postconf smtpd_milters command
- Please content of your /etc/default/spamass-milter file
- Please content of your /etc/default/spamassassin file
- Content of your /etc/postfix/main.cf file
- Content of your /etc/postfix/master.cf file
and again, status of both spamassassin and spamass-milter services.
Thank.
-
Na dann raten wir mal was für Fehlermeldungen erscheinen..
Ohne eindeutige Fehlermeldungen kann hier niemand helfen.
I've removed his thread already for that reason.
Please read carefully: Reporting rules - Reminder
Basically put, you need in order:
- Install the latest release i-MSCP version, not the git version: https://github.com/i-MSCP/imscp/releases
- Make use of a supported distribution (Debian Jessie, Stretch, Devuan Jessie or Ubuntu 16.04 or 18.04)
Thank you.
-
For all user who are affected with the problem under Ubuntu!
Error Compiling PHP Versions for PHP Switcher
You have to replace
Well, not really. Those which are not on 16.04 version MUST not copy that by closing eyes