Cloudron Forum

@joseph Thank you very much. That fixed the issue

the post can be marked as solved

Hi @james
It is for a client. They have let some freelancer to log in and install custom Plugins. Then something broke.
Then the freelancer ditched.

We have the latest 7 backups and we are trying to restore EspoCRM, but with no luck.
We also tried the cloning option. No success with that either.

So we sent the Logs error in case if your team and the community can notice what is the issue

EspoCRM stopped working.
It's marked as: Not responding

The current version is:
App title & version - Espo CRM 9.2.5
Package version - com.espocrm.cloudronapp@2.19.4

This is the error in the logs:

-----
Nov 21 10:29:15 2025-11-21T09:29:15Z
Nov 21 10:29:15 ==> Could not upgrade
Nov 21 10:29:23 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.12:8000
Nov 21 10:29:33 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.12:8000
Nov 21 10:29:43 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.12:8000
Nov 21 10:29:53 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.12:8000
Nov 21 10:30:03 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.12:8000
Nov 21 10:30:13 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.12:8000
Nov 21 10:30:15 ==> Fixing up modules
Nov 21 10:30:16 ==> Data version is 9.1.9. Expecting 9.2.5
Nov 21 10:30:16 ==> Running upgrade script
Nov 21 10:30:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.17.12:8000
Nov 21 10:30:20 ==> Failed to upgrade.
Nov 21 10:30:20 ----- Upgrade output -----
Nov 21 10:30:20 Error: Your EspoCRM version (9.1.9) is not supported. Required version: 9.2.4.

Has anybody else had this problem? If yes, please share the solution

@matix131997 Thank you
We added that setting & then tested all combinations.
Still nothing works.

Thank you @james , much appreciated

Thank you @james

We have performed the steps and it's working

Here are the steps in detail (for noobs like me to replicate it):

1. Log in Cloudron + select EspoCRM + Click on the Repair tab: Enable Recovery Mode
2. Click: Terminal
3. Copy paste this:
   nano +704 application/Espo/Core/Utils/File/Manager.php
