Ubuntu 20.04 with hestiacp 1.4.0

I’ve tried to instal the new alpha 1.4.0 on my test server with Ubuntu 20.04. When I installed the package, the files were installed, but the installation script didn’t run.

root@:~# dpkg -i hestia_1.4.0~alpha_amd64.deb
Selecting previously unselected package hestia.
(Reading database … 108974 files and directories currently installed.)
Preparing to unpack hestia_1.4.0~alpha_amd64.deb …
Unpacking hestia (1.4.0~alpha) …
Setting up hestia (1.4.0~alpha) …
root@:~#

When I had a look in the folder /usr/local/hestia/install, I recognized the install script was missing the executable bit.

root@:/usr/local/hestia/install# ls -la
total 160
drwxrwxr-x 5 root root 4096 Mar 4 20:21 .
drwxr-xr-x 6 root root 4096 Mar 4 20:21 …
drwxrwxr-x 28 root root 4096 Mar 4 20:21 deb
-rwxrwxr-x 1 root root 67592 Feb 28 12:18 hst-install-debian.sh
-rw-rw-r-- 1 root root 3070 Feb 28 12:18 hst-install.sh
-rwxrwxr-x 1 root root 68870 Feb 28 12:18 hst-install-ubuntu.sh
drwxrwxr-x 26 root root 4096 Mar 4 20:21 rhel
drwxrwxr-x 4 root root 4096 Mar 4 20:21 upgrade

After I’ve set the executable bit, I was able to run the installation script manually.

How did you install it?

Over a 1.3.3 install?

No, installed it on a clean server.

It will not work do the following:

Go to hestiacp/install at main · hestiacp/hestiacp · GitHub

Download the installer you need (Debian or Ubuntu)

Download the package.

bash hst-install-{os}.sh --with-debs /path_packages/

Where {os} is your OS.

https://docs.hestiacp.com/development/panel.html#install-hestia-from-packages

1 Like

Sorry, I forgot the procedure for a clean install of a beta version. Now it worked. Thank you.

I’ve restored a backup from a hestiacp 1.3.3 server and got the following messeges during restore:

– MAIL –
2021-03-04 21:44:02 xxxxxxxxxxxxxxxxxx
Error: WEBMAIL_ALIAS is not defined in hestia.conf.
Usage: grep [OPTION]… PATTERNS [FILE]…
Try ‘grep --help’ for more information.
Error: type is invalid
Usage: grep [OPTION]… PATTERNS [FILE]…
Try ‘grep --help’ for more information.
Error: type is invalid

When I edit a mail account, the “Webmail Alias” is not shown correctly. On the old server it was http://webmail.domain. Now it is http://.domain .

Let me check it.

Thank you for reporting following pull request should fix your issues + a few more

I’ve updated hestia using:

v-update-sys-hestia-git hestiacp fix/2021-03-install-issues install

The webmail-Alias is now created correctly.

During the update of hestia I’ve got the following errors when processing the user, where the backup has shown the errors before:

[ * ] Rebuilding user accounts and domains:
- admin:
---- Web domains…
---- DNS zones…
---- Mail domains…
---- User configuration…
- xxxxxxxx:
---- Web domains…
---- DNS zones…
---- Mail domains…
Usage: grep [OPTION]… PATTERNS [FILE]…
Try ‘grep --help’ for more information.
Error: type is invalid
Usage: grep [OPTION]… PATTERNS [FILE]…
Try ‘grep --help’ for more information.
Error: type is invalid
---- User configuration…
Usage: grep [OPTION]… PATTERNS [FILE]…
Try ‘grep --help’ for more information.
Error: type is invalid
Usage: grep [OPTION]… PATTERNS [FILE]…
Try ‘grep --help’ for more information.
Error: type is invalid
[ * ] Applying user interface updates…

When I delete the user and reimport the backup, the WEBMAIL_ALIAS error isn’t shown any more, but the grep errors are still shown:

– MAIL –
2021-03-06 20:39:47 prangerschuetzen-ebenau.at
Usage: grep [OPTION]… PATTERNS [FILE]…
Try ‘grep --help’ for more information.
Error: type is invalid
Usage: grep [OPTION]… PATTERNS [FILE]…
Try ‘grep --help’ for more information.
Error: type is invalid

Can you post /usr/local/hestia/conf/hestia.conf?

There was an bug in the installer. And there for Roundcube was not installed run

v-add-sys-roundcube

Also run
v-add-web-templates
v-add-mail-templates
v-add-dns-templates

Thank you. After running v-add-sys-roundcube and v-update-web-templates, v-update-mail-templates and v-update-dns-templates the error has gone. I even can import the backup without any problems.

This is my hestia.conf:

WEB_SYSTEM='apache2'
WEB_RGROUPS='www-data'
WEB_PORT='8080'
WEB_SSL_PORT='8443'
WEB_SYSTEM='apache2'
WEB_RGROUPS='www-data'
WEB_PORT='8080'
WEB_SSL_PORT='8443'
WEB_SYSTEM='apache2'
WEB_RGROUPS='www-data'
WEB_PORT='8080'
WEB_SSL_PORT='8443'
WEB_SSL='mod_ssl'
PROXY_SYSTEM='nginx'
PROXY_PORT='80'
PROXY_SSL_PORT='443'
STATS_SYSTEM='awstats'
WEB_BACKEND='php-fpm'
DB_SYSTEM='mysql'
FTP_SYSTEM='vsftpd'
DNS_SYSTEM='bind9'
MAIL_SYSTEM='exim4'
ANTIVIRUS_SYSTEM='clamav-daemon'
ANTISPAM_SYSTEM='spamassassin'
IMAP_SYSTEM='dovecot'
CRON_SYSTEM='cron'
FIREWALL_SYSTEM='iptables'
FIREWALL_EXTENSION='fail2ban'
DISK_QUOTA='no'
BACKUP_SYSTEM='local'
BACKUP_GZIP='4'
BACKUP_MODE='zstd'
LANGUAGE='en'
LOGIN_STYLE='default'
INACTIVE_SESSION_TIMEOUT='60'
RELEASE_BRANCH='fix/2021-03-install-issues'
UPGRADE_SEND_EMAIL='true'
UPGRADE_SEND_EMAIL_LOG='true'
DB_PMA_ALIAS='phpmyadmin'
API='yes'
BACKEND_PORT='8083'
THEME='dark'
FILE_MANAGER='true'
WEBMAIL_ALIAS='webmail'
WEBMAIL_SYSTEM=''
VERSION='1.4.0~alpha'

Had the same trouble as OP and thought it was funny the app first prompts to uninstall itself before proceeding with the install lol. In any case, i followed the install instructions for “–with-debs” installation and noticed that the was also still an error with the roundcube installation during the hestia installation. Something about unknown path. The installation proceeded but I went to run the “v-add-” for roundcube and the 3 templates that are marked as solution but I can’t find them anywhere?!?

As noted in my previous post, I had to run the three scripts v-update-web-templates, v-update-mail-templates and v-update-dns-templates, not the three scripts mentioned in eris’ post, which started with “v-add-”.

We will release a new test version soon. The old install script has some bugs that are fixed in the new version

You can also build the packages yourself:
https://docs.hestiacp.com/development/panel.html#install-hestia-from-packages

can you make the firewall ban list page in tabs like 20-30-40-50 …

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