Release data for version Ver 1.1

On Debian 10 you need to run apt install util-linux as proposed.

About disabling exim and/or bind, please checkout the additional installation commands: https://github.com/hestiacp/hestiacp/blob/master/README.md#custom-installation

Hi @Raphael , yes i know i can avoid to install BIND but it would be nice if i can install it and then play with it by disabling also, not only pausing. It’s just a small thing, but it could be handy :slight_smile:

Anyway, it’s working well like it is now, don’t get me wrong.

Cheers

@Ubi I didnt got you wrong, maybe I wrote a bit to directly :smiley:. Currently, we do not plan to implement such a function, but a idea is to make hestia more “modular” like we did it in php already. So you can add and remove features like bind if you (don’t) need them. Thanks for testing, let us know if you find anything else that doesnt work properly.

Have installed 1.1 a few more times and all went OK,

I did notice a fresh install without upgrade takes longer now > 30-40min. on Deb 9 and Deb 10 ( both using local mirrors for OS)

Installed with apache, nginx, multiphp, clamav, spamassassin both at different providers being Linode and one here in New Zealand. Both 1 core vps.and perform well just install takes longer than usual.

Benchmark - Linode (Sydney, Australia DC)
CPU Name: AMD EPYC 7601 32-Core Processor
OS Name: Debian GNU/Linux 9 (stretch)
Virtualization: qemu
Kernel: Linux 4.9.0-11-amd64
CPU Cores: 1
CPU (Mhz): 2200
BogoMIPS (Mhz): 4400
MEMORY (GB): 2.0
HDD (GB): 49
IO READ cache (MB/sec): 587.121
IO READ (MB/sec): 604.878
IO WRITE (MB/sec): 388.715
CPU TEST GZIP (sec): 28.549
CPU TEST BZIP2 (sec): 28.575
CPU TEST SHA1SUM (sec): 25.418
CPU TEST SHA256SUM (sec): 28.195
CPU TEST MD5SUM (sec): 22.492
PING (ms) EU: 290.891
PING (ms) North America: 226.744
PING (ms) South America: 326.436
PING (ms) China: 237.009
PING (ms) Australia: 1.213

Benchmark - Auckland New Zealand
VPS cost here is very expensive > $30NZD with 20GB International B/W and unmetered within NZ, bandwidth is not a problem as target is NZ market.

CPU Name: AMD EPYC 7302 16-Core Processor
OS Name: Debian GNU/Linux 10 (buster)
Virtualization: xen
Kernel: Linux 4.19.0-8-amd64
CPU Cores: 1
CPU (Mhz): 3000
BogoMIPS (Mhz): 6000
MEMORY (GB): 1.5
HDD (GB): 15
IO READ cache (MB/sec): 399.485
IO READ (MB/sec): 350.085
IO WRITE (MB/sec): 292.315
CPU TEST GZIP (sec): 42.804
CPU TEST BZIP2 (sec): 24.261
CPU TEST SHA1SUM (sec): 67.775
CPU TEST SHA256SUM (sec): 70.552
CPU TEST MD5SUM (sec): 68.043
PING (ms) EU: 272.337
PING (ms) North America: 188.899
PING (ms) South America: 301.613
PING (ms) China: 320.764
PING (ms) Australia: 34.570

DCC, Pyzor, Razor integrated with SpamAssassin
Brotli installed as dynamic module - set to update if/when Nginx updates.
Dovecot sieve installed and custom sieve rules added.
Updated to be PCI complient with current standards,
Webp and ImageMagick installed from source

Just tested another install with Linode but in the USA at Fremont DC, installed in 9 - 10 minutes.

So possibly what the installer downloads when around here causes the extra time if in a country in the middle of nowhere :slight_smile:

Selecting previously unselected package hestia.
(Reading database … 89037 files and directories currently installed.)
Preparing to unpack …/debs//hestia_1.1.0_amd64.deb …
Unpacking hestia (1.1.0) …
Setting up hestia (1.1.0) …

Hello i installed hours ago hestia 1.1.0 in debian 10 using this steps

############################################################
# Clean install Hestia from latest master or local changes #
############################################################
SRCDIR='/home/debian'