4. This is the original line:
   if (is_dir($dirPath) && is_writable($dirPath)) {
5. Change it to this:
   if (is_dir($dirPath) && is_writable($dirPath) && is_link($dirPath) === false) {
6. On the keyboard click: CTRL + X
   Then click to confirm: Y
7. Copy paste this:
   mkdir -p /run/espocrm/cache
   mkdir -p /run/espocrm/logs
   php command.php extension -u --name="Advanced Pack"
8. Close the Terminal window
9. Click to Disable the Recovery mode
   there is no need to Restart EspoCRM
10. Log in EspoCRM as admin >>> extensions

• 1 more step to update the Extension:
  Since the old Extension version was uninstalled, now we upload the new version + click Install

@james We noticed that the change in the Manager.php file is not permanent.
So this means that we would have to go through all these steps each time an Extension update is required.

Business-wise, this will reduce the client-retention rate of the Cloudron userbase. Especially those that aren't tech experienced.

Ideally the extension updates would be performed by the EspoCRM admin just uploading the new version inside EspoCRM (UI) and it replaces the old version.
Is it possible for the Cloudron team some day to push an update to the EspoCRM package that applies this change permanently?

Since only the person that has paid for it is able to get updates, I'll send the file to you in the private chat (for testing purposes)

@james Thank you for the fast response
Cloudron version: v8.3.2 (Ubuntu 24.04.3 LTS) (I have included the OS for just in case)
EspoCRM version: Espo CRM 9.2.2
Package Version: com.espocrm.cloudronapp@2.19.1
Advanced Pack - Extension version: advanced-pack-3.11.7

We couldn't find any info on how to Upgrade an extension, so here is the process we have done:
(Extension name: Advanced Pack)

1. We tried to upload it (the new version on top of the already installed version) directly in EspoCRM, and we got this error:
   Error 500
   Permission denied to delete files.

2. In EspoCRM we tried to Uninstall the extension, but we got this error:
   Error 500
   Permission denied to delete files.

3. We followed the steps listed here:
   https://docs.cloudron.io/packages/espocrm/#uninstalling-extension
   Command:
   php command.php extension -u --name="Advanced Pack"
   and we got this error:

PHP Warning:  mkdir(): File exists in /app/code/9.2.2/application/Espo/Core/Utils/File/Manager.php on line 517
PHP Warning:  mkdir(): No such file or directory in /app/code/9.2.2/application/Espo/Core/Utils/File/Manager.php on line 517
PHP Fatal error:  Uncaught Espo\Core\Utils\File\Exceptions\PermissionError: Permission denied: unable to create a folder on the server data/cache/application in /app/code/9.2.2/application/Espo/Core/Utils/File/Manager.php:654
Stack trace:
#0 /app/code/9.2.2/application/Espo/Core/Utils/File/Manager.php(298): Espo\Core\Utils\File\Manager->checkCreateFile()
#1 /app/code/9.2.2/application/Espo/Core/Utils/File/Manager.php(412): Espo\Core\Utils\File\Manager->putContents()
#2 /app/code/9.2.2/application/Espo/Core/Utils/DataCache.php(82): Espo\Core\Utils\File\Manager->putPhpContents()
#3 /app/code/9.2.2/application/Espo/Core/Utils/Module.php(101): Espo\Core\Utils\DataCache->store()
#4 /app/code/9.2.2/application/Espo/Core/Utils/Module.php(71): Espo\Core\Utils\Module->init()
#5 /app/code/9.2.2/application/Espo/Core/Utils/Module.php(120): Espo\Core\Utils\Module->get()
#6 [internal function]: Espo\Core\Utils\Module->Espo\Core\Utils\{closure}()
#7 /app/code/9.2.2/application/Espo/Core/Utils/Module.php(119): usort()
#8 /app/code/9.2.2/application/Espo/Core/Binding/EspoBindingLoader.php(42): Espo\Core\Utils\Module->getOrderedList()
#9 /app/code/9.2.2/application/Espo/Core/Container/ContainerBuilder.php(210): Espo\Core\Binding\EspoBindingLoader->__construct()
#10 /app/code/9.2.2/application/Espo/Core/Application.php(66): Espo\Core\Container\ContainerBuilder->build()
#11 /app/code/9.2.2/application/Espo/Core/Application.php(57): Espo\Core\Application->initContainer()
#12 /app/code/9.2.2/command.php(35): Espo\Core\Application->__construct()
#13 {main}
  thrown in /app/code/9.2.2/application/Espo/Core/Utils/File/Manager.php on line 654

4. We tried to do it with the Recovery turned off and here is the result:

php command.php extension -l

Extensions:
 Name: Advanced Pack
 ID: 68daa3e8f1907e629
 Version: 3.11.7
 Installed: yes

root@a039099f-5cea-4d45-9e1a-b2ddf13a2a71:/app/code/9.2.2# php command.php extension -u --name="Advanced Pack"
Uninstalling... Do not close the terminal. This may take a while...
Permission denied to delete files.
root@a039099f-5cea-4d45-9e1a-b2ddf13a2a71:/app/code/9.2.2# 

Currently we aren't able to Uninstall or Upgrade the current Extension.
Perhaps there is some bug with the current EspoCRM version or some other reason?

Thank you very much
@robi @joseph @crazybrad and @p44

The settings are correct because we are also using Backblaze for the backups.

We tried all your recommendations and nothing worked.

Has ANYBODY successfully performed the Typebot-BackblazeB2 connection?

If yes, please share the settings. We will perform the tests on our side also. Then we will send the detailed steps for the Cloudron developers to add in the Typebot documentation (if they wish) for everybody to benefit

With the recent changes to MinIO, we are forced to use another solution for the Typebot storage.

So we took a look at BackblazeB2.
Backblaze is very cost-effective 1TB=$6/m so it's a good solution.

We tried the following configuration:

1. Inside Backblaze
   Activated the Bucket
   Set CORS as receive from all
   Left the Lifecycle rules the same
   In the settings tested both Private + Public

2. In the Typebot backend file added the standard: (for this specific bucket)

export S3_ACCESS_KEY=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
export S3_SECRET_KEY=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
export S3_BUCKET=typebotstorage
export S3_ENDPOINT=s3.us-east-005.backblazeb2.com
export S3_SSL=true
export S3_REGION=us-east-005
+
It didn't work.

Made tests with:
export STORAGE_TYPE=s3
export S3_REGION=US
export S3_REGION=us
export S3_PORT=443
+
Also, no results.

And yes, we performed an App restart per each individual change.

Does anyone have an idea how to make it work?

Thank you @nebulon and @joseph

Thank you @nebulon
Please release the next patch when possible, because this means that we can't do any config editions to any of the Apps

I wish that we could do that, but this specific client doesn't want the configuration to be done. He is afraid that something might break. We assured him that all will be ok, but he insists. We must respect his wishes.

Perhaps in the near future we will try it for some other client with high number of users.

Hi

When we try to edit the config files using the File Manager for any app this happens:
(Example with Matrix)

1. Edit file: homeserver.yaml (owner: cloudron)
2. Click: Save + Close
3. In the folder there is a new file: homeserver.yaml.1 (owner: root)
4. Click: Restart App
5. The new file has changed owner: homeserver.yaml.1 (owner: cloudron)
6. And there aren't any changes performed inside: homeserver.yaml (owner: cloudron)
7. The changes aren't applied in the app

Is it possibly something that we are doing wrong, or is it just a temporary bug?

Thank you @girish that will be very useful

Thank you @nebulon and @girish very much!

Yes @nebulon it's a quite big database. This Nextcloud has around 6000 users.
The disk has above 1TB SSD so that was ok.

Thank you @girish for the detailed steps. They were very helpful!
The import was a success.

Note: The change isn't persistent on a Reboot.
It would be nice to change this:
max_connections = 500
to this:
max_connections = 3000
If the server is powerful enough, it should be able to sustain the x6 boost.
The only challenge is how to make the change persistent after Reboot

Thank you @nebulon and @joseph on your help

The PostreSQL service was already set to the max available 64GB RAM (from total 132GB RAM)

@nebulon here is the requested log: (thank you again)

Jul 17 06:51:43 2024-07-17 04:51:43.846 UTC [1062] ERROR: temporary file size exceeds temp_file_limit (1048576kB)

Jul 17 06:51:43 2024-07-17 04:51:43.846 UTC [1062] STATEMENT: CREATE INDEX oc_notifications_object ON public.oc_notifications USING btree (object_type, object_id);

Jul 17 06:51:43 2024-07-17 04:51:43.848 UTC [1007] root@db57af86418ca34a61b18acbf6308fb45e CONTEXT: parallel worker

Jul 17 06:51:43 2024-07-17 04:51:43.848 UTC [1007] root@db57af86418ca34a61b18acbf6308fb45e ERROR: temporary file size exceeds temp_file_limit (1048576kB)

Jul 17 06:51:43 2024-07-17 04:51:43.848 UTC [1007] root@db57af86418ca34a61b18acbf6308fb45e STATEMENT: CREATE INDEX oc_notifications_object ON public.oc_notifications USING btree (object_type, object_id);

Jul 17 06:51:43 2024-07-17 04:51:43.851 UTC [49] LOG: background worker "parallel worker" (PID 1062) exited with exit code 1

Jul 17 06:51:44 CONTEXT: parallel worker

Jul 17 06:51:44 restore: failed to restore database. code=3

Jul 17 06:51:44 restore: stderr from db import: ERROR: temporary file size exceeds temp_file_limit (1048576kB)

Jul 17 22:20:03 [GET] /healthcheck

Jul 17 22:20:03 healthcheck: disconnected

The PostgreSQL Dump file is 15GB.
From what we understand here, the limit is 1GB.
How can we increase this limit or solve this problem another way?

Hi

Have tried 10+ times to run a Nextcloud migration.

But we are constantly getting the same error.

We hope that this can be solved. Since this forum is public, the solution will be available for everyone else who will have the same problem

Task Error in the Nextcloud > Repair Tab:

Addons Error: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false

Logs:

17 06:41:29 box:tasks update 2805: {"percent":65,"message":"Download finished 2024-07-15-190000-564/app_vtmg.link_v4.22.2/postgresqldump to /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump"}
Jul 17 06:41:29 box:backupformat/rsync Recreating empty directories in {"localRoot":"/home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e","layout":[]}

Jul 17 06:44:37 box:backuptask downloadApp: time: 27101.091

Jul 17 06:44:37 box:tasks update 2805: {"percent":70,"message":"Restoring addons"}

Jul 17 06:44:37 box:services restoreAddons

Jul 17 06:44:37 box:services restoreAddons: restoring ["postgresql","sendmail","ldap","redis","localstorage","scheduler","turn"]

Jul 17 06:44:37 box:services Restore postgresql

Jul 17 06:44:37 box:services pipeFileToRequest: piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e

Jul 17 06:48:43 box:services pipeFileToRequest: piped /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e

Jul 17 06:51:44 box:services pipeFileToRequest: request completed with status code 500

Jul 17 06:51:44 box:apptask run: app error for state pending_restore: BoxError: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1311:60) at ClientRequest.emit (node:events:518:28) at ClientRequest.emit (node:domain:488:12) at HTTPParser.parserOnIncomingClient (node:_http_client:698:27) at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17) at Socket.socketOnData (node:_http_client:540:22) at Socket.emit (node:events:518:28) at Socket.emit (node:domain:488:12) at addChunk (node:internal/streams/readable:559:12) at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) { reason: 'Addons Error', details: {} }

