* Backup filename changed
Changed the backup filename for running more backup each day - for example every 4 hours
* Restore user fix with new backup date
* Check if the backup name has an old notation
* Fix backup permission check
* fixed regex
* fix
Add a file that's setting the hostname certificate for exim, dovecot & vesta-web so the email is always with a valid LE certificate.
# Todo:
- add to cronjobs (default every month) of adds to lets encrypt renewall/request when updating system hostname certificate
This issue is getting some hits on the forum. Tiny typo on Line 58.
exponent=$(openssl pkey -inform perm -in "$key" -noout -text_pub |\
-inform perm is not a valid openssl pkey option. The correct code iis:
exponent=$(openssl pkey -inform pem -in "$key" -noout -text_pub |\
I check some servers and some times I see than cname not working, I check records and the problem is than some useres add record whit a dot ( in vesta GUI or CLI )
comerecord. in cname 2222 google.com
and vesta add it as it
cname. 14400 IN CNAME google.com.
test. 14400 IN MX 10 mail.googl.com.
So whit this pull we remove that dot if added
hola 14400 IN CNAME test.net.
record 14400 IN CNAME hola.es.
recordar 14400 IN CNAME Tres.net.
This solve the dot but I think in a while loop, because vesta leave add users cname thiw multiple dots:
Adding DNS Record → Record cname.......sdd.net has been created successfully.
Maybe vesta team have better solution for this one.
With use "mv" command, configuration file owner, group and permission will become "root: root" with default permissions. This can lead to access problem, because a services will cannot access to the configuration file. For example, "named", will cannot restart, because required user "named" access to own configuration file.
"Cat" command, will be overwrite config file too, but it saves owner / group / permissions original file.
