# Hestia Upgrade A lot of errors

**URL:** <https://forum.hestiacp.com/t/hestia-upgrade-a-lot-of-errors/22413>\
**Category:** Uncategorized\
**Created:** [November 3, 2026, 11:08am UTC](https://forum.hestiacp.com/t/hestia-upgrade-a-lot-of-errors/22413 "2026-11-03T11:08:39Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![surya](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/surya/32/7795_2.png) [@surya](https://forum.hestiacp.com/u/surya)\
**Post date:** [November 3, 2026, 11:08am UTC](https://forum.hestiacp.com/t/hestia-upgrade-a-lot-of-errors/22413/1 "2026-11-03T11:08:39Z")

</div>

![image](https://forum.hestiacp.com/uploads/default/original/2X/b/b008714731fc6de238da852fcf9def7343ea754e.png)

 ![image](https://forum.hestiacp.com/uploads/default/original/2X/a/ae84ebd224e086531a4b3606e7ba95ec60cd4d5d.jpeg)

I kept hestia auto update disabled as it would get untested updates and disturbed my whole server, from the experience of past releases of hestia which broke down my server various time , i kept it disabled. Everything was working fine until this week when we have to upgrade mandatorily because of PHP Vulnerability that left us no option. So I performed upgrade of my server from hestia 1.9.3 - 1.10.5 and every service looks broken from apache to mariadb. The whole server have come to halt after the upgrade.

---

<div class="post-metadata">

**Author:** ![surya](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/surya/32/7795_2.png) [@surya](https://forum.hestiacp.com/u/surya)\
**Post date:** [November 3, 2026, 11:14am UTC](https://forum.hestiacp.com/t/hestia-upgrade-a-lot-of-errors/22413/2 "2026-11-03T11:14:16Z")

</div>

![image](https://forum.hestiacp.com/uploads/default/original/2X/5/528e2e422ec133721a98f2496367b87fe64369da.png)

 ![image](https://forum.hestiacp.com/uploads/default/original/2X/3/341221822fcd3ab75b558fc45a0d6e4243a0e8d2.jpeg)

---

<div class="post-metadata">

**Author:** ![sahsanu](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/sahsanu/32/9318_2.png) [@sahsanu](https://forum.hestiacp.com/u/sahsanu)\
**Post date:** [November 3, 2026, 11:15am UTC](https://forum.hestiacp.com/t/hestia-upgrade-a-lot-of-errors/22413/3 "2026-11-03T11:15:05Z")

</div>

That’s not really an Hestia fault, I explain it in this PR:

> <https://github.com/hestiacp/hestiacp/pull/5888>
>
> On Ubuntu 22.04, Composer 2.11.x fails with \`curl error 27: Out of memory\` when …downloading files from GitHub. This is not related to actual memory usage. Composer 2.11 enables \`CURLOPT\_CERTINFO\`, and \`hestia-php\` is linked against \`libcurl-gnutls\` 7.81.0 (GnuTLS 3.7.3), which returns this error when processing GitHub's certificate chain.
> 
> The issue does not occur with newer versions of GnuTLS, as confirmed by successful tests on Debian 12, Debian 13, Ubuntu 24.04, and Ubuntu 26.04.
> 
> Building \`hestia-php\` against \`libcurl4-openssl-dev\` instead of \`libcurl4-gnutls-dev\` resolves the issue. This solution works across all OS currently supported by Hestia (Debian 12, Debian 13, Ubuntu 22.04, Ubuntu 24.04, and Ubuntu 26.04).
> 
> Fixes #5886

You can downgrade /home/admin/.composer/composer to 2.10.3 version. The other option is upgrade Ubuntu 22.04 to 24.04 that doesn’t have this issue.

---

<div class="post-metadata">

**Author:** ![surya](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/surya/32/7795_2.png) [@surya](https://forum.hestiacp.com/u/surya)\
**Post date:** [November 3, 2026, 11:27am UTC](https://forum.hestiacp.com/t/hestia-upgrade-a-lot-of-errors/22413/4 "2026-11-03T11:27:06Z")

</div>

Can access the hestiacp panel now, but the other things are still broken. Cannot access any server website or even open mails. Getting the same server success page on every website.

 ![image](https://forum.hestiacp.com/uploads/default/original/2X/0/0b6e3df29e39b4652c5bca31dd907b5c7ec9321e.png)

getting this on every domain or mail domain.

---

<div class="post-metadata">

**Author:** ![surya](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/surya/32/7795_2.png) [@surya](https://forum.hestiacp.com/u/surya)\
**Post date:** [November 3, 2026, 11:28am UTC](https://forum.hestiacp.com/t/hestia-upgrade-a-lot-of-errors/22413/5 "2026-11-03T11:28:54Z")

</div>

![image](https://forum.hestiacp.com/uploads/default/original/2X/d/dfc0c31e1f557ba9a97b9a13c30ae74875646405.png)

The websites started working after running this command. But the mails were giving below error page.

 ![image](https://forum.hestiacp.com/uploads/default/original/2X/d/d4711793c4e5557c0c1cc9887750456a5ad6697f.png)

---

<div class="post-metadata">

**Author:** ![sahsanu](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/sahsanu/32/9318_2.png) [@sahsanu](https://forum.hestiacp.com/u/sahsanu)\
**Post date:** [November 3, 2026, 11:31am UTC](https://forum.hestiacp.com/t/hestia-upgrade-a-lot-of-errors/22413/6 "2026-11-03T11:31:33Z")

</div>

Execute this and try again:

```t
mv /var/lib/roundcube/composer.json /var/lib/roundcube/composer.json.bak
mv /var/lib/roundcube/composer.lock /var/lib/roundcube/composer.lock.bak
mv /var/lib/roundcube/composer.json-dist /var/lib/roundcube/composer.json
source /usr/local/hestia/conf/hestia.conf
COMPOSER_ALLOW_SUPERUSER=1 "/usr/bin/php" "-d disable_functions=" "/home/$ROOT_USER/.composer/composer" --working-dir="/var/lib/roundcube" update --no-dev --no-interaction --optimize-autoloader

```

If that doesn’t work, I’ll be back in a couple of hours, I’m leaving now.

---

<div class="post-metadata">

**Author:** ![surya](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/surya/32/7795_2.png) [@surya](https://forum.hestiacp.com/u/surya)\
**Post date:** [November 3, 2026, 11:35am UTC](https://forum.hestiacp.com/t/hestia-upgrade-a-lot-of-errors/22413/7 "2026-11-03T11:35:47Z")

</div>

yeah sahsanu, it’s alright, you’ve been a great help throughout my journey.

Chatgpt responded with the below fix. I ran your command but that didn’t fixed it.

 ![image](https://forum.hestiacp.com/uploads/default/original/2X/0/0e31487b8ccce0edd7a99c16f7ba0e92a7f61551.png)

---

<div class="post-metadata">

**Author:** ![surya](https://forum.hestiacp.com/user_avatar/forum.hestiacp.com/surya/32/7795_2.png) [@surya](https://forum.hestiacp.com/u/surya)\
**Post date:** [November 3, 2026, 11:39am UTC](https://forum.hestiacp.com/t/hestia-upgrade-a-lot-of-errors/22413/8 "2026-11-03T11:39:42Z")

</div>

it fixed the issue. Now everything is up and working.
