Have you tried restarting the deployment?

Hi!

Since your app worked before and now fails without code changes, this points to a Railway volume or permissions issue rather than a Flowise bug.

Flowise needs a writable database for login and session data, but it sounds like your SQLite file or Railway volume is currently read‑only. To possibly fix this:

Store the .db file in a persistent volume, not ephemeral storage.

Make sure the volume is mounted with write access (rw).

Check file ownership inside the container, Flowise must be able to write to the file.

As the previous commenter mentioned, restarting or redeploying with a fresh volume often resolves the issue.

This does not sound iike a system‑wide problem, but a deployment setup issue.

Let me know if you have any more details to share.

Same problem here. Since I'm working with the "official" flowise template, could it be a problem of the template repo build configuration?
In the last two updates (each one has the same problem for me) i saw in the build log that this last action "RUN chown -R node:node ." took a very long time...