cd $SRCDIR
git clone https://github.com/hestiacp/hestiacp.git
cd hestiacp

# After we are done editing we build hestia deb packages (dst dir: /tmp/hestiacp-src/debs/)
sudo $SRCDIR/hestiacp/src/hst_autocompile.sh --hestia "~localsrc" no

# And now we will install Hestia with our freshly compiled debs instead of the ones from the official repo
# - This flag "--with-debs" will instruct the installer where look for Hestia packages
sudo su -
/home/debian/hestiacp/install/hst-install-debian.sh --with-debs /tmp/hestiacp-src/debs/ --force --apache yes --nginx yes --multiphp yes

Eveything is running without issues and i will start using it in production, so now my question is this “testing” installation cannot receive automatic updates? (updating from hestia panel or cron).
If not, what i have to do in case a new update is released to apply it in my installation?

1 Like

Infact you’re “already” on 1.1.0, you will not get a update after the release. You could simply repeate the deb installation or run apt install --reinstall hestia to get the latest version (do it only AFTER the release of 1.1.0).

If there is a hotfix release (for example 1.1.1), you will get it over autoupdate.

1 Like

Hi again,

I’m still playing with DEBIAN 10 / HST 1.1.0 and i found something i’m not sure how to handle.
I’ve set a couple of cronjobs from HST and are working fine. The only issue i get is about CRON notifications. Seems are running not with the cron user i set in HST because i get this mail notification every time cron is triggered :

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.

sudo: no tty present and no askpass program specified

So i tried to turn off cron notification from HST and all the emails now are marked as frozen and still in exim mail queue.

My question is : Is it normal that crons send everytime the above notification? If yes, it sounds as permission problem.

Secondly, can HST avoid to keep frozen messages in EXIM queue and force to delete it manually?

Thank you again for your super work and sorry if i miss something. I’m not reading all the forum topics :slight_smile:

Cheers

Any ETA time to release 1.1.0 official version?.
I need install new hestiacp waiting for 1.1.0 official release.

Within a few days, we finish the last testing steps for Debian on our side, Ubuntu seems to working properly.

@Ubi, please open a new thread, this is not related to the upgrade procedure or the new version of hestia.

I found the issue with slow install time today in my post above, I did not setup the resolv.conf with external ip’s and used providers resolvers so install again today was under 15-20min using public DNS servers

So before install must remember to check resolv.conf and set to something like Google public DNS 8.8.8.8 and 8.8.4.4 or Cloudflare public DNS 1.1.1.1 and 1.0.0.1 :+1:

DNS usualy doesnt take seconds or minutes to lookup a record. Sounds like your provider seems to have a issue or points you to different servers, both things are a bit weird :smiley:. Thanks for keeping us up to date!

12 posts were split to a new topic: Changes to php settings via GUI not applied to php.ini

Hi,

Question this is only for update 1.0.6 or i can install from scrach 1.1.0

wget https://apt.hestiacp.com/beta/hestia_1.1.0_amd64.deb
dpkg -i hestia_1.1.0_amd64.deb
apt install -f

Error installing Hestia 1.0.6 on Ubuntu 18.04

Welcome to the Hestia Control Panel installer!

Please wait a moment while we update your system’s repositories and
install any necessary dependencies required to proceed with the installation…

!!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!!

WARNING: The following packages are already installed
ufw* hestia*

It is highly recommended that you remove them before proceeding.

!!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!!

Would you like to remove the conflicting packages? [y/n] y
E: Unable to locate package hestia_1.1.0_amd64.deb
E: Couldn’t find any package by glob ‘hestia_1.1.0_amd64.deb’
E: Couldn’t find any package by regex ‘hestia_1.1.0_amd64.deb’
Error: apt-get remove failed
root@vmi314606:~#

@mmgnservices for new installs, please have a look here: https://github.com/hestiacp/hestiacp/issues/568#issuecomment-521086717

Hi guys,
any chanche you release v. 1.1.0 this weekend?
Thanks

no, we currently prepare the docs due to importantly needed informations for migration steps. The release should be around next week.

3 Likes

5 posts were split to a new topic: Some Bugs after Upgrade to 1.1.0