Posts by fulltilt

    installtion works, but afterwards when create a new reseller or client the panel shows

    Code
    1. Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /var/www/imscp/gui/library/vendor/Zend/library/Zend/Form.php on line 1173 Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in /var/www/imscp/gui/library/vendor/Zend/library/Zend/Form.php on line 1690

    seems the ZEND library conflicts with composer 2.x ...

    any idea?

    - IMSCP: 1.5.3

    - Distribution: Debian 9

    - Proftpd

    - PHP FPM

    - MariaDB 10.1

    - Dovecot

    - Roundcube

    - Web2FTP

    - Plugins: PMA Captcha, RoundCubePlugins, SpamAssassin , LetsEncrypt, PHPswitcher, ClamAV



    is there a way to update the composer package without using the i-mscp installer - means only composer update from 1.8.0 to 2.1.3?

    Code
    1. nano /usr/local/src/imscp-1.5.3-mod-new/engine/PerlLib/iMSCP/Composer.pm
    2. # search for
    3. $self->{'composer_version'} = '1.8.0';
    4. # change to
    5. $self->{'composer_version'} = '2.1.3';

    that works so far, but I don't want to use the installer for some installations because of. special adaptations

    nano /var/www/imscp/gui/plugins/PhpSwitcher/backend/PhpSwitcher.pm

    # change:

    for my $phpVersion ( qw/ 5.6 7.0 7.1 7.2 7.3 7.4 / ) {

    # to:

    for my $phpVersion ( qw/ 5.6 7.0 7.1 7.2 7.3 7.4 8.0 / ) {



    nano /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/php_compiler.pl

    #search for: End of life


    # replace:

    '7.4' => [ # End of life: December 2022 - Unreleased yet

    '7.4.0RC4', 'https://downloads.php.net/~derick/php-7.4.0RC4.tar.gz'

    ]


    # with


    '7.4' => '7.4.5', # End of life: 28 November 2022

    '8.0' => '8.0.1' # End of life: 26 November 2023


    # run

    perl /var/www/imscp/gui/plugins/PhpSwitcher/PhpCompiler/php_compiler.pl --register --packaged --packaged-only

    some more fixes:

    Code
    1. # Bind9 when ipv6 disabled (Unable to fetch DNSKEY set)
    2. sudo nano /etc/default/bind9
    3. OPTIONS="-u bind -4"
    Code
    1. # LetsEncrypt fix
    2. mv /opt/eff.org /opt/eff.org_OLD
    3. cd /tmp
    4. sudo wget https://raw.githubusercontent.com/certbot/certbot/7f0fa18c570942238a7de73ed99945c3710408b4/letsencrypt-auto-source/letsencrypt-auto
    5. chmod a+x letsencrypt-auto
    6. ./letsencrypt-auto --dry-run


    Code
    1. # Proftpd starter
    2. nano /etc/default/proftpd
    3. #below
    4. CONFIG_FILE=/etc/proftpd/proftpd.conf
    5. # add
    6. # Master system-wide proftpd switch. The initscript
    7. # will not run if it is not set to yes.
    8. RUN="yes"
    Code
    1. # dovecot TLS protocols
    2. nano /etc/dovecot/dovecot.conf
    3. #ssl_protocols = !SSLv3
    4. ssl_min_protocol = TLSv1.2
    5. ssl_dh=</etc/dovecot/dh.pem
    6. # run
    7. dd if=/var/lib/dovecot/ssl-parameters.dat
    8. openssl dhparam -out /etc/dovecot/dh.pem 4096
    9. sudo service dovecot restart

    debian9 to debian10 fixes

    Code
    1. sudo apt purge rsyslog
    2. sudo apt install rsyslog
    3. systemctl daemon-reload
    4. sudo service rsyslog restart

    you should purge & re-install also:

    dovecot, fail2ban, spamassassin, opendkim, postfwd

    because pid location changed from "/var/run" to "/run"

    or edit all these files:

    Code
    1. nano /lib/systemd/system/dovecot.service
    2. nano /etc/systemd/system/multi-user.target.wants/dovecot.service
    3. PIDFile=/run/dovecot/master.pid

    logrotate

    and another dovecot fix ...


    reboot afterwards