Cloudron Forum

@timconsidine Thank you for your fast response. No worries.

Your documentation is very useful:
https://git.cloudron.io/timconsidine/cloudron-moltbot/-/blob/main/POSTINSTALL.md?ref_type=heads
so perhaps it will help me make OpenClaw work on DokPloy.

I'll test additionally if I can self-host an LLM via Ollama on a Cloudron VPS and connect it to OpenClaw

Congratz @timconsidine CCAI-P is an excellent software. I'm looking forward to Cloudron 9.1 and you expanding the Apps list.

I tested installing Moltbot (OpenClaw) and there are errors.

Used settings ---
Repository Location:
http://git.cloudron.io/timconsidine/cloudron-moltbot
+
Docker Image Location:
tcmbp132021/cloudron-moltbot:latest
+
Port Binding:
3000

Basically, it says that the image can't be pulled.

Please see if you can spot something strange:

Error in CCAI-P:
[7:34:50 PM] [2026-02-13 18:34:49] App installation error: Installation failed: Unable to pull image tcmbp132021/cloudron-moltbot:latest. message: (HTTP code 404) unexpected - manifest for tcmbp132021/cloudron-moltbot:latest not found: manifest unknown: manifest unknown statusCode: 404
[7:34:50 PM] [2026-02-13 18:34:49] Installation failed with exit code 1
[7:34:50 PM] ERROR: Installation failed: Unknown error

Error in Cloudron:
Error - Unable to pull image tcmbp132021/cloudron-moltbot:latest. message: (HTTP code 404) unexpected - manifest for tcmbp132021/cloudron-moltbot:latest not found: manifest unknown: manifest unknown statusCode: 404

Congratz Team Cloudron
Is there an approximate timeline for 9.1?

The Custom app build & deploy + Community packages are something that the majority of us have been looking forward to for a long time

We tested it by adding this Cron:

@monthly find /app/data/files/ -type f -name "*.mp4" -mtime +60 -delete

The purpose was to remove all videos with the extension .mp4 that are older than 2 months.
We have no idea if it's working or not. We can't see anything in the logs.

If anyone know how to improve the Cron please let me know

Thank you @james

We performed these steps and it was successful:

1. Add these lines in env.sh
   export NODES_EXCLUDE="["ExecuteCommand", "LocalFileTrigger"]"

2. Restarted N8N

3. Performed the test using these steps:

• (+) - Execute command
• Execute Once: ON
• Command: ffmpeg -version
• Test step
• Check the OUTPUT - ok (screenshot attached)

Thank you @james for the fast response.

1. For starters, we checked if FFmpeg is installed on the OS and we get the result that it isn't.
   Screenshot attached

2. Then, according to this:
   

   
   We should perform modifications to the docker compose file of N8N,
   but since we are doing that with env.sh (export put in front), we don't know what to add there.

That is why we asked if somebody has already done this successfully so that he can send the summarized steps, if possible

Hi

According to this Forum post/comment:
https://forum.cloudron.io/post/17531

FFmpeg is installed on Ubuntu 24.04 LTS OS

...
We researched and in order to make it work with N8N, some additional changes are required.

It would be very helpful if anybody can share that info

Thank you both @robi and @nebulon

Got it working.

Here are the steps in case if anybody wishes to replicate the process.
It would help a lot to the new Evcc users if the package includes the mentioned changes already.

Steps:

1. Installed Evcc
2. Click: File Manager
3. Click: New > New File
4. Name it this text: evcc.yaml
5. Click: Restart App
6. Refresh the web browser window. A new file will be created named: evcc.db
7. Open the file: evcc.yaml
   There is already a text like this inside:

network:
  schema: http
  port: 7070
  host: evcc.demo.cloudron.io
database:
  type: sqlite
  dsn: /app/data/evcc.db

Click enter 2 times to be able to write to a new line bellow

8. Copy-paste the text from here:
   https://docs.evcc.io/en/docs/installation/configuration#manual

This is the text:

## minimal configuration example

site:
  title: Home # display name for UI
  meters:
    grid: my_grid
    pv:
      - my_pv
    battery:
      - my_battery

# define your loadpoints according your needs
# see https://docs.evcc.io/en/docs/reference/configuration/loadpoints
loadpoints:
  - title: Garage # display name for UI
    charger: my_charger # charger
    vehicle: my_car # default vehicle

# meter definitions
# name can be freely chosen and is used as reference when assigning meters to site and loadpoints
# for documentation see https://docs.evcc.io/docs/devices/meters
meters:
  # replace with your real grid meter
  - name: my_grid
    type: template
    template: demo-meter
    usage: grid
    power: -1000 # 1 kW feed-in
  # replace with your real solar system
  - name: my_pv
    type: template
    template: demo-meter
    usage: pv
    power: 4000 # 4 kW production
  # replace with your real battery
  - name: my_battery
    type: template
    template: demo-battery
    usage: battery
    power: -1000 # 1 kW battery charging
    soc: 50 # 50 % state of charge

# replace with your real charger
# see https://docs.evcc.io/docs/devices/chargers
chargers:
  - name: my_charger
    type: template
    template: demo-charger
    status: C # charging
    power: 2000 # 2 kW charging power
    enabled: true # optional

# replace with your real vehicle (optional)
# see https://docs.evcc.io/docs/devices/vehicles
vehicles:
  - name: my_car
    type: template
    template: offline
    title: blue e-Golf
    capacity: 50 # in kWh

# enter your real grid tariff and feed-in price
# see https://docs.evcc.io/docs/tariffs
tariffs:
  currency: EUR
  grid:
    type: fixed
    price: 0.29 # EUR/kWh
  feedin:
    type: fixed
    price: 0.10 # EUR/kWh

9. Click: Save + Restart App

10. Click on Evcc (URL)

11. There we can see Demo data for: blue e-Golf - charging

Add a new Admin password
Click: Configuration + Add the password again
Click to activate the Experimental features

After this hopefully, the changes can be performed directly inside Evcc via the web browser UI.
If not, the evcc.yaml file will have to be edited manually,
because these terminal commands still aren't working: evcc detect + evcc configure

Hope that was useful

Thank you @robi for the fast response. We tested that and the result is the same

1. We installed Evcc

2. We see this notification:
   Run evcc detect or evcc configure for initial setup. Then restart the app.

3. We went in the EVCC - Terminal and have run both commands and this is the result:

Connecting...
root@448da2a9-736b-4cc3-9370-1e160d939387:/app/code# evcc detect
This account is currently not available.
root@448da2a9-736b-4cc3-9370-1e160d939387:/app/code# evcc configure
This account is currently not available.
root@448da2a9-736b-4cc3-9370-1e160d939387:/app/code#

Since there isn't any post in this category (except for the Package Updates post), has anybody configured Evcc and confirmed it's functionality?

@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