Posts by kess

    Thank you for your investigation and for confirming the bug.
    At present I've re-created the root user on all the MySQL instances, so it's a non problem...


    Regarding the code part you have missed, don't worry, it happens to the bests also :thumbup:

    Hello guys,
    I've searched the forums and the issue tracker but didn't find anything related.


    After upgrading to 1.3.0 (and also with 1.3.1) my MySQL root user account is deleted from the system.
    As written in the errata file, the root account in MySQL souldn't be changed:

    Code
    1. Note that while installing or reconfiguring i-MSCP, the installer will still ask you for the SQL root user info when needed. However, this user will be only used to create and grant privileges to i-MSCP SQL users. This means that i-MSCP will never store any data related to the SQL root user, nor change any of its properties.
    2. Be also aware that in latest versions of the i-MSCP PhpMyAdmin package, usage of SQL root user has been prohibited for security reasons. If you want connect to PhpMyAdmin to work on all databases, you should now use the i-MSCP master SQL user.

    I really like a lot what the errata says, but unfortunately this is not what happening (at least on my systems).


    I don't have logs to provide, if you need any further info please let me know, I'll be pleased to send everything needed.


    System: Debian Jessie x64
    i-MSCP: 1.3.1 FPM, ProFTPD, Dovecot
    Plugins: ClamAV, Mailgraph, Monitorix, OpenDKIM, PhpSwitcher, Postscreen, RoundcubePlugins, ServerDefaultPage, SpamAssassin


    Thank you very much,
    bye Kess.

    @kess
    You're totally right ;) If you use the same domain for many i-MSCP instances (each in a subzone as you mention). That exactly why we require a FQHN for the base server vhost ;)


    Well, the other method could be to use 1 unique domain for each instance... But I can't see how it could be useful... :-)

    @kess vuxxx.fqdn.tld would work

    I dont agree with you, at least not totally.
    It works correctly if you have 1 single server.


    Example:
    Server 1 : server1.mydomain.tld
    Server 2 : server2.mydomain.tld


    At present I have a record in the registrar DNS that tells:
    *.server1.mydomain.tld A 1.2.3.4
    *.server2.mydomain.tld A 2.3.4.5
    So it works without intervention because every vuxxxx.serverX.mydomain.tld are transparently "created" or better, automatically resolved.


    But if you remove the subdomain alias from the panel address:
    First Problem: If you want to act like the Change Request, you have to setup each vuxxxx.mydomain.tld individually in your registrar DNS (at least for my case)
    Second Problem: Who grants that vuxxxx can't be on both systems ?


    Do you see what happens ?

    You have to do this before with mysql... I'm on mobile at present and I can't confirm the exact query but it should be something like:
    UPDATE plugins SET plugin_status='disabled';
    and it should be run in imscp database