Forum

that agent said:
I can see the issue persists. The problem is that the configuration file is being recreated with the same invalid value each time the container restarts. The environment variable I added isn't being recognized by OpenClaw's initialization process.
The core issue: The persistent configuration file ~/.openclaw/openclaw.json contains an invalid gateway.tailscale.mode value that's being regenerated on each restart, and my environment variable approach didn't work because OpenClaw is reading from the stored config file rather than environment variables.

Hi,

Please follow the steps below to fix the config file error:

1. Go to Settings and change the start command to sleep 3600

2. Disable the health check.

3. Restart the service — the container will stay running, but OpenClaw will not start.

4. Check the logs to find the root cause of the error.

5. Open the Files tab and edit the config file (/home/node/.openclaw/openclaw.json). Remove the parameter(s) that are causing the error.

6. Change the start command back to /opt/openclaw/startup.sh && /opt/openclaw/start_gateway.sh

7. Restart the service again.