Posts by verleihnix

    Dear All,

    I have to setup one special domain with PHP- Settings different from the rest. Using FPM, this has to be done in /etc/php7.1/fpm/pool.d/domain.conf, as described in Config single domain php.ini . This is working fine, but when updating or reconfiguring i-mscp these changes are lost.

    is there a way to prevent these settings from being overwritten?

    My configuration is
    Debian 9, i-MSCP 1.5.x-konzeptplus, PHP-FPM 7.1

    Best regards

    Dear all,

    im migrating my i-mscp installation to a new server. There i have to setup a recipient whitelist within the policyd_weight plugin. On my old Installation (1.2.x) i used a Listener file to do so.

    Here the File:

    1. # i-MSCP - internet Multi Server Control Panel# Copyright (C) 2013-2016 by Sascha Bay## This program is free software; you can redistribute it and/or# modify it under the terms of the GNU General Public License# as published by the Free Software Foundation; either version 2# of the License, or (at your option) any later version.## This program is distributed in the hope that it will be useful,# but WITHOUT ANY WARRANTY; without even the implied warranty of# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the# GNU General Public License for more details.## You should have received a copy of the GNU General Public License# along with this program; if not, write to the Free Software# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA .### Allows to setup policyd-weight whilelist maps.#package Listener::Postfix::Policyd::Whitelist;use strict;use warnings;use iMSCP::Debug;use iMSCP::EventManager;use iMSCP::Execute;### Configuration variables#my $policydWeightClientWhitelist = '/etc/postfix/imscp/policyd_weight_client_whi telist';my $policydWeightRecipientWhitelist = '/etc/postfix/imscp/policyd_weight_recipie nt_whitelist';my $checkClientAccess = "\n check_client_access hash:/etc/postfix/imscp/policyd_ weight_client_whitelist,";my $checkRecipientAccess = "\n check_recipient_access hash:/etc/postfix/imscp/po licyd_weight_recipient_whitelist,";### Please, don't edit anything below this line#iMSCP::EventManager->getInstance()->register('afterMtaBuildMainCfFile', sub { my $tplContent = shift; return 0 unless -f $policydWeightClientWhitelist && -f $policydWeightRec ipientWhitelist; my ($stdout, $stderr); my $rs = execute("postmap $policydWeightClientWhitelist", \$stdout, \$st derr); debug($stdout) if $stdout; error($stderr) if $stderr && $rs; return $rs if $rs; $rs = execute("postmap $policydWeightRecipientWhitelist", \$stdout, \$st derr); debug($stdout) if $stdout; error($stderr) if $stderr && $rs; return $rs if $rs; if ($$tplContent !~ /check_client_access/m) { $$tplContent =~ s/(reject_non_fqdn_recipient,)/$1$checkClientAcc ess/; } if ($$tplContent !~ /check_recipient_access/m) { $$tplContent =~ s/(reject_non_fqdn_recipient,)/$1$checkRecipient Access/; } 0;});1;__END__

    When using this in current 1.5.1 version, imscp-reconfigure ist aborted

    1. root@s: /etc/postfix/imscp: /var/www/imscp/engine/setup/imscp-reconfigure -d [FATAL] iMSCP::EventManager::_init: Can't locate iMSCP/ in @INC (you may need to install the iMSCP::EventMaanger module) (@INC contains: /var/www/imscp/engine/setup/../PerlLib /var/www/imscp/engine/setup/../PerlVendor /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /etc/imscp/listeners.d/ line 27.
    2. BEGIN failed--compilation aborted at /etc/imscp/listeners.d/ line 27.
    3. Compilation failed in require at /var/www/imscp/engine/setup/../PerlLib/iMSCP/ line 266.

    I'm not a perl-programmer, so it's difficult to understand the problem. So my question is: How can i configure a whitelist with current version and make this changings persistent?

    Requested information to my installation:
    Debian Stretch, i-mscp 1.5.1, PHP-FPM, Plugin PolicydWeight Version 1.3.0 (Build 2018032000)

    Best regards


    today i performed an update from 1.2.17 to 1.3.8. it ended with
    'i-MSCP has been successfully installed/updated.'
    but proftpd did not start correctly. a service proftpd restart says

    1. root@vs /usr/local/src/imscp-1.3.8: service proftpd restart/etc/init.d/proftpd: Zeile 48: [: Argument erwartet.[ ok ] Stopping ftp server: proftpd.[....] Starting ftp server: proftpdvs proftpd[14304]: mod_tls/2.4.3: compiled using OpenSSL version 'OpenSSL 1.0.1e 11 Feb 2013' headers, but linked to OpenSSL version 'OpenSSL 1.0.1t 3 May 2016' libraryvs proftpd[14304]: mod_sftp/0.9.8: compiled using OpenSSL version 'OpenSSL 1.0.1e 11 Feb 2013' headers, but linked to OpenSSL version 'OpenSSL 1.0.1t 3 May 2016' library. ok

    My System is
    - Debian 7.11
    - in an OpenVZ container
    - i-mscp is now 1.3.8
    - proftp

    proftpd ssl-conf is

    excluding tls and sftp brings back proftp without ssl, but the following remains:
    root@vs /usr/local/src/imscp-1.3.8: service proftpd restart
    /etc/init.d/proftpd: Zeile 48: [: Argument erwartet.

    As a next step i planned to upgrade from wheezy to jessie, but not sure to proceed. would this solve my problem?

    best regards

    Since i-MSCP 1.2.12, there is a new setup dialog asking you which port range you want use for the FTP server. If your're behind a NAT, you should in order:

    Restrict this port range such as 33000 to 33500


    what is the expected port range for this dialog? my server uses a range of 200 somewhere in the 61000s, but the dialog did not accept that. it is possible to set passive ports in proftpd.conf afterwards.

    best regards

    flames, thank you, this solved the problem.

    perhaps somebody can correct the text in config.php to state that the path to the certificate is necessary, even if it is the same as the server cert, but not a wildcard cert.

    best regards


    last weekend i did an upgrade from i-mscp 1.1 to 1.2.17 and installed serverdefaultpage 1.2.2. at the server's name i can see the new default page. fine! but when i use i receive an error message verwendet ein ungültiges Sicherheitszertifikat. Dem Zertifikat wird nicht vertraut, weil es vom Aussteller selbst signiert wurde. (Fehlercode: sec_error_unknown_issuer)

    the server panel's certificate is installed correctly and isn't a self signed certificate. config.php is unchanged (leave empty for default value (panel certificate)). what's going wrong here? do i need to config?

    best regards