Posts by Heppi

  • Update order (i-MSCP, debian stretch)

    Hello Nuxwin,


    I have the plan to update debian to stretch next week and also i-MSCP to 1.4.5.
    What would be the correct order?
    First a full dist-upgrade of debian, or first an update to i-MSCP?
    What happens to mysql_5.5 since strech will use MariaDB? Is an update with no problems possible?
    Will i-MSCP do the DB migration automagically or is it debian (or stays it at mysql)? For this part I am really confused and are in doubt!
    Of course a do a backup before :-)
    but who knows what happens... ?(


    ## i-MSCP version info
    BuildDate = 20170107
    Version = 1.3.16
    CodeName = Horner
    # Distro info
    DISTRO_ID = debian
    DISTRO_CODENAME = jessie
    DISTRO_RELEASE = 8.7 (really is 8.8 latest)
    # Plugins
    DebugBar Version 1.1.2
    LetsEncrypt Version 3.1.0 (Build 2017041700)
    Mailman Version 1.0.3 (Build 2017021601)
    PanelRedirect Version 1.1.5
    RoundcubePlugins Version 1.2.6
    # Servers
    FRONTEND_SERVER = nginx
    SQL_SERVER = mysql_5.5
    PO_SERVER = dovecot
    NAMED_SERVER = bind
    HTTPD_SERVER = apache_php_fpm
    FTPD_SERVER = proftpd
    MTA_SERVER = postfix
    PHP_SERVER = php5

  • unknown command: postscreen_pipelining_enable

    check doch mal durch


    Shell-Script
    1. postconf -n | grep postscreen

    die PostScreen config. Vielleicht ist durch einen Fehler in der main.cf das postscreen_pipelining_enable in die postscreen_access_list gerutscht!
    Es sollte postscreen_pipelining_enable auf einer separaten Zeile stehen.

  • unknown command: postscreen_pipelining_enable

    Eventuell ist dein Postfix zu alt

    Code
    1. postconf -d | grep mail_version


    Code
    1. postscreen_pipelining_enable (default: no)
    4. Enable "pipelining" SMTP protocol tests in the postscreen(8) server. These tests are expensive: a good client must disconnect after it passes the test, before it can talk to a real Postfix SMTP server.
    7. This feature is available in Postfix 2.8.

  • Letsencrypt failed due to missing updates after January 28th

    Hello Nuxwin,


    I am using
    ## i-MSCP version info
    BuildDate = 20161123
    Version = 1.3.8
    CodeName = Horner
    # Distro info
    DISTRO_ID = debian
    DISTRO_CODENAME = jessie
    DISTRO_RELEASE = 8.6


    Letsencrypt 2.04 (and now 2.05)
    I had the following error message after 28 Jan on four of my sub/domains.


    Code
    1. Saving debug log to /var/log/letsencrypt/letsencrypt.logStarting new HTTPS connection (1): acme-v01.api.letsencrypt.orgRenewing an existing certificateAn unexpected error occurred:The server experienced an internal errorPlease see the logfiles in /var/log/letsencrypt for more details.


    accidentally I ran:

    Code
    1. certbot-auto --help


    which automatically updates itself and afterwards also these particular four domains.


    But now these domain certs are only on disk and not in DB for usage via i-mscp.


    Is there some config option to transfer the certs to db?


    thx
    Peter


    BTW: Letsencrypt itself now works perfect for newly created domains and renews!

  • Mails land in Spam

    Another possibility is (when you aquired this server(IP) freshly in recent time) that this IP is listed from former owner.


    I had this problem last year when I bought a new server. The IP was used by a spammer before :-(

  • Change PW of mail user doesn't work

    Yesterday evening it was:

    Code
    1. root 478 0.0 0.0 12664 1668 pts/3 S+ 17:10 0:00 grep imscproot 2634 0.0 0.0 4336 812 ? Ss 12:00 0:00 /bin/sh -c nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.pl > /dev/null 2>&1root 2639 0.0 0.0 60440 14556 ? SN 12:00 0:00 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.plroot 10692 0.0 0.0 4336 756 ? Ss 13:00 0:00 /bin/sh -c nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.pl > /dev/null 2>&1root 10693 0.0 0.0 60456 14564 ? SN 13:00 0:00 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.plroot 15093 0.0 0.0 4336 808 ? Ss 15:00 0:00 /bin/sh -c nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.pl > /dev/null 2>&1root 15094 0.0 0.0 60456 14472 ? SN 15:00 0:00 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.plroot 18430 0.0 0.0 4336 764 ? Ss 14:00 0:00 /bin/sh -c nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.pl > /dev/null 2>&1root 18431 0.0 0.0 60440 14472 ? SN 14:00 0:00 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.plroot 19480 0.0 0.0 4336 800 ? Ss 10:00 0:00 /bin/sh -c nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.pl > /dev/null 2>&1root 19484 0.0 0.1 166864 21652 ? SN 10:00 0:00 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.plroot 19493 0.0 0.1 72208 18484 ? SN 10:00 0:00 perl /var/www/imscp/engine/imscp-rqst-mngrroot 22895 0.0 0.0 4336 760 ? Ss 16:00 0:00 /bin/sh -c nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.pl > /dev/null 2>&1root 22896 0.0 0.0 60440 14484 ? SN 16:00 0:00 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.plroot 27223 0.0 0.0 4336 720 ? Ss 11:00 0:00 /bin/sh -c nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.pl > /dev/null 2>&1root 27224 0.0 0.0 60440 14508 ? SN 11:00 0:00 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.plroot 30729 0.0 0.0 4336 708 ? Ss 17:00 0:00 /bin/sh -c nice -n 15 ionice -c2 -n5 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.pl > /dev/null 2>&1root 30730 0.0 0.0 60456 14624 ? SN 17:00 0:00 perl /var/www/imscp/gui/plugins/LetsEncrypt/cronjobs/pending.plroot 31910 0.0 0.0 4216 1060 ? S 17:07 0:00 /var/www/imscp/daemon/imscp_daemon -b /var/www/imscp/engine/imscp-rqst-mngr -p /var/run/imscp_daemon.pidroot 32592 0.1 0.1 72924 19316 pts/4 S+ 17:08 0:00 perl /var/www/imscp/engine/imscp-rqst-mngr -v


    Now it is:



    I do not have so many letsencrypt domains (only 13). Don't know whether this is related?!


    So, how to start that pw change test again. With services imscp* stopped or....
    thx
    Peter