OpenClaw

[creative567145]

@andreasdueren Thank you for the fast response and fix.
We performed the update.
And now OpenClaw is stuck in process: Starting

Here are the error logs, if they are useful:

Jul 19 17:37:59 OpenClaw 2026.7.1 (2d2ddc4)
Jul 19 17:37:59 I'm basically a Swiss Army knife, but with more opinions and fewer sharp edges.
Jul 19 17:37:59 2026-07-19T15:37:59Z 
Jul 19 17:38:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.17.9:8000
Jul 19 17:38:00 [openclaw] Could not start the CLI.
Jul 19 17:38:00 [openclaw] Reason: Cannot find module '@openclaw/ai/internal/runtime'
Jul 19 17:38:00 Require stack:
Jul 19 17:38:00 - /app/code/dist/errors-XbAR6hS3.js
Jul 19 17:38:00 [openclaw] Debug: set OPENCLAW_DEBUG=1 to include the stack trace.
Jul 19 17:38:00 [openclaw] Try: openclaw doctor
Jul 19 17:38:00 [openclaw] Help: openclaw --help
Jul 19 17:38:13 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:38:23 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:38:33 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:38:43 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:38:53 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:39:01 => Healthcheck error: Error: connect ECONNREFUSED 172.18.17.9:8000
Jul 19 17:39:01 ==> Loading environment from /app/data/.env
Jul 19 17:39:03 ==> Starting OpenClaw gateway on port 8000
Jul 19 17:39:05 2026-07-19T15:39:05Z 
Jul 19 17:39:05 OpenClaw 2026.7.1 (2d2ddc4)
Jul 19 17:39:05 Your config is valid, your assumptions are not.
Jul 19 17:39:05 2026-07-19T15:39:05Z 
Jul 19 17:39:06 [openclaw] Could not start the CLI.
Jul 19 17:39:06 [openclaw] Reason: Cannot find module '@openclaw/ai/internal/runtime'
Jul 19 17:39:06 Require stack:
Jul 19 17:39:06 - /app/code/dist/errors-XbAR6hS3.js
Jul 19 17:39:06 [openclaw] Debug: set OPENCLAW_DEBUG=1 to include the stack trace.
Jul 19 17:39:06 [openclaw] Try: openclaw doctor
Jul 19 17:39:06 [openclaw] Help: openclaw --help
Jul 19 17:39:13 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:39:23 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:39:33 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:39:43 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:39:53 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:40:01 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:40:06 ==> Loading environment from /app/data/.env
Jul 19 17:40:08 ==> Starting OpenClaw gateway on port 8000
Jul 19 17:40:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.17.9:8000
Jul 19 17:40:10 2026-07-19T15:40:10Z 
Jul 19 17:40:10 OpenClaw 2026.7.1 (2d2ddc4)
Jul 19 17:40:10 I'm not AI-powered, I'm AI-possessed. Big difference.
Jul 19 17:40:10 2026-07-19T15:40:10Z 
Jul 19 17:40:11 [openclaw] Could not start the CLI.
Jul 19 17:40:11 [openclaw] Reason: Cannot find module '@openclaw/ai/internal/runtime'
Jul 19 17:40:11 Require stack:
Jul 19 17:40:11 - /app/code/dist/errors-XbAR6hS3.js
Jul 19 17:40:11 [openclaw] Debug: set OPENCLAW_DEBUG=1 to include the stack trace.
Jul 19 17:40:11 [openclaw] Try: openclaw doctor
Jul 19 17:40:11 [openclaw] Help: openclaw --help
Jul 19 17:40:23 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:40:33 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:40:43 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:40:53 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:41:03 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 17:41:11 => Healthcheck error: Error: connect ECONNREFUSED 172.18.17.9:8000
Jul 19 17:41:11 ==> Loading environment from /app/data/.env
Jul 19 17:41:14 ==> Starting OpenClaw gateway on port 8000
Jul 19 17:41:15 2026-07-19T15:41:15Z 
Jul 19 17:41:15 OpenClaw 2026.7.1 (2d2ddc4)
Jul 19 17:41:15 Open source means you can see exactly how I judge your config.

[andreasdueren]

@creative567145

