#Main agent UI on Hostinger OpenClaw does not persist changes

1 messages · Page 1 of 1 (latest)

hoary copper
#

Hi all,

I am using the Hostinger OpenClaw plan with the OpenClaw Docker container and I have been running into several issues.

First, for around two weeks now, there seems to be a newer update available, but I have not been able to update my instance successfully. I already tried updating both through the Hostinger interface and through the console, but neither worked.

Second, I seem to have a persistence problem in the UI, especially with the main agent setup. For example, when I tell the system to delete certain API keys, it says the change was made, but after rebooting the VPS, the keys are there again. So from the UI it looks as if the change was successful, but in practice it is not being persisted correctly. This makes it hard to trust changes made through the main agent workflow.

As a workaround, I installed Claude Code directly on the VPS, and there things work better. But honestly, I do not really want to manage everything through the CLI. My actual goal is to use the main agents in the OpenClaw UI, not to do manual command-line work for basic management tasks.

So I wanted to ask:

  • Has anyone else seen update problems on the Hostinger OpenClaw plan?
  • Has anyone experienced persistence issues in the UI, especially with deleted API keys or settings coming back after a reboot?
  • Is there a known fix for this, or is the Hostinger container setup currently broken in some way?

Would really appreciate any tips or experiences.

Thanks a lot.

maiden gustBOT
tranquil archBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

late mapleBOT
#

This does not sound like expected behavior.

A few concrete things:

  • On Docker installs, openclaw update inside the container is usually not the right update path. For Hostinger VPS, the docs say updates should come from Docker Manager → Update. For 1-click managed, Hostinger handles updates.
    https://docs.openclaw.ai/install/hostinger

  • There was a Docker-side bug where the UI kept showing “update available” even when the latest image was already running, so the banner itself may be misleading.

  • For the API keys coming back after reboot, the 2 most likely causes are:

    1. the key is coming from Hostinger/Docker env vars (OPENAI_API_KEY, ANTHROPIC_API_KEY, etc.), so deleting it in the UI removes only the stored profile, but restart brings the env-backed credential back
    2. the container is not persisting /home/node/.openclaw, so auth-profiles.json and config get reset on restart

Per the Docker docs, persisted state should live under /home/node/.openclaw, including:

#

So I would check these first:

  1. Which Hostinger product is this exactly?

    • Managed 1-click OpenClaw
    • VPS + Docker Manager

  2. Paste:

    openclaw --version
openclaw status --all
openclaw gateway status

  3. In Hostinger/Docker Manager, check whether those API keys are also set as environment variables.

  4. Verify the container has persistent storage mounted for /home/node/.openclaw.