Recent reports (June/July 2025) confirm this is happening to many users globally, especially with MariaDB 11.x repos for Ubuntu/Debian
Link provided is a 2024 post… I just installed a new server last week with no repo issues.
I was getting the same error yesterday. i’ll reinstall the VM and try again
Dear @alber , I just test this on couple local VMs (Debian 12 & Ubuntu 24.04), not issues at all installing Hestia 1.9.4… MariaDB source at /etc/apt/sources.list.d/mariadb.list used still default: https://dlm.mariadb.com/repo/mariadb-server/11.4/repo for both, Ubuntu and Debian… Pls check yours 
Thank you for downloading Hestia Control Panel! In a few moments,
we will begin installing the following components on your server:
- NGINX Web / Proxy Server
- Multi-PHP Environment: Version php7.4 php8.3 php8.4
- Bind DNS Server
- Exim Mail Server + SpamAssassin
- Dovecot POP3/IMAP Server+ Sieve
- MariaDB Database Server
- ProFTPD FTP Server
- Web terminal
- Firewall (iptables)
========================================================================
Would you like to continue with the installation? [y/N]: y
Installation backup directory: /root/hst_install_backups/230720251940
Installation log file: /root/hst_install_backups/hst_install-230720251940.log
Adding required repositories to proceed with installation:
[ * ] NGINX
[ * ] PHP
[ * ] MariaDB 11.4
[ * ] Hestia Control Panel
[ * ] Node.js 20
Scanning processes…
Scanning linux images…
Updating currently installed packages, please wait… E: Failed to fetch https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu/dists/noble/InRelease 403 Forbidden [IP: 2607:f8b0:4004:c23::cf 443]
E: The repository ‘https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu noble InRelease’ is not signed.
The installer is now downloading and installing all required packages.
NOTE: This process may take 10 to 15 minutes to complete, please wait…
1 Like
Before installing Hestia, force apt to use IPv4:
echo 'Acquire::ForceIPv4 "true";' | sudo tee /etc/apt/apt.conf.d/99force-ipv4
3 Likes
Well, @sahsanu answered when I was alredy writting this hahaha, so I have deleted everything, but in sum. I was thinking things of kind of blocks, Geolocation related, and already noticed IPv6 error shown… HestiaCP does not support IPv6 yet… Just in case, if @sahsanu solution given above does not work, you can try (just an option hehe), test in other server or location like free tier at Oracle let say, or even still on VM but behind a VPN, hope @sahsanu solution works… Interesting thing anyway, becaue I have installed Hestia previously on VPS at Hostinger and Contabo with IPv6 activated with no issues at all.
2 Likes
This fixes it!
3 Likes