Hestia 1.10.0-rc1 problem

[jekasumy]

Would you like to continue with the installation? [y/N]: y
Installation backup directory: /root/hst_install_backups/140820260831
Installation log file: /root/hst_install_backups/hst_install-140820260831.log

Adding required repositories to proceed with installation:

[ * ] NGINX
[ * ] PHP
[ * ] Apache2
[ * ] MariaDB 11.8
[ * ] Hestia Control Panel
[ * ] Node.js 24

Updating currently installed packages, please wait… W: OpenPGP signature verification failed: https://apt.hestiacp.com trixie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Error: Failed to parse keyring “/usr/share/keyrings/hestia-keyring.gpg” Caused by: 0: Reading “/usr/share/keyrings/hestia-keyring.gpg”: EOF 1: EOF

E: The repository ‘https://apt.hestiacp.com trixie InRelease’ is not signed.

The installer is now downloading and installing all required packages.
NOTE: This process may take 10 to 15 minutes to complete, please wait…
E: Unable to locate package hestia
E: Unable to locate package hestia-nginx
E: Unable to locate package hestia-php
E: Unable to locate package hestia-web-terminal

========================================================================

[ * ] Configuring system settings…
cp: cannot stat ‘/usr/local/hestia/install/deb/logrotate/httpd-prerotate/': No such file or directory
[ * ] Configuring Hestia Control Panel…
cp: cannot stat ‘/usr/local/hestia/install/common/sudo/hestiaweb’: No such file or directory
chmod: cannot access ‘/etc/sudoers.d/hestiaweb’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/logrotate/hestia’: No such file or directory
ln: failed to create symbolic link ‘/usr/local/hestia/log’: No such file or directory
touch: cannot touch ‘/usr/local/hestia/log/system.log’: No such file or directory
touch: cannot touch ‘/usr/local/hestia/log/nginx-error.log’: No such file or directory
touch: cannot touch ‘/usr/local/hestia/log/auth.log’: No such file or directory
touch: cannot touch ‘/usr/local/hestia/log/backup.log’: No such file or directory
chmod: cannot access ‘/usr/local/hestia/log’: No such file or directory
chmod: cannot access '/var/log/hestia/’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/common/packages’: No such file or directory
sed: can’t read /usr/local/hestia/data/packages/.pkg: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/templates’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/common/templates/web/’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/common/templates/dns/’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/common/templates/web/unassigned/index.html’: No such file or directory
cp: cannot stat '/usr/local/hestia/install/common/templates/web/skel/document_errors/': No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/common/firewall’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/common/api’: No such file or directory
[ * ] Configuring OpenSSL to improve TLS performance…
[ * ] Generating default self-signed SSL certificate…
hst-install-debian.sh: line 1531: /usr/local/hestia/bin/v-generate-ssl-cert: No such file or directory
Error: failed to parse generated SSL certificate

The problem persists. I’m doing a clean install again. I’m installing version 1.10.1.
I’m installing on Hetzher Cloud. The server is cx23. The system is Debian 13 without IPv6.

@eris @sahsanu

[jekasumy]

I solved the problem this way: curl -s “https://apt.hestiacp.com/pubkey.gpg” | gpg --dearmor | tee /usr/share/keyrings/hestia-keyring.gpg > /dev/null 2>&1

But that’s not right…

First, I load the key manually, and then I start installing the panel on a clean system.

[eris]

We will release 1.10.2 sortly and will do the same thing …

[jekasumy]

Okay, thanks. I’ll wait for the new version, then I’ll update all the production servers.
I’m currently testing it on the test server. There might be some other issues.

[jekasumy]

Is it possible to increase the size of the downloaded file through the file manager? For example, up to 100 gigabytes?

[sahsanu]

@jekasumy

Is it possible to increase the size of the downloaded file through the file manager?

is too large, please upload files less than 1gb

You should login to your server via ssh, switch to user root and modify this file: /usr/local/hestia/web/fm/configuration.php Replacing this: $dist_config["frontend_config"]["upload_max_size"] = 1024 * 1024 * 1024; By this (it will raise the file size limit to 2GB): $dist_config["frontend_config"]["upload_max_size"] = 2 * 1024 * 1024 * 1024;

[jekasumy]

Yes, thanks, I know that. But it wouldn’t be bad to implement it in the panel by default.

[jekasumy]

After updating to the latest version, sso does not work

ERR_TOO_MANY_REDIRECTS

What to do?

@sahsanu @eris

[sahsanu]

I can’t reproduce it, it works fine on my server. Try disabling and enabling SSO

[jekasumy]

v-delete-sys-pma-sso

Error: PMA Single Sign On already disabled
v-add-sys-pma-sso
Error: SSO has been installed before to reenable it please run v-delete-sys-pma-sso first

v-delete-sys-pma-sso
Error: PMA Single Sign On already disabled

[sahsanu]

I can’t also reproduce it.

Did you use a remote DB?

Show the output of:

bash -x v-add-sys-pma-sso

[Raphael]

I dont think you should upload such big files ober the filemanager, there are other protocols which are more stable.

[jekasumy]

Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://deb.nodesource.com/node_20.x nodistro InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound: No binding signature at time 2026-04-30T12:44:55Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
Warning: Failed to get https://deb.nodesource.com/node_20.x/dists/nodistro/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound: No binding signature at time 2026-04-30T12:44:55Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
Warning: Some index files could not be downloaded. They were ignored, or older versions were used instead.

If you have this problem after upgrading to Debian 13, run the following command:

sudo curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /usr/share/keyrings/nodesource.gpg