Posts by sanitariu

    Thanks for the support. I patched manually webmail and some other stuff so i hope it works now by magic.

    I will wait and update next version when it goes out.

    Yes i have backups but that release touched a lot of stuff so i think it will be dangerous to try the backups.

    I still do not know if phpswitcher is working and some other plugins....

    I will wait and even pay for newer as far as i can update my current maintenance stuck now.

    As i said downgrading and upgrading is impossible now. And reinstalling is not an option for me.

    Please change maintenance to development or something like that so no other people get confused.


    By accident i upgraded my 1.5.3 installation to imscp-1.5.3-maintenance. This led to some huge problems. One is that i can not downgrade and the other

    is that i have problems with plugins even paid ones. I saw too late that we should not use imscp-1.5.3-maintenance but then why it is allowed to be downloaded ?

    You are unable to test it in real situation. Also the name maintenance is misleading. For me it means that this revision has just some small

    fixes over 1.5.3 and you should use it. If it is something else not for mass usage just name it development. Now i am stuck to nowhere.

    Can not downgrade and can not upgrade because as far as i know there is no newer version after 1.5.3 ?

    The error i have is: "Couldn't synchronize plugin data: Invalid plugin archive: The 'name' plugin info field is missing."

    Do you have any solution for me ?



    I am using latest stable i-mscp 1.5.3 installed on debian 8 system.

    I have opendkim installed.

    I have the following scenario:

    2 domains and in one client account.

    One of the domains have external mail server (

    Opendkim is enabled.

    When we try sending mail from that external server ( to email address from the

    other domain ( we always fail with the following reason:

    "5.7.1 rejected due to DKIM ADSP evaluation;"

    The problem is that "dkim=discardable" and we can not easy change that.

    Also we can not disable opendkim for a particular domain as it was before some releases.

    Any idea how can send email to without disabling opendkim globally ?

    i-MSCP 1.5.3

    Build: 20180516

    Codename: Ennio Morricone

    php -v

    PHP 5.6.36-1+0~20180505045733.13+jessie~1.gbp9b5cab (cli)

    Copyright (c) 1997-2016 The PHP Group

    Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies

    with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies


    I put image here:

    I can confirm that SSL is working normal !

    It just does not have dates and i am afraid not to stop ?

    Maybe i should try to reinstall the module ?

    Looking at /var/log/letsencrypt/letsencrypt.log

    I see:


    Your key file has been saved at:


    Your cert will expire on 2018-09-06. To obtain a........


    Seems like cache or something similar ?


    I am using Letrencrypt 3.4.2.

    I activated everything is working from ssl point of view.

    But clicking on letsencrypt for the domain i see N/A on Expiry date and N/A on Next renewal date.

    The same is on any domain i activate here. SSL working but no dates.

    Will the be a problem after 1 month ?

    I tried version 1.3.5.

    www:/usr/src/imscp-1.3.5# ./imscp-autoinstall -d

    This is what i got:

    iMSCP::Composer::_installPackages: Could not install/update i-MSCP packages from GitHub │

    │ │

    │ Please have a look at if you need help.

    I think this should print more information about what is the error.

    Is there anyway to disable at all Composer packages ?

    I do not need roundcube/awstats or anything like that.


    My problem is getting to version 1.1.21.

    I think have some bug in that version and stops the install. Can i somehow skip all

    www:/var/www/imscp/engine/setup# perl imscp-setup --skip-addons-update

    Does not help at all.

    Sorry for taking your time.




    I will do until 1.5.3.

    I am not sure if now i am at some middle broken setup or i can take another imscp version like 1.2.16 and start again the migrate process ?

    I think 1.1.21 have brokern or something like that. Can i disable at all ?