Hestia 1.2.0 RC - WE NEED YOU!

Raphael · June 25, 2020, 5:00pm

@arktex54 Thanks for the details, the issue has been fixed here: https://github.com/hestiacp/hestiacp/commit/e6dca969aaa6d8456a81b826f5c1dba1f1ccc71c

@kpv May I ask you to create a github issue with your suggestion to adjust the match user part in sshd config? So we could track the feature request there: https://github.com/hestiacp/hestiacp/issues/new

kpv · June 25, 2020, 5:35pm

@Raphael I can open a new issue, actually I had first suggested this back in Feb-2020:

If there a usage scenario where a hestia user shouldn’t be allowed to use sftp to access his website(s), then we might have to create a new group (e.g. hestia-sftp). Otherwise the simple sshd_config snippet above would suffice.

Raphael · June 25, 2020, 5:50pm

Hi @kpv

Thanks for the information, to answer your question: no, I think there is no case that sftp have to be restricted. We currently discuss the change, not sure if we can implement it for 1.2.0, because we want to ship it on monday - if not, we we will place it on 1.2.1 .

lazyassdeveloper · June 27, 2020, 3:52am

Ouch that shiny line-through-the-middle UI looks a little dated. It’s ok.

The shortcuts listed at the bottom seem to ignore users and thus numbers are shifted -1.

Install went without a hitch on debian 10 64bit, default options, redirected from http to https given the port. Next will test without nginx.

UPDATE: crap. The installer from master branch installed 1.1.1. Let me update.

Upon installing the hestia .deb I got these:

(*) Hardening Apache2 Server Status Module...
(*) Updating Roundcube configuration...
(*) Updating exim4 configuration...
Enabling conf hestia-event.
Enabling module hestia-status.
(*) Configuring Filegator FileManager...
(*) Updating public_(s)html ownership...
/usr/local/hestia/install/upgrade/versions/latest.sh: line 117: conditional binary operator expected
/usr/local/hestia/install/upgrade/versions/latest.sh: line 117: syntax error near `/home/${user}/web/*/public_*html'
/usr/local/hestia/install/upgrade/versions/latest.sh: line 117: `    [[ ls /home/${user}/web/*/public_*html >/dev/null 2>&1 ]] || continue'
(*) Upgrading phpMyAdmin to version v5.0.2...
(*) Rebuilding domains and account for user: admin...
(*) Restarting services...

Otherwise everything seems in order, but the shortcuts thing is still eating users, links are -1.

Lupu · June 27, 2020, 4:52am

The beta package wasn’t rebuilt since yesterday, should be sorted now (latest.sh error)

jorgepala · June 28, 2020, 10:21pm

Environment:
QEMU / KVM Virtualization
Core: 2
Ram: 20Gb
SO: Debian 10.4
Hestia: v1.2.0 (APACHE + NGINX)

No problems when updating, following the indicated steps.

Errors found so far:

Backup section:
When you want to download a backup file, you do not download it, but queue a new backup.

eris · June 28, 2020, 10:45pm

Should be fixed 4 days ago

github.com

hestiacp/hestiacp/blob/master/web/download/backup/index.php

<?php
// Init
error_reporting(NULL);
ob_start();
session_start();
include($_SERVER['DOCUMENT_ROOT']."/inc/main.php");
// Check token
if ((!isset($_GET['token'])) || ($_SESSION['token'] != $_GET['token'])) {
    header('Location: /login/');
    exit();
}

$backup = $_GET['backup'];  
   
if(!file_exists('/backup/'.$backup)){
    $v_username = escapeshellarg($user);
    $backup = escapeshellarg($_GET['backup']);
    exec (HESTIA_CMD."v-schedule-user-backup-download ".$v_username." ".$backup , $output, $return_var);
    if ($return_var == 0) {
        $_SESSION['error_msg'] = __('BACKUP_DOWNLOAD_SCHEDULED');

This file has been truncated. show original

jorgepala · June 28, 2020, 11:21pm

It is effectively solved.
Thank you very much!

anon95304325 · June 29, 2020, 3:56pm

Version 1.2.0 has been released - https://forum.hestiacp.com/t/version-1-2-0-is-now-available/

For users who are running the release candidate, please run apt update && apt install --reinstall hestia to update to the final build.

wumix · July 9, 2020, 11:14pm

After upgrade to 1.2.0 hestia start and short time later mysql stops and can’t restart

Raphael · July 10, 2020, 5:26am

Please open a issue report on github, provide as much informations as pssoible and follow the template. But i don’t think this is related to the hestia 1.2.0 upgrade, there were no changes on the mariadb configuration or service.