Posts by Athar

    This is from the actual "nightly build" you can grab on Github directly :

    Added: Support for Debian Buster (10.x) - Experimental

    Be aware that this is not intended for production use, consider it as potentially "unstable" (not all tests has been done yet, it's close of a pre-prod version right now).

    You can read this post on more details about the next release date : Next release date....


    First : Your post isn't at the correct place. There is a section for all plugins support request. Thread moved.

    Secondly : You did not comply with the rules, no systems info, etc... we will not provide any help without further information (just because we can't, and you may use an older version of the plugin, or anything else, we just DON'T know that.)

    So, edit your first post with to be compliant with our forum rules and we might be able to help afterward. Without those "base details", we can't.

    I'm nice enough to give you the direct link of the rules' post : Reporting rules - Reminder


    The zone (and template also) is not encrypted in any way !

    But keep in mind this :

    - Manually change the value on the working zone will be undone when you make any changes through the web interface (which imply the DNS rebuild process)

    - To get this change permanent "easily", you have to change the template directly, but this change will then apply to all customers.

    (- Like I said, some kind of listener file might work, but for this, I'm unsure of the way doing that, and only for a specific domain)

    - Lastly, god Nuxwin may have a better solution :D

    After this, the choice is up to you.

    Also, remind you that when doing any i-MSCP upgrade, templates files will get back to their initial state unless you change it prior the upgrade process.

    If I'm not wrong, this is not possible for now.

    "www" entry is static in the DNS zone template file, so this is added for every kind of domains you manage by default through i-MSCP.

    However, I read somewhere that all the DNS thing is being reworked (at least on the todo) so that all DNS entries would be stored into DB and make all those available for modification by end-user.

    In the meantime, maybe some kind of listener file could be use, but as this is only for one domain, honestly, I don't know how to handle that case.

    Hey Nuxwin , me again :D

    I tried to install the DebugBar without success on release 1.5.3-2018120800

    On the plugin page, it's marked "Version compatible with i-MSCP Serie ≥ 1.5.x (version ≥ 1.5.2)"

    but, in the info.php of the plugin :

    'require_api' => '1.5.1'

    But, if I'm not wrong, this plugin API will be at that version for the upcoming release ?

    This is my imscp.conf, maybe it's wrong, or not :D :

    Hi Nuxwin and HB to you (don't buy a car :D ),

    I'm faced to an issue, which I'm unsure why it happen.

    Steps to reproduce :

    - Get into any customers

    - Create a subdomain

    - In LetsEncrypt, request a certificate for this newly created subdomain (after a few minutes for DNS replication)

    - Go back to the subdomain, SSL Management then enable HSTS

    There, I get :

    - An unexpected error occur.

    - An email with this content :

    As you can see, I can't go further, I don't even get the SQL query :/

    For the test, I did create another subdomain for which I have a Comodo cert.

    Did add the certificate to that subdomain, then after, enable HSTS, it work.

    There might be something wrong between Letsencrypt plugin and subdomain.

    LetsEncrypt on a base domain is working just fine for HSTS, only subdomain seems impacted.

    What can I do to troubleshot this error ?

    Versions :

    Debian 9.8 up-to-date

    I--MSCP 1.5.3-2018120800

    LetsEncrypt : 3.5.0

    PHP Fcgi