Debian 12 "bookworm" released

Is support in the todo list? ))

No, It is allready almost finished :slight_smile:

7 Likes

That’s a very good news :slight_smile:

Will add to night beta repo for deb 12 :slight_smile:

1 Like

We have just pushed the first Beta release for Hestia 1.8.0

  • Debian 12 support
  • Improved security with TLS 1.3 for Email, Web
  • SRS Support for Exim4 allow users to send autoreplys / forward emails with the use of STMP relay!
  • Improvement for Mobile users

To install the update follow the instructions that can be found: Beta and release candidate testing | Hestia Control Panel For Debian 11 or 10 users wanting to upgrade to Debian 12. Please with upgrading as some repos that we use haven’t been updated yet! Please help testing and report any issues you have found! For translations: Projects < GlotPress (edited)

Beta and release candidate testing | Hestia Control Panel

Open-source web server control panel.

4 Likes

Hello.

I am trying to install hestiacp on a new server with Debian 12 and I get this error:

[ * ] Configuring System IP…
grep: /usr/local/hestia/data/ips/*: No such file or directory
Error: IP 51.xx.xx.xx doesn’t exist
Error: can’t create xxxxxx.xxxxxx.net domain

Can you run:

# Get primary IP
default_nic="$(ip -d -j route show | jq -r '.[] | if .dst == "default" then .dev else empty end')"
# IPv4
primary_ipv4="$(ip -4 -d -j addr show "$default_nic" | jq -r '.[].addr_info[] | if .scope == "global" then .local else empty end' | head -n1)"
ip="$primary_ipv4"

echo $ip

Also what is your provider?

1 Like

root@osiris:~# echo $ip
51.xx.xx.xx

[ * ] Configuring System IP…
grep: /usr/local/hestia/data/ips/*: No existe el fichero o el directorio
Error: IP 51.xx.xx.xx doesn’t exist
Error: can’t create xxx.xxx.xxx domain

Provider is Scaleway (Dedibox).

And here:

iface="$(ip -d -j addr show | jq --arg IP "$ip" -r '.[] | if .addr_info[].local == $IP then .ifname else empty end')"
# If that fails, detect the default interface as a fallback
if [ -z "$iface" ]; then
	iface="$(ip -d -j route show | jq -r '.[] | if .dst == "default" then .dev else empty end')"
fi
echo $iface;

I had some issues with Proxmox with the same check

root@sd-130879:~# cat iface.sh
iface=“$(ip -d -j addr show | jq --arg IP “$ip” -r ‘.[] | if .addr_info[].local == $IP then .ifname else empty end’)”
if [ -z “$iface” ]; then
iface=“$(ip -d -j route show | jq -r ‘.[] | if .dst == “default” then .dev else empty end’)”
fi
echo $iface;

root@sd-130879:~# ./iface.sh
enp1s0f0

I assume you have used an

Serverless Containers?

Do you mind giving me access to run some tests?

Feel free to DM me…

Thanks the issue was not there but in v-update-sys-ip

Fix bug in v-update-sys-ip by jaapmarcus · Pull Request #3688 · hestiacp/hestiacp · GitHub will solve the issue

2 Likes

I have done a quick install (only web).
During the install process I’ve got this error :

[ * ] Configuring system settings…
sed: can’t read /etc/systemd/timesyncd.conf: No such file or directory
Failed to enable unit: Unit file systemd-timesyncd.service does not exist.
Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service not found.

After that the ssl certificate was not created during the install, I needed to do v-add-letsencrypt-host. Strange thing is that it wasn’t working at first… But few minutes later I was able to do the command and get the certificate installed.

[ * ] Configuring system settings…
sed: can’t read /etc/systemd/timesyncd.conf: No such file or directory
Failed to enable unit: Unit file systemd-timesyncd.service does not exist.
Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service not found.

Is a know issue … Couldn’t find a fix for it

After that the ssl certificate was not created during the install, I needed to do v-add-letsencrypt-host. Strange thing is that it wasn’t working at first… But few minutes later I was able to do the command and get the certificate installed.

It should be generated during the boot but maybe DNS was not working properly

I will take a look at timesyncd, this is something new in deb12…
I never used it before…

Same here it looks like it has been replaced by ntpsec …

13:03]Jaap Marcus: It looks lilke the have replaced ntp with ntpsec
https://docs.ntpsec.org/latest/quick.html
According the docs:
pool 0.pool.ntp.org
pool 1.pool.ntp.org
pool 2.pool.ntp.org
pool 3.pool.ntp.org

in /etc/ntpsec/ntp.conf should work but ntpdate restults in nothing
[14:06]Jaap Marcus:
root@test:/etc/ntpsec# ntpdig -dc 2.debian.pool.ntp.org
ntpdig: querying 2a01:4f8:191:946a::2 (2.debian.pool.ntp.org)
ntpdig: querying 2a09:e1c1:efc1:1337::123 (2.debian.pool.ntp.org)
ntpdig: querying 2003:a:87f:c37c::7 (2.debian.pool.ntp.org)
ntpdig: querying 2001:638:504:2000::34 (2.debian.pool.ntp.org)
ntpdig: querying 162.159.200.1 (2.debian.pool.ntp.org)
ntpdig: querying 142.132.210.78 (2.debian.pool.ntp.org)
ntpdig: querying 81.7.16.52 (2.debian.pool.ntp.org)
ntpdig: querying 46.4.54.78 (2.debian.pool.ntp.org)
ntpdig: querying ::1 (localhost)
ntpdig: querying 127.0.0.1 (localhost)
org t1: e8317b6a.cf35f800 rec t2: e8317b6a.cf427af1
xmt t3: e8317b6a.cf427d1f dst t4: e8317b6a.cf442000
org t1: 1686568170.809417 rec t2: 1686568170.809608
xmt t3: 1686568170.809608 dst t4: 1686568170.809633
rec-org t21: 0.000191  xmt-dst t34: -0.000025
2023-06-12 13:09:30.809608 (+0200) +0.000083 +/- 0.000108 2.debian.pool.ntp.org 2a01:4f8:191:946a::2 s2 no-leap

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.