Testing Ubuntu 20.04

eris · June 5, 2020, 4:02pm

mofoster · June 7, 2020, 11:33am

Any ETA on when will the new packge be release that’s fully support 20.04?

Cheers

eris · June 7, 2020, 11:34am

No, not yet… We are currently testing all the features and improvements

dao · June 8, 2020, 1:20pm

So it was installed without problems. Everything that I tried on the test server (Ryzen 3950x 128G) so far works without errors (web, DB, DNS, Mail). Perhaps a release soon?

Lupu · June 8, 2020, 2:34pm

Good to hear this @dao , our tests also are succesful.
I could not reproduce @merotorg issue with iptables paths, but i’ve tested only on clean ubuntu install

merotorg · June 10, 2020, 9:39am

Maybe, this bug was already fixed…
Is there any known bugs left for 20.20?

Raphael · June 10, 2020, 9:50am

For 20.04, there is currently no known bug left (that wouldnt be in our github issue list).

eris · June 10, 2020, 9:54am

Did a upgrade last night from 18.04 to 20.04 but I had some issues

root@cp:/sbin# ln -s /usr/sbin/iptables /sbin/iptables
root@cp:/sbin# ln -s /usr/sbin/iptables-save /sbin/iptables-save
root@cp:/sbin# ln -s /usr/sbin/iptables-restore /sbin/iptables-restore

Solved my errors please check which -a iptables-save

merotorg · June 10, 2020, 10:16am

Yes, I upgraded from 18.04 to 20.04. How did you solved iptables problem?

which -a iptables-save

/usr/sbin/iptables-save

eris · June 10, 2020, 10:22am

ln -s /usr/sbin/iptables /sbin/iptables
ln -s /usr/sbin/iptables-save /sbin/iptables-save
ln -s /usr/sbin/iptables-restore /sbin/iptables-restore

It will create a symbolic link from /sbin/ to /usr/sbin for iptables, save and restore

merotorg · June 10, 2020, 10:55am

Yes, made links and now IPtables is not greyed out.
I can stop and start it, but restart fails with error message
““Restart” “” failed”

eris · June 10, 2020, 11:11am

Run via command

Try to run the command from command line

v-restart-service iptables

To check the output

I have currently no issues with it

merotorg · June 10, 2020, 11:20am

Blockquote

v-restart-service iptables

/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 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.

Blockquote

eris · June 10, 2020, 11:32am

Please check if /usr/lib/networkd-dispatcher/routable.d/ exists

merotorg · June 10, 2020, 11:53am

Checked it does not exist.

test -d “/usr/lib/networkd-dispatcher/routable.d/” && echo “exist” || echo “Nope”

Nope

eris · June 10, 2020, 12:28pm

Create that folder as root It should work…

merotorg · June 10, 2020, 12:32pm

Yes, now it works - no errors!

temposuender · June 10, 2020, 3:36pm

Any plans or timeline to update the main script?

https://raw.githubusercontent.com/hestiacp/hestiacp/release/install/hst-install.sh
is not supportiong Ubuntu 20.04

https://raw.githubusercontent.com/hestiacp/hestiacp/master/install/hst-install-ubuntu.sh
seems borked now as well (that worked a few weeks ago,.

Installation Aborted

Install script does not match Hestia release version
Please use the installer from the release branch

To test the beta version you need to build the hestia deb packages and re-run the installer
./hst_autocompile.sh --hestia no
./hst-install.sh … --with-debs /tmp/hestiacp-src/debs

Raphael · June 10, 2020, 3:53pm

Hmm, does not look broken to me at all…

ronald · June 15, 2020, 4:38pm

I’ve just installed hestia from built deb packages on a netcup VPS with minimal Ubuntu 20.04. The installation succeded. I just got an email with subject: “OpenSSH restart failed”, but the SSH server was still available.

I even was able to restore an old vesta cp backup on the server including a wordpress site which was working perfectly.