Jul 17 06:51:44 box:taskworker Task took 27570.192 seconds

Jul 17 06:51:44 box:tasks setCompleted - 2805: {"result":null,"error":{"stack":"BoxError: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false\n at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1311:60)\n at ClientRequest.emit (node:events:518:28)\n at ClientRequest.emit (node:domain:488:12)\n at HTTPParser.parserOnIncomingClient (node:_http_client:698:27)\n at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)\n at Socket.socketOnData (node:_http_client:540:22)\n at Socket.emit (node:events:518:28)\n at Socket.emit (node:domain:488:12)\n at addChunk (node:internal/streams/readable:559:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)","name":"BoxError","reason":"Addons Error","details":{},"message":"Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false"}}

Jul 17 06:51:44 box:tasks update 2805: {"percent":100,"result":null,"error":{"stack":"BoxError: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false\n at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1311:60)\n at ClientRequest.emit (node:events:518:28)\n at ClientRequest.emit (node:domain:488:12)\n at HTTPParser.parserOnIncomingClient (node:_http_client:698:27)\n at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)\n at Socket.socketOnData (node:_http_client:540:22)\n at Socket.emit (node:events:518:28)\n at Socket.emit (node:domain:488:12)\n at addChunk (node:internal/streams/readable:559:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)","name":"BoxError","reason":"Addons Error","details":{},"message":"Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false"}}
[no timestamp]  Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false

Additional info if needed:

1. The migration is run from a Linode VPS (Nexcloud on Cloudron) Ubuntu 22.04 LTS OS
   to a Dedicated server Ubuntu 24.04 LTS OS
2. In order so that there isn't any PostgreSQL database corruption, before the Backup was created we put Nextcloud in Recovery mode (so that the database isn't edited). We also tested without putting it in Recovery mode and the result was the same.
3. The migration is running from a Linode Object Storage

@girish we are trying to connect a MySQL DB but it requires the following:
driver "mysql-connector-python"
Is it possilble for it to be installed by us or by your team (by pushing it in the new update)?
Thank you