We’ve compiled a second release candidate of version 1.2.0, which should resolve the previous issues that some users faced during the upgrade process. If no issues are found with this build over the weekend, we will release it to production on Monday, July 6, 2020.
wget https://raw.githubusercontent.com/hestiacp/hestiacp/master/install/hst-install-ubuntu.sh
wget https://apt.hestiacp.com/beta/hestia_1.2.0_amd64.deb
indent preformatted text by 4 spaces
bash ./hst-install-ubuntu.sh --with-debs /root --apache yes --nginx yes --phpfpm no --multiphp yes --vsftpd no --proftpd yes --named yes --mysql yes --postgresql no --exim yes --dovecot yes --clamav no --spamassassin no --iptables no --fail2ban no --quota yes --api yes --lang en --hostname hotnamehere --email emailhere --password password --force yes
_ _ _ _ ____ ____
| | | | ___ ___| |_(_) __ _ / ___| _ \
| |_| |/ _ \/ __| __| |/ _` | | | |_) |
| _ | __/\__ \ |_| | (_| | |___| __/
|_| |_|\___||___/\__|_|\__,_|\____|_|
Hestia Control Panel
v1.2.0
====================================================================
The following components will be installed on your server:
- NGINX Web / Proxy Server
- Apache Web Server (as backend)
- Multi-PHP Environment
- Bind DNS Server
- Exim Mail Server
- Dovecot POP3/IMAP Server
- MariaDB Database Server
- ProFTPD FTP Server
====================================================================
Would you like to continue with the installation? [Y/N]: Y
Installation backup directory: /root/hst_install_backups/030720200317
Installation log file: /root/hst_install_backups/hst_install-030720200317.log
Adding required repositories to proceed with installation:
(*) NGINX
(*) PHP
(*) Apache2
(*) MariaDB
(*) Hestia Control Panel
Updating currently installed packages, please wait...-
Now installing Hestia Control Panel and all required dependencies.
NOTE: This process may take 10 to 15 minutes to complete, please wait... \
Error: apt-get install failed
root@la-s1:~#
@Amadex, in this case it’s a configuration file error (the version was initially set to be 1.1.2 early in the development process). You can run nano $HESTIA/conf/hestia.conf and change the VERSION variable to 1.1.1 so that it aligns correctly with the package version.