2.0.5 is publishing now with the fix: workspace symlinks are materialized into real directories in the image, and the build now asserts that the AI runtime module actually resolves before an image can ship. So this class of breakage will fail the build going forward instead of breaking your installation.

[creative567145]

@andreasdueren Thank you.
Now it's marked as: Not responding.

Here are the error logs, hope they are useful:

Jul 19 22:11:45 OpenClaw 2026.7.1 (2d2ddc4)
Jul 19 22:11:45 Give me a workspace and I'll give you fewer tabs, fewer toggles, and more oxygen.
Jul 19 22:11:48 ◇  Doctor warnings ────────────────────────────────────────────────────╮
Jul 19 22:11:48 - Skipped Memory Core short-term recall import for /app/data/.openclaw/workspace because SQLite rows already exist; left legacy source in place
Jul 19 22:11:48 20:11:48 [state-migrations] Legacy state migration warnings:
Jul 19 22:11:48 │
Jul 19 22:11:48 │                                                                      │
Jul 19 22:11:48 │                                                                      │
Jul 19 22:11:48 │    /app/data/.openclaw/workspace because SQLite rows already exist;  │
Jul 19 22:11:48 │    left legacy source in place                                       │
Jul 19 22:11:48 │  - Skipped Memory Core short-term recall import for                  │
Jul 19 22:11:48 ├──────────────────────────────────────────────────────────────────────╯
Jul 19 22:11:48 - Skipped Memory Core short-term recall import for /app/data/.openclaw/workspace because SQLite rows already exist; left legacy source in place
Jul 19 22:11:48 Run "openclaw doctor --fix" against the mounted state/config, then restart the container.
Jul 19 22:11:48 [openclaw] Could not start the CLI.
Jul 19 22:11:48 [openclaw] Debug: set OPENCLAW_DEBUG=1 to include the stack trace.
Jul 19 22:11:48 [openclaw] Help: openclaw --help
Jul 19 22:11:48 [openclaw] Reason: OpenClaw startup migrations did not complete cleanly; refusing to report the gateway ready.
Jul 19 22:11:48 [openclaw] Try: openclaw doctor
Jul 19 22:11:57 => Healthcheck error: AbortError: The operation was aborted
Jul 19 22:12:07 => Healthcheck error: AbortError: The operation was aborted
Jul 19 22:12:17 => Healthcheck error: AbortError: The operation was aborted
Jul 19 22:12:24 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 22:12:33 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 22:12:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.17.9:8000
Jul 19 22:12:40 ==> Loading environment from /app/data/.env
Jul 19 22:12:42 ==> Starting OpenClaw gateway on port 8000
Jul 19 22:12:44 2026-07-19T20:12:44Z 
Jul 19 22:12:44 2026-07-19T20:12:44Z 
Jul 19 22:12:44 OpenClaw 2026.7.1 (2d2ddc4)
Jul 19 22:12:44 WhatsApp automation without the "please accept our new privacy policy".
Jul 19 22:12:48 ◇  Doctor warnings ────────────────────────────────────────────────────╮
Jul 19 22:12:48 - Skipped Memory Core short-term recall import for /app/data/.openclaw/workspace because SQLite rows already exist; left legacy source in place
Jul 19 22:12:48 20:12:48 [state-migrations] Legacy state migration warnings:
Jul 19 22:12:48 │
Jul 19 22:12:48 │                                                                      │
Jul 19 22:12:48 │                                                                      │
Jul 19 22:12:48 │    /app/data/.openclaw/workspace because SQLite rows already exist;  │
Jul 19 22:12:48 │    left legacy source in place                                       │
Jul 19 22:12:48 │  - Skipped Memory Core short-term recall import for                  │
Jul 19 22:12:48 ├──────────────────────────────────────────────────────────────────────╯
Jul 19 22:12:48 - Skipped Memory Core short-term recall import for /app/data/.openclaw/workspace because SQLite rows already exist; left legacy source in place
Jul 19 22:12:48 Run "openclaw doctor --fix" against the mounted state/config, then restart the container.
Jul 19 22:12:48 [openclaw] Could not start the CLI.
Jul 19 22:12:48 [openclaw] Debug: set OPENCLAW_DEBUG=1 to include the stack trace.
Jul 19 22:12:48 [openclaw] Help: openclaw --help
Jul 19 22:12:48 [openclaw] Reason: OpenClaw startup migrations did not complete cleanly; refusing to report the gateway ready.
Jul 19 22:12:48 [openclaw] Try: openclaw doctor
Jul 19 22:12:57 => Healthcheck error: AbortError: The operation was aborted
Jul 19 22:13:07 => Healthcheck error: AbortError: The operation was aborted
Jul 19 22:13:17 => Healthcheck error: AbortError: The operation was aborted
Jul 19 22:13:24 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 22:13:33 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 22:13:43 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 22:13:48 ==> Loading environment from /app/data/.env
Jul 19 22:13:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.17.9:8000
Jul 19 22:13:51 ==> Starting OpenClaw gateway on port 8000
Jul 19 22:13:52 2026-07-19T20:13:52Z 
Jul 19 22:13:52 2026-07-19T20:13:52Z 
Jul 19 22:13:52 OpenClaw 2026.7.1 (2d2ddc4)
Jul 19 22:13:52 I'm the assistant your terminal demanded, not the one your sleep schedule requested.
Jul 19 22:13:56 20:13:56 [state-migrations] Legacy state migration warnings:
Jul 19 22:13:56 - Skipped Memory Core short-term recall import for /app/data/.openclaw/workspace because SQLite rows already exist; left legacy source in place
Jul 19 22:13:56 │
Jul 19 22:13:56 ◇  Doctor warnings ────────────────────────────────────────────────────╮
Jul 19 22:13:56 │                                                                      │
Jul 19 22:13:56 │  - Skipped Memory Core short-term recall import for                  │
Jul 19 22:13:56 │    /app/data/.openclaw/workspace because SQLite rows already exist;  │
Jul 19 22:13:56 │    left legacy source in place                                       │
Jul 19 22:13:56 │                                                                      │
Jul 19 22:13:56 ├──────────────────────────────────────────────────────────────────────╯
Jul 19 22:13:56 [openclaw] Could not start the CLI.
Jul 19 22:13:56 [openclaw] Reason: OpenClaw startup migrations did not complete cleanly; refusing to report the gateway ready.
Jul 19 22:13:56 - Skipped Memory Core short-term recall import for /app/data/.openclaw/workspace because SQLite rows already exist; left legacy source in place
Jul 19 22:13:56 Run "openclaw doctor --fix" against the mounted state/config, then restart the container.
Jul 19 22:13:56 [openclaw] Debug: set OPENCLAW_DEBUG=1 to include the stack trace.
Jul 19 22:13:56 [openclaw] Try: openclaw doctor
Jul 19 22:13:56 [openclaw] Help: openclaw --help
Jul 19 22:14:07 => Healthcheck error: AbortError: The operation was aborted
Jul 19 22:14:17 => Healthcheck error: AbortError: The operation was aborted
Jul 19 22:14:27 => Healthcheck error: AbortError: The operation was aborted
Jul 19 22:14:33 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 22:14:43 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 22:14:53 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.17.9:8000
Jul 19 22:14:56 ==> Loading environment from /app/data/.env
Jul 19 22:14:59 ==> Starting OpenClaw gateway on port 8000
Jul 19 22:15:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.17.9:8000
Jul 19 22:15:00 2026-07-19T20:15:00Z 

[andreasdueren]

Thanks for your patience, this was a third, different layer of the same upstream release, and should be fixed in 2.0.6.

What happened: OpenClaw v2026.7.x introduced a strict startup check. After an update, the gateway runs state migrations and refuses to start if any migration finishes with a warning. Your install has older Memory Core state files (memory/.dreams/*.json) whose contents had already been migrated to the new SQLite store, so the migration skipped them with a "left legacy source in place" warning. And that recurring warning was treated as fatal on every restart, hence the permanent "Not responding".

2.0.6 now attempts the package self-heal on startup: it runs upstream's documented remedy (openclaw doctor --fix) automatically before starting the gateway, and then archives the already-migrated legacy state files to /app/data/legacy-state-archive/<timestamp>/.

Please update to 2.0.6, it should then come up healthy with no manual steps. If it still misbehaves, post fresh logs and I'll take another look.

[creative567145]

@andreasdueren Thank you very much. I confirm that OpenClaw is now running without errors.

[creative567145]

Hi @andreasdueren
The OpenClaw version 2.0.8 - 2 months old

When we try to update it, it gives this error:
Error - Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown statusCode: 404

Please notify me if we need to make some modification via the Terminal or File manager so that it pulls from the right location, thanks

[andreasdueren]

@creative567145 you should be all set again, I pruned a bit too much on the docker side of things while cleaning up the server.

[creative567145]

Thank you @andreasdueren much appreciated.
Re-tried the updates and failed again.
This is the error:
Error - Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown statusCode: 404

Here are the logs in case if useful:

Oct 27 19:21:49 apptask: run: startTask installationState: pending_update runState: running
Oct 27 19:21:49 tasks: updating task 4192 with: {"percent":5,"message":"Verify manifest"}
Oct 27 19:21:49 tasks: updating task 4192 with: {"percent":20,"message":"Downloading image"}
Oct 27 19:21:49 shell: df: df -B1 --output=source,fstype,size,used,avail,pcent,target /var/lib/docker
Oct 27 19:21:49 docker: downloadImage: registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9
Oct 27 19:21:49 docker: pullImage: will pull registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. auth: no
Oct 27 19:21:50 docker: Attempt 1 failed. Will retry: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404 
Oct 27 19:21:55 docker: pullImage: will pull registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. auth: no
Oct 27 19:21:56 docker: Attempt 2 failed. Will retry: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404 
Oct 27 19:22:01 docker: pullImage: will pull registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. auth: no
Oct 27 19:22:02 docker: Attempt 3 failed. Will retry: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404 
Oct 27 19:22:07 docker: pullImage: will pull registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. auth: no
Oct 27 19:22:08 docker: Attempt 4 failed. Will retry: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404 
Oct 27 19:22:13 docker: pullImage: will pull registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. auth: no
Oct 27 19:22:14 docker: Attempt 5 failed. Will retry: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404 
Oct 27 19:22:19 docker: pullImage: will pull registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. auth: no
Oct 27 19:22:20 docker: Attempt 6 failed. Will retry: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404 
Oct 27 19:22:25 docker: pullImage: will pull registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. auth: no
Oct 27 19:22:26 docker: Attempt 7 failed. Will retry: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404 
Oct 27 19:22:31 docker: pullImage: will pull registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. auth: no
Oct 27 19:22:32 docker: Attempt 8 failed. Will retry: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404 
Oct 27 19:22:37 docker: pullImage: will pull registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. auth: no
Oct 27 19:22:38 docker: Attempt 9 failed. Will retry: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404 
Oct 27 19:22:43 docker: pullImage: will pull registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. auth: no
Oct 27 19:22:44 apptask: run: app error for state pending_update: BoxError: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404
    at pullImage (file:///home/yellowtent/box/src/docker.js:116:50)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async file:///home/yellowtent/box/src/docker.js:489:122
    at async retry (file:///home/yellowtent/box/src/retry.js:13:20)
    at async Object.downloadImage (file:///home/yellowtent/box/src/docker.js:487:5)
    at async downloadImage (file:///home/yellowtent/box/src/apptask.js:197:5)
    at async updateCommand (file:///home/yellowtent/box/src/apptask.js:732:5) {
  [stack]: [Getter/Setter],
  [message]: 'Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404',
  name: 'BoxError',
  reason: 'Not found',
  extra: {}
}
Oct 27 19:22:44 docker: Attempt 10 failed. Will retry: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404 BoxError: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404
    at pullImage (file:///home/yellowtent/box/src/docker.js:116:50)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async file:///home/yellowtent/box/src/docker.js:489:122
    at async retry (file:///home/yellowtent/box/src/retry.js:13:20)
    at async Object.downloadImage (file:///home/yellowtent/box/src/docker.js:487:5)
    at async downloadImage (file:///home/yellowtent/box/src/apptask.js:197:5)
    at async updateCommand (file:///home/yellowtent/box/src/apptask.js:732:5)
Oct 27 19:22:44 tasks: setCompleted - 4192: {"result":null,"error":{"message":"Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404","reason":"Not found","stack":"BoxError: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404\n    at pullImage (file:///home/yellowtent/box/src/docker.js:116:50)\n    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n    at async file:///home/yellowtent/box/src/docker.js:489:122\n    at async retry (file:///home/yellowtent/box/src/retry.js:13:20)\n    at async Object.downloadImage (file:///home/yellowtent/box/src/docker.js:487:5)\n    at async downloadImage (file:///home/yellowtent/box/src/apptask.js:197:5)\n    at async updateCommand (file:///home/yellowtent/box/src/apptask.js:732:5)"},"percent":100}
Oct 27 19:22:44 tasks: updating task 4192 with: {"completed":true,"result":null,"error":{"message":"Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404","reason":"Not found","stack":"BoxError: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404\n    at pullImage (file:///home/yellowtent/box/src/docker.js:116:50)\n    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n    at async file:///home/yellowtent/box/src/docker.js:489:122\n    at async retry (file:///home/yellowtent/box/src/retry.js:13:20)\n    at async Object.downloadImage (file:///home/yellowtent/box/src/docker.js:487:5)\n    at async downloadImage (file:///home/yellowtent/box/src/apptask.js:197:5)\n    at async updateCommand (file:///home/yellowtent/box/src/apptask.js:732:5)"},"percent":100}
Oct 27 19:22:44 taskworker: Task took 54.932 seconds
Oct 27 19:22:44 BoxError: Unable to pull image registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9. message: (HTTP code 404) unexpected - manifest for registry.docker.due.ren/andreasdueren/openclaw-cloudron:2.0.9 not found: manifest unknown: manifest unknown  statusCode: 404
    at pullImage (file:///home/yellowtent/box/src/docker.js:116:50)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async file:///home/yellowtent/box/src/docker.js:489:122
    at async retry (file:///home/yellowtent/box/src/retry.js:13:20)
    at async Object.downloadImage (file:///home/yellowtent/box/src/docker.js:487:5)
    at async downloadImage (file:///home/yellowtent/box/src/apptask.js:197:5)
    at async updateCommand (file:///home/yellowtent/box/src/apptask.js:732:5)
Oct 27 19:22:44 Exiting with code 0
Oct 27 19:56:03 2026-10-27T18:56:03Z 
Oct 27 19:56:03     at #cachedDefaultResolve (node:internal/modules/esm/loader:701:20)
Oct 27 19:56:03     at #resolve (node:internal/modules/esm/loader:683:17)
Oct 27 19:56:03     at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:721:38)
Oct 27 19:56:03     at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:603:35)
Oct 27 19:56:03     at ModuleLoader.resolveSync (node:internal/modules/esm/loader:759:56)
Oct 27 19:56:03     at TracingChannel.tracePromise (node:diagnostics_channel:362:14) {
Oct 27 19:56:03     at node:internal/modules/esm/loader:632:32
Oct 27 19:56:03 Node.js v24.19.0
Oct 27 19:56:03 code: 'ERR_MODULE_NOT_FOUND',
Oct 27 19:56:03 url: 'file:///app/code/node-version.mjs'
Oct 27 19:56:03 }
Oct 27 19:57:03 2026-10-27T18:57:03Z 
Oct 27 19:57:03 2026-10-27T18:57:03Z 
Oct 27 19:57:03 2026-10-27T18:57:03Z 
Oct 27 19:57:03 2026-10-27T18:57:03Z 
Oct 27 19:57:03     at #cachedDefaultResolve (node:internal/modules/esm/loader:701:20)
Oct 27 19:57:03     at #cachedDefaultResolve (node:internal/modules/esm/loader:701:20)
Oct 27 19:57:03     at #resolve (node:internal/modules/esm/loader:683:17)
Oct 27 19:57:03     at #resolve (node:internal/modules/esm/loader:683:17)
Oct 27 19:57:03     at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:721:38)
Oct 27 19:57:03     at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:721:38)
Oct 27 19:57:03     at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:603:35)
Oct 27 19:57:03     at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:603:35)
Oct 27 19:57:03     at ModuleLoader.resolveSync (node:internal/modules/esm/loader:759:56)
Oct 27 19:57:03     at ModuleLoader.resolveSync (node:internal/modules/esm/loader:759:56)
Oct 27 19:57:03     at TracingChannel.tracePromise (node:diagnostics_channel:362:14) {
Oct 27 19:57:03     at TracingChannel.tracePromise (node:diagnostics_channel:362:14) {
Oct 27 19:57:03     at defaultResolve (node:internal/modules/esm/resolve:992:11)
Oct 27 19:57:03     at defaultResolve (node:internal/modules/esm/resolve:992:11)
Oct 27 19:57:03     at finalizeResolution (node:internal/modules/esm/resolve:271:11)
Oct 27 19:57:03     at finalizeResolution (node:internal/modules/esm/resolve:271:11)
Oct 27 19:57:03     at moduleResolve (node:internal/modules/esm/resolve:865:10)
Oct 27 19:57:03     at moduleResolve (node:internal/modules/esm/resolve:865:10)
Oct 27 19:57:03     at node:internal/modules/esm/loader:632:32
Oct 27 19:57:03     at node:internal/modules/esm/loader:632:32
Oct 27 19:57:03 ==> Loading environment from /app/data/.env
Oct 27 19:57:03 ==> Running openclaw doctor --fix (startup migration self-heal)
Oct 27 19:57:03 ==> Starting OpenClaw gateway on port 8000
Oct 27 19:57:03 ==> doctor --fix exited non-zero (non-fatal, continuing)
Oct 27 19:57:03 Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/app/code/node-version.mjs' imported from /app/code/openclaw.mjs
Oct 27 19:57:03 Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/app/code/node-version.mjs' imported from /app/code/openclaw.mjs
Oct 27 19:57:03 Node.js v24.19.0
Oct 27 19:57:03 Node.js v24.19.0
Oct 27 19:57:03 ^
Oct 27 19:57:03 ^
Oct 27 19:57:03 code: 'ERR_MODULE_NOT_FOUND',
Oct 27 19:57:03 code: 'ERR_MODULE_NOT_FOUND',
Oct 27 19:57:03 node:internal/modules/esm/resolve:271
Oct 27 19:57:03 node:internal/modules/esm/resolve:271
Oct 27 19:57:03 throw new ERR_MODULE_NOT_FOUND(
Oct 27 19:57:03 throw new ERR_MODULE_NOT_FOUND(
Oct 27 19:57:03 url: 'file:///app/code/node-version.mjs'
Oct 27 19:57:03 url: 'file:///app/code/node-version.mjs'
Oct 27 19:57:03 }
Oct 27 19:57:03 }

[andreasdueren]

@creative567145 Please try updating one more time now.

[creative567145]

Thank you @andreasdueren - now that is fixed.
OpenClaw was updated to the current version: 2.0.12
And the state is now: Not responding

If useful, here are the logs:

Oct 27 20:40:55 ==> Starting OpenClaw gateway on port 8000
Oct 27 20:40:55 [openclaw] For help, run `openclaw doctor`.
Oct 27 20:40:55 [openclaw] The CLI command failed.
Oct 27 20:40:56 [gateway] startup phase: cli.main.gateway-run-select-environment starting total=764.5ms
Oct 27 20:40:56 [gateway] startup phase: entry.run-main-import 49.7ms total=199.4ms start=149.6ms
Oct 27 20:40:56 [gateway] startup phase: entry.run-main-import starting total=149.6ms
Oct 27 20:40:57 t;ut;4;0m
Oct 27 20:40:57 [gateway] startup phase: cli.main.gateway-run-select-environment 315.5ms total=1080.0ms start=764.5ms failed
Oct 27 20:40:57 [openclaw] For help, run `openclaw doctor`.
Oct 27 20:40:57 [openclaw] The CLI command failed.
Oct 27 20:41:02 taskworker: Starting task 4198. Logs are at /home/yellowtent/platformdata/logs/da4c169b-7ed5-4c41-b0d3-853def962a5b/apptask.log
Oct 27 20:41:02 taskworker: Running task of type app
Oct 27 20:41:02 apptask: run: startTask installationState: pending_restart runState: running
Oct 27 20:41:02 tasks: updating task 4198 with: {"percent":10,"message":"Starting app services"}
Oct 27 20:41:02 tasks: updating task 4198 with: {"percent":30,"message":"Restarting container"}
Oct 27 20:41:02 tasks: updating task 4198 with: {"percent":70,"message":"Configuring reverse proxy"}
Oct 27 20:41:02 shell: openssl: openssl x509 -noout -subject -issuer
Oct 27 20:41:02 reverseproxy: providerMatches: subject=CN=ai.midwestmettle.com domain=ai.midwestmettle.com issuer=C=US, O=Let's Encrypt, CN=YE2 wildcard=false/false prod=true/true issuerMismatch=false wildcardMismatch=false match=true
Oct 27 20:41:02 shell: openssl: openssl x509 -startdate -enddate -subject -noout
Oct 27 20:41:02 openssl: expiryDate: subject=CN=ai.midwestmettle.com notBefore=Oct 11 11:11:53 2026 GMT notAfter=Jan  9 11:11:52 2027 GMT daysLeft=73.64640278935185
Oct 27 20:41:02 reverseproxy: ensureCertificate: ai.midwestmettle.com acme cert exists and is up to date
Oct 27 20:41:02 reverseproxy: needsRenewal: false. ARI {"start":"Wed, 09 Dec 2026 13:55:57 GMT","end":"Fri, 11 Dec 2026 09:06:47 GMT","rt":"Thu, 10 Dec 2026 23:39:31 GMT","valid":"Tue, 27 Oct 2026 20:58:14 GMT","url":"https://acme-v02.api.letsencrypt.org/acme/renewal-info","ts":"Tue, 27 Oct 2026 15:10:01 GMT"}
Oct 27 20:41:02 reverseproxy: writeAppLocationNginxConfig: writing config for "ai.midwestmettle.com" to /home/yellowtent/platformdata/nginx/applications/da4c169b-7ed5-4c41-b0d3-853def962a5b/ai.midwestmettle.com.conf with options {"sourceDir":"/home/yellowtent/box","vhost":"ai.midwestmettle.com","hasIPv6":true,"ip":"172.18.18.4","port":8000,"endpoint":"app","redirectTo":null,"certFilePath":"/home/yellowtent/platformdata/nginx/cert/ai.midwestmettle.com.cert","keyFilePath":"/home/yellowtent/platformdata/nginx/cert/ai.midwestmettle.com.key","robotsTxtQuoted":null,"cspQuoted":null,"hideHeaders":[],"proxyAuth":{"enabled":{"supportsBearerAuth":true},"id":"da4c169b-7ed5-4c41-b0d3-853def962a5b","location":"/","oidcClientId":"da4c169b-7ed5-4c41-b0d3-853def962a5b","oidcEndpoint":"my.videos.midwestmettle.com"},"upstreamUri":"","ingress":{"enabled":false,"appIp":null,"appIp6":null,"vpnAppIp":null,"vpnAppIp6":null},"hstsPreload":false,"http2OnDirective":true}
Oct 27 20:41:02 shell: reverseproxy: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/restartservice.sh nginx
Oct 27 20:41:02 tasks: updating task 4198 with: {"percent":100,"message":"Done"}
Oct 27 20:41:02 tasks: setCompleted - 4198: {"result":null,"error":null,"percent":100}
Oct 27 20:41:02 tasks: updating task 4198 with: {"completed":true,"result":null,"error":null,"percent":100}
Oct 27 20:41:02 Exiting with code 0
Oct 27 20:41:02 taskworker: Task took 0.348 seconds
Oct 27 20:41:02 ==> Loading environment from /app/data/.env
Oct 27 20:41:02 ==> Running openclaw doctor --fix (startup migration self-heal)
Oct 27 20:41:03 t;ut;4;0m==> doctor --fix exited non-zero (non-fatal, continuing)
Oct 27 20:41:03 ==> Starting OpenClaw gateway on port 8000
Oct 27 20:41:03 [openclaw] For help, run `openclaw doctor`.
Oct 27 20:41:03 [openclaw] The CLI command failed.
Oct 27 20:41:04 t;ut;4;0m
Oct 27 20:41:04 [gateway] startup phase: cli.main.gateway-run-select-environment 368.4ms total=1088.0ms start=719.6ms failed
Oct 27 20:41:04 [gateway] startup phase: cli.main.gateway-run-select-environment starting total=719.6ms
Oct 27 20:41:04 [gateway] startup phase: entry.run-main-import 49.8ms total=195.9ms start=146.1ms
Oct 27 20:41:04 [gateway] startup phase: entry.run-main-import starting total=146.1ms
Oct 27 20:41:04 [openclaw] For help, run `openclaw doctor`.
Oct 27 20:41:04 [openclaw] The CLI command failed.
Oct 27 20:41:05 ==> Loading environment from /app/data/.env
Oct 27 20:41:05 ==> Running openclaw doctor --fix (startup migration self-heal)
Oct 27 20:41:06 t;ut;4;0m==> doctor --fix exited non-zero (non-fatal, continuing)
Oct 27 20:41:06 ==> Starting OpenClaw gateway on port 8000
Oct 27 20:41:06 [gateway] startup phase: cli.main.gateway-run-select-environment starting total=729.3ms
Oct 27 20:41:06 [gateway] startup phase: entry.run-main-import 49.2ms total=194.4ms start=145.2ms
Oct 27 20:41:06 [gateway] startup phase: entry.run-main-import starting total=145.2ms
Oct 27 20:41:06 [openclaw] For help, run `openclaw doctor`.
Oct 27 20:41:06 [openclaw] The CLI command failed.
Oct 27 20:41:07 t;ut;4;0m

[andreasdueren]

@creative567145 Thanks, the update itself works now, so we are one step further. 2.0.12 starts fine on a fresh install, so this is related to the existing data from 2.0.8. OpenClaw hides the actual error by default.

Could you add this line to ‘/app/data/.env via the File manager: OPENCLAW_DEBUG=1

Then restart the app, wait about 5 minutes (the first start after the update migrates the database and can take a few minutes), and post the log lines after "Running openclaw doctor --fix" and "Starting OpenClaw gateway"? You can remove the line again afterwards.

[creative567145]

Thank you @andreasdueren I appreciate the assistance

This is what we see in the logs now:

Oct 28 16:16:07 ==> Running openclaw doctor --fix (startup migration self-heal)
Oct 28 16:16:08 [openclaw] The CLI command failed.
Oct 28 16:16:08 [openclaw] Reason: Cannot find package 'is-plain-obj' imported from /app/code/node_modules/execa/lib/methods/create.js
Oct 28 16:16:08 [openclaw] Stack:
Oct 28 16:16:08 [openclaw] Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'is-plain-obj' imported from /app/code/node_modules/execa/lib/methods/create.js
Oct 28 16:16:08 [openclaw]     at Object.getPackageJSONURL (node:internal/modules/package_json_reader:331:9)
Oct 28 16:16:08 [openclaw]     at packageResolve (node:internal/modules/esm/resolve:784:25)
Oct 28 16:16:08 [openclaw]     at moduleResolve (node:internal/modules/esm/resolve:873:18)
Oct 28 16:16:08 [openclaw]     at defaultResolve (node:internal/modules/esm/resolve:1006:11)
Oct 28 16:16:08 [openclaw]     at #cachedDefaultResolve (node:internal/modules/esm/loader:705:20)
Oct 28 16:16:08 [openclaw]     at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:725:38)
Oct 28 16:16:08 [openclaw]     at nextStep (node:internal/modules/customization_hooks:189:26)
Oct 28 16:16:08 [openclaw]     at resolve (file:///app/code/dist/entry.esm-resolve-fast-path-gJ7_FrDl.mjs:78:10)
Oct 28 16:16:08 [openclaw]     at nextStep (node:internal/modules/customization_hooks:189:26)
Oct 28 16:16:08 [openclaw]     at resolveWithHooks (node:internal/modules/customization_hooks:417:10)
Oct 28 16:16:08 [openclaw] Try: openclaw doctor
Oct 28 16:16:08 [openclaw] Help: openclaw --help
Oct 28 16:16:08 t;ut;4;0m==> doctor --fix exited non-zero (non-fatal, continuing)
Oct 28 16:16:08 ==> Starting OpenClaw gateway on port 8000

[andreasdueren]

@creative567145 Thanks, that log showed the real cause, and it was a packaging bug. OpenClaw changed how its dependencies are laid out, and the package was breaking those links during the build. 2.0.13 fixes this, and the build now only publishes an image after running doctor --fix and booting the gateway successfully.

Please update to 2.0.13. The first start can take a few minutes while doctor migrates the database. You can remove OPENCLAW_DEBUG=1 from /app/data/.env again, or keep it until it is running.

[creative567145]

Thank you @andreasdueren the fix is confirmed. I appreciate your help very much! If there is anything that I can do to assist you in the future (test some software for you, donate, etc) please let me know