Please use the following instructions
wget https://raw.githubusercontent.com/hestiacp/hestiacp/master/install/hst-install-ubuntu.sh
bash hst-install-ubuntu.sh
Please use the following instructions
wget https://raw.githubusercontent.com/hestiacp/hestiacp/master/install/hst-install-ubuntu.sh
bash hst-install-ubuntu.sh
Clean bare metall server which was upgraded from 18.04 to 20.04 Ubuntu.
Run the following commands:
1)
bash ./hst_autocompile.sh --all master no
bash hst-install-ubuntu.sh --apache no --nginx yes --phpfpm yes --multiphp no --vsftpd no --proftpd no --named no --mysql yes --postgresql no --exim yes --dovecot no --clamav no --spamassassin no --iptables yes --fail2ban yes --quota yes --api no --lang en --hostname myhostname --email [email protected] --port 8045 --force --with-debs /tmp/hestiacp-src/debs
Got the output:
The following server components will be installed on your system:
====================================================================
Would you like to continue with the installation? [Y/N]: y
Installation backup directory: /root/hst_install_backups/220520202258
Installation log file: /root/hst_install_backups/hst_install-220520202258.log
Adding required repositories to proceed with installation:
() NGINX
() PHP
() MariaDB
() Hestia Control Panel
Updating currently installed packages, please wait…-
mkdir: cannot create directory ‘nginx’: File exists
mkdir: cannot create directory ‘apache2’: File exists
mkdir: cannot create directory ‘php’: File exists
mkdir: cannot create directory ‘vsftpd’: File exists
mkdir: cannot create directory ‘proftpd’: File exists
mkdir: cannot create directory ‘bind’: File exists
mkdir: cannot create directory ‘exim4’: File exists
mkdir: cannot create directory ‘dovecot’: File exists
mkdir: cannot create directory ‘clamd’: File exists
mkdir: cannot create directory ‘spamassassin’: File exists
mkdir: cannot create directory ‘mysql’: File exists
mkdir: cannot create directory ‘postgresql’: File exists
mkdir: cannot create directory ‘hestia’: File exists
Now installing Hestia Control Panel and all required dependencies.
NOTE: This process may take 10 to 15 minutes to complete, please wait…
Selecting previously unselected package hestia.
(Reading database … 122854 files and directories currently installed.)
Preparing to unpack …/debs/hestia_1.1.2_amd64.deb …
Unpacking hestia (1.1.2) …
Setting up hestia (1.1.2) …
() Configuring system settings…
() Configuring Hestia Control Panel…
() Generating default self-signed SSL certificate…
() Adding SSL certificate to Hestia Control Panel…
() Configuring NGINX…
() Configuring PHP-FPM…
() Configuring PHP…
() Configuring MariaDB database server…
() Installing phpMyAdmin version v5.0.2…
() Configuring Exim mail server…
(*) Configuring fail2ban access monitor…
/usr/local/hestia/bin/v-update-firewall: line 175: /sbin/iptables-save: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 180: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 181: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 182: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 183: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 184: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 185: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 186: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 187: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 188: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
chmod: cannot access ‘/usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks’: No such file or directory
/dev/md2 [/]: group quotas turned on
/dev/md2 [/]: user quotas turned on
/usr/local/hestia/bin/v-stop-firewall: line 68: /sbin/iptables-save: No such file or directory
/usr/local/hestia/bin/v-stop-firewall: line 73: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-stop-firewall: line 74: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-stop-firewall: line 75: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-stop-firewall: line 76: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-stop-firewall: line 77: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-stop-firewall: line 78: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-stop-firewall: line 79: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
chmod: cannot access ‘/usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks’: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 175: /sbin/iptables-save: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 180: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 181: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 182: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 183: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 184: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 185: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 186: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 187: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
/usr/local/hestia/bin/v-update-firewall: line 188: /usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks: No such file or directory
chmod: cannot access ‘/usr/lib/networkd-dispatcher/routable.d/50-ifup-hooks’: No such file or directory
Error: ERROR: Restart of iptables failed.
====================================================================
Congratulations!
You have successfully installed Hestia Control Panel on your server.
Ready to get started? Log in using the following credentials:
Seems that the file is in another place. Using find gives result:
/usr/sbin/iptables-save
/etc/alternatives/iptables-save
As a result - iptables is grayed in Server list
Overall HestiaCP is working.
Also I noticed, that PHP 7.3 version is being used instead of 7.4 which is default in Ubuntu 20.20. Is it a bug or a feature which should be changed in server configuration menu? In one config place hestia-php has 7.4.5 version (screenshot below)…
Also Fm (File Manager?) page is giving 404 error. I don’t need FM anyway…
Correct, i noticed as well after installing last night.
Just did a test run on a Digital Ocean Ubuntu 20.10 droplet. (n.b. DO needs the --force flag as it has an admin account configured). Commands run:
wget https://raw.githubusercontent.com/hestiacp/hestiacp/dde0dc69d507e658334cb16d5540af5c79f6fbc0/src/hst_autocompile.sh
wget https://raw.githubusercontent.com/hestiacp/hestiacp/master/install/hst-install-ubuntu.sh
chmod 700 *.sh
./hst_autocompile.sh --all master no # … compile time approx 20 mins.
./hst-install-ubuntu.sh --vsftpd “no” --named “no” --clamav “no”
–port “7777” --hostname “test.domain.com” --email “[email protected]”
–password “xxxxxxxxxx” --force --with-debs /tmp/hestiacp-src/debs
All seems to work. But a couple of small points.
Initial domain got bound to the internal 10.x.x.x IP address. Vesta login worked, but needed to re-bind to the public IP address before the website showed up. DO VM has two IPs configured on eth0. Perhaps it picked the first one numerically? Second one was 66.x.x.x.
Need to run v-add-letsencrypt-host immediately as previously noted. Would that be a sensible default to run on the end of the install? Always supposing the IP address resolves to the hestia box.
I didn’t install ftp or bind, so as usual I removed the firewall entries. Perhaps these firewall entries could be disabled/removed if bind/ftp aren’t installed? Not a great problem if no daemon is running on that port though.
I got an email alert “OpenSSH can not be restarted. Please check config:” after installing and rebooting, although ssh started fine.
That’s about all. Nice updated versions of roundcube, phpmyadmin etc.
Question: If I installed hestia using the compile script, will I still be able to update hestia through the normal channels afterwards. (I’m wondering whether to start to configure the server as-is, or whether to wait for the final release.)
Hi @pluto
Just haven’t enough time here to answer the other questions, but for the one above a strong “no”: This is only for testing, the servers are not planed to get in the normal productive branch, also you may miss important updates during the dev state if you do it anyway.
Also noticed, that PHPMyAdmin is not working. Instead there is 404 error.
Also it is not possible to change PHPcli version for user in GUI. It can be changed and saved, but when you go back to the user edit page - it is back to default 7.3
Just to confirm:
Change first to 7.4 of any other version and then
execute in shell as the user or root :
cat /home/admin/.bash_aliases
And check with php -v the php version?
In case 7.4 it should read 7.4.5 or something like that. I think it is a interface bug
(https://github.com/hestiacp/hestiacp/commit/7bb52d8186f71b73ee8f54b4defb96bd59fdd911 is with the fix)
Are you using
or https://hostname.nl/phpmyadmin/
The first one has been disabled for security reasons
I use http://ip/phpmyadmin.
Now I understood that this is banned for security reason. But then it should be clear stated. An information page, not 404 is definitely needed… Will make a featurerequest later…
When accessed by DNS name - PhpMyAdmin is working as expected.
It is all the time 7.4.6 even when i change to 7.3…
$ php -v
PHP 7.4.6 (cli) (built: May 14 2020 10:03:35) ( NTS )
Copyright © The PHP Group
Zend Engine v3.4.0, Copyright © Zend Technologies
with Zend OPcache v7.4.6, Copyright ©, by Zend Technologies
You should first login / logout first .bash_aliases are run when you login
Just tried over here it is working
Yes, you are right! After logout->login php version has changed. So this is a GUI problem.
Code to perfect install, i’am not using github for this:
wget https://raw.githubusercontent.com/hestiacp/hestiacp/master/install/hst-install-ubuntu.sh -O hst-install-ubuntu.sh
sed -i '1583iwget https://www.pcready.space/v-list-sys-services -O /usr/local/hestia/bin/v-list-sys-services' hst-install-ubuntu.sh
sed -i '1584ichmod +775 /usr/local/hestia/bin/v-list-sys-services' hst-install-ubuntu.sh
sed -i '1585i#' hst-install-ubuntu.sh
sed -i '1586iwget https://www.pcready.space/v-update-firewall -O /usr/local/hestia/bin/v-update-firewall' hst-install-ubuntu.sh
sed -i '1587ichmod +775 /usr/local/hestia/bin/v-update-firewall' hst-install-ubuntu.sh
sed -i '1588i#' hst-install-ubuntu.sh
sed -i 's#/release/#/master/#g' hst-install-ubuntu.sh
bash hst-install-ubuntu.sh --nginx yes --phpfpm yes --multiphp no --vsftpd no --proftpd no --named yes --mysql yes --postgresql no --exim yes --dovecot yes --clamav no --spamassassin no --iptables yes --fail2ban yes --quota no --api yes --lang es --hostname $cp_hostname --email $cp_email --password $cp_password --interactive no --force
Ubuntu 20.04 isnt released yet, if you want to test it, please use the official way over compiling the own deb packages. You can even run the installer from master, followed by a v-update-sys-hestia-git master and you would basicly get a working system.
Infact this is not the target at all - because you would also have to include the latest changes for filemanager in combination with hestia-php.
tl;dr: Just use the proposed way of installation for the testing build - Hestia deb packages
It does not work with the clean ubuntu 20.04 server…
“It does not work” isnt realy enough information to give you a proper answer - but maybe you want to share additional informations with us, just tested a fresh installation yesterday due to our mpm_event changes and all was working perfectly.
meant this instruction
installation aborted
probably the instruction is not complete
And you didnt read the information message in a bright yellow that appears and leads you to the next steps that have changed during the time since @eris posted it?