Posts by UncleJ

    Hi,


    sounds like the cron is not able to find php - perhaps it is not in the PATH - try to call it with the complete path of your php binary.


    Regards Jörg

    Hello MoosehMan,


    which level has your customer for running cronjobs (cronjob type)? If set to full or jailed it should be possible. If set to URL you only can run jobs by passing a URL.


    Regards Jörg

    Hello,


    I noticed that when using the 10_roundcube_tls.pl listener file the hostname of the user login does not match the mail_host entry in the database because the hostname in the roundcube config is changed from localhost to BASE_SERVER_VHOST. So all user settings are saved as new entry in the database because during the i-MSCP update all mail_host entries are updated to localhost again (Roudcube installer -> sub _updateDatabase). Perhaps the listener should also update the database table.


    Regards Jörg

    Hello,


    the menu entry under profile is not correct in the german translation - it is written "YubiKey verwaltung" but it should be "YubiKey Verwaltung" (small improvement for the next release). It is the same for all three access levels.


    Regards Jörg

    Hello,


    I have tried to set up my YubiKey to the Reseller account after I linked it but I got the message that the key is already used for one account.
    I would like to use the YubiKey for several accounts (admin, reseller, domains) in order to have higher security level for all of them. Perhaps another setting (use key just for one accound <-> allow key for several accounts) would be helpful for others too?


    Regards Jörg

    @Nuxwin


    This would be pefect the way you explained.
    Currrently the master for domain.tld is on server1 where it is configued as client with glue records and synced to server2. The zones for panel1 and panel2 are on their own server and then synced to the other one. Same for the customers defined on each server. So each server is master for its own customers and slave for the customers of the other server.

    Hello everybody,


    I hope it is okay to add my thoughts on this here.
    I am running two instances of i-MSCP on two different servers - they are named <panel1>.<domain.tld> and <panel2>.<domain.tld> for hostnames as well as for panel. Both are DNS slaves for each other and also BackupMX (automatically configured using scripts installed by listeners). The glue records are done in the customer <domain.tld> on the primary server.


    Generally I like suggestion because it will end up in a clean and lean configuration but I guess my idea of having two servers on the same domain would not work anymore except using <sub1>.<domain.tld> and <sub2>.<domain.tld> instead of <domain.tld> which would result in longer names for the panel (<panel>.<sub1>.<domain.tld>).


    Perhaps I missed something but I guess similar thoughts might come up when heading a planed multi server deployment.


    Regards Jörg

    @Nuxwin


    Hello,


    okay, I will try to remember that.


    The entries should be merged. So in case that there are globally defined mx-entries and per Domain defined ones, both should be added. This should help to cover all possible combinations then (only global, only local, some global for all and special per domain, a.s.o.). In case both contain the same key (is it also a key when talking about a HASH?) the value should be taken from domain specification.


    Thanks in adavance for your fix - it will also help for some other files I have nearly finished ;)


    Regards Jörg