Hallo @bcde
du kannst zurückstellen indem du in der Datei bind.data folgenden Eintrag änderst: BIND_DB_FORMAT = raw=0
Grüße
Jörg
Sorry für die Doppelposts - hatte eine Fehlermeldung erhalten und keinen EIntrag gesehen.
Hallo @bcde
du kannst zurückstellen indem du in der Datei bind.data folgenden Eintrag änderst: BIND_DB_FORMAT = raw=0
Grüße
Jörg
Sorry für die Doppelposts - hatte eine Fehlermeldung erhalten und keinen EIntrag gesehen.
the english version of the message is "Domain panel1.<tld> is unavailable." (replaced the actual domain by <tld>)
I did the following steps:
Regards Jörg
Hi,
I am sure that this will solve the issue - normally the traffic collection is run every half hour so you should see the result soon.
Regards Jörg
Hello @rgabor73,
have you updated your i-MSCP on the 6th? There was a bug in one of the older versions that traffic had not been counted correctly - this is fixed in the latest version 1.4.6. If you are running an older version you should update.
Regards Jörg
Hello,
I tried to replace the PanelRedirect-Plugin as described here but when I try to create a new customer with the panel domain it says that the domain is not available (see screenshot). When using a subdomain of an existing customer it works fine.
Can anybody confirm?
Regards Jörg
Hi,
yes I guess you have to create a script which renames or repacks everything before you transfer it to your backup location. I use the script (collects all backups to one folder named by date, creates subfolder by customer and then transfers folder) below to transfer all backups via rsync - you can try to adapt it to use with mput:
If mput cannot transfer folders you could tar the backup_folder before transfering.
Regards Jörg
Hello Viktor,
I noticed the same with my backup script. I rewrote it to take the name of the domain from the directory and attach it to the final filename so that each file is named individually again.
Regards Jörg
currently I am not really sure if this is the problem. He did not write under which address / port he is trying to access the panel but I also assume that he still tried to access the panel over the standard HTTPS port. Let's see if this is really the case.
Hallo @Iceman,
hast du versucht das Panel nur über die Domain zu erreichen oder auch den entsprechende Nginx-Port verwendet? Nachdem das Panel-Redirect deaktiviert ist, ist das Panel nicht mehr über Port 443 erreichbar.
Gruß Jörg
Hello,
I have upgraded from 1.4.3 to 1.4.4 last friday. Since then no system backups are created even in config BACKUP_IMSCP = yes is set.
The log imscp-backup-imscp-mngr.log says
The customer backups work as expected.
Can anybody confirm this?
Regards Jörg