Support for Debian 11 just released
- myVesta
- Site Admin
- Posts: 932
- Joined: Fri Jun 19, 2020 9:59 am
- Has thanked: 8 times
- Been thanked: 6 times
We are pretty sure that this is the first hosting panel that has support for Debian 11.
Keep in mind that it's still in testing phase.
(by the way, Debian11 is not released yet)
You can install Debian11 and then follow instructions from https://www.myvestacp.com/#how-to-install in order to install myVesta.
- myVesta
- Site Admin
- Posts: 932
- Joined: Fri Jun 19, 2020 9:59 am
- Has thanked: 8 times
- Been thanked: 6 times
Too early, since Debian11 will come probably after July 31.
We can say that right now everything on Deb11 (including myVesta) is just for testing.
What we did here is that we just adapted myVesta for Deb11, so myVesta will be ready when Deb11 goes officially.
Soon or later we should adapt myVesta for Deb11, so we just did it now... better now than later
![Very Happy :D](./images/smilies/icon_e_biggrin.gif)
Thanks!, i found this tutorial to upgrade Debian10 to Debian11.
https://www.how2shout.com/linux/how-to- ... eye-linux/
If someone have another better one please post it here, so i dont have to reinstall all the accounts again or do a backup and be forced to reinstall all from zero again.
https://www.how2shout.com/linux/how-to- ... eye-linux/
If someone have another better one please post it here, so i dont have to reinstall all the accounts again or do a backup and be forced to reinstall all from zero again.
- myVesta
- Site Admin
- Posts: 932
- Joined: Fri Jun 19, 2020 9:59 am
- Has thanked: 8 times
- Been thanked: 6 times
Don't do that until we write walkthrough for upgrade from deb10 to deb11.
Deb11 is not released yet, anyway.
Exim need total new config, ProFTPd needs one little change in config file, and you need to tell Debian to keep using sha512 for /etc/shadow
Deb11 is not released yet, anyway.
Exim need total new config, ProFTPd needs one little change in config file, and you need to tell Debian to keep using sha512 for /etc/shadow
- myVesta
- Site Admin
- Posts: 932
- Joined: Fri Jun 19, 2020 9:59 am
- Has thanked: 8 times
- Been thanked: 6 times
Deb10 will receive updates until 2024, so really no need to hurry up with upgrade.
I will personally leave Deb10 on my servers until 2024, for sure.
(plus, there is Extended LTS for minimum 2 additional years, so, practically, you will be covered with security updates until 2026)
check out https://wiki.debian.org/LTS
---
extended LTS - https://deb.freexian.com/extended-lts/
right now Debian8 is still covered with security updates, totally for free.
(big companies are paying for updates, but anyway, apt repo is totally public and free for everyone, so every server can get those updates for free)
I will personally leave Deb10 on my servers until 2024, for sure.
(plus, there is Extended LTS for minimum 2 additional years, so, practically, you will be covered with security updates until 2026)
check out https://wiki.debian.org/LTS
---
extended LTS - https://deb.freexian.com/extended-lts/
right now Debian8 is still covered with security updates, totally for free.
(big companies are paying for updates, but anyway, apt repo is totally public and free for everyone, so every server can get those updates for free)
How is the progress with exim?
I've tried to print-out dkim-dns and failed (Adding/listing scripts failed to execute):
root@mail:/usr/local/vesta/bin# /usr/local/vesta/bin/v-add-mail-domain-dkim admin mydomain.com
/usr/local/vesta/bin/v-add-mail-domain-dkim: line 19: /func/main.sh: No such file or directory
/usr/local/vesta/bin/v-add-mail-domain-dkim: line 20: /func/domain.sh: No such file or directory
/usr/local/vesta/bin/v-add-mail-domain-dkim: line 21: /conf/vesta.conf: No such file or directory
etc...
I had to add "VESTA=/usr/local/vesta" to the beginning to each script
I've tried to print-out dkim-dns and failed (Adding/listing scripts failed to execute):
root@mail:/usr/local/vesta/bin# /usr/local/vesta/bin/v-add-mail-domain-dkim admin mydomain.com
/usr/local/vesta/bin/v-add-mail-domain-dkim: line 19: /func/main.sh: No such file or directory
/usr/local/vesta/bin/v-add-mail-domain-dkim: line 20: /func/domain.sh: No such file or directory
/usr/local/vesta/bin/v-add-mail-domain-dkim: line 21: /conf/vesta.conf: No such file or directory
etc...
I had to add "VESTA=/usr/local/vesta" to the beginning to each script
- myVesta
- Site Admin
- Posts: 932
- Joined: Fri Jun 19, 2020 9:59 am
- Has thanked: 8 times
- Been thanked: 6 times
Looks like viewtopic.php?f=17&t=49tna wrote: ↑Mon Aug 16, 2021 6:05 am root@mail:/usr/local/vesta/bin# /usr/local/vesta/bin/v-add-mail-domain-dkim admin mydomain.com
/usr/local/vesta/bin/v-add-mail-domain-dkim: line 19: /func/main.sh: No such file or directory
/usr/local/vesta/bin/v-add-mail-domain-dkim: line 20: /func/domain.sh: No such file or directory
/usr/local/vesta/bin/v-add-mail-domain-dkim: line 21: /conf/vesta.conf: No such file or directory
But anyway, Exim is a daemon where I can expect problems because we were forced to put very modified conf file due to Exim version 4.94+
https://github.com/myvesta/vesta/commit ... 143c43d81f