When trying to restart openclaw , my browser window slowly flicks as starting openclaw ( please wait this may take a moment) is on the screen
Anyone ever had this issue and resolved it.
I use openclaw outside of umbrel on an rpi5 - really don’t need it messing with my wallet on the machine!
But are you talking about restarting the container in umbrel, or restarting the gateway. This version is a fair part behind the current version by a few weeks and they literally update openclaw every other day.
Hi,
did you find a solution as I have the same issue, updated openclaw to 1.7.26 and it says starting open claw but browser flickers and just keeps repeating?
hey, i was able to reproduce this on an older version. basically the page keeps refreshing while the openclaw gateway is trying to start, so thats where the flickering comes from.
can you check the openclaw page in the app store and see what exact version it shows? the latest one should be 2026.7.1-1, the -1 at the end matters. if its older, update it and restart the app once. dont uninstall it.
if you’re already on that exact version and it still happens, share the openclaw app logs here and i can try to figure out whats keeping the gateway from starting.
Hi
2026.7.1-2 is version.
I reverted back to a June build and it worked. Just updated to above and got the same issue as last time, won’t connect, refreshes and keeps trying to connect.
Logs are: ignore brave issue that’s not the problem. Asked ai and it says it’s a migration issue… ran doctor fix in openclaw terminal of umbrel no fix…
Any help appreciated will need to go back to June version again if no solution.
umbrel_openclaw_2026-08-13_13-04.log (56.0 KB)
ok, the new log clears this up. the brave/codex notice isnt what is stopping it.
2026.7.1-2 sees the old short-term recall JSON and existing rows in SQLite, but it never compares them. it treats that situation as fatal and keeps restarting the gateway. doctor --fix runs the same broken check, which is why it didnt help. this is the upstream issue: [Bug]: additional legacy-state migration sources still block gateway startup after #102780 (Matrix, Memory Core, update-check state, Codex sidecar ownership) · Issue #103076 · openclaw/openclaw · GitHub
for a reversible workaround, run this in the same OpenClaw terminal:
mv /data/.openclaw/workspace/memory/.dreams/short-term-recall.json \
/data/.openclaw/workspace/memory/.dreams/short-term-recall.json.migrated-$(date +%Y%m%d-%H%M%S)
then restart OpenClaw from Umbrel. this leaves the SQLite database untouched and keeps the old JSON under a timestamped name, so dont delete that backup or uninstall the app.
i reproduced the exact failure on the 2026.7.1-2 Umbrel image and verified that this brought the gateway and Control UI back up. the proper upstream fix compares the two stores and is merged, but it isnt in the current stable package yet: fix(state): converge legacy startup migrations by steipete · Pull Request #107002 · openclaw/openclaw · GitHub
Aides
Thank you Sir!! Back up and running, no idea of why or how but I appreciate your help, thank you thank you!
Vain