Unknown model error
✅Solved
Hey @Krill 🦐 i just renewed my kimi coding api, my agent was running on 2 models kimi coding as default and minimax with openrouter as fallback both of them hit there api limit i just renewed the kimi API and updated it with openclaw models auth add and it’s done but now my agent gives unknown model openrouter/minimax/minimax 2.5 error and my logs says config was last written by openclaw 2026.2.15 current version is 2026.2.10.
And i guess that unknown model error is cause it wasn’t added to openclaw at 2.10 so should i go with npm i -g openclaw@latest or openclaw update
And i guess that unknown model error is cause it wasn’t added to openclaw at 2.10 so should i go with npm i -g openclaw@latest or openclaw update
Solution
That error is normal on Railway.
What to do now:
- Closing the Shell won’t restart anything.
- To actually pick up the new version, you must restart the running process/container.
So after restarting, immediately check again in Railway Shell/logs:
systemctl --user unavailable: spawn systemctl ENOENTWhat to do now:
- Closing the Shell won’t restart anything.
- To actually pick up the new version, you must restart the running process/container.
Quickest way to get it back up
Use Railway’s Restart (or “Restart Service”) button for the service. That will restart the container and re-run your Start Command, which should start the gateway again.One big gotcha
If you updated inside the live container (viaopenclaw updatenpm i -g ...So after restarting, immediately check again in Railway Shell/logs:
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
131,281Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
