Troubleshoot space loading
“Backend unreachable” means the product could not complete the API requests needed to restore your spaces.
“Backend unreachable” means the product could not complete the API requests needed to restore your spaces. It does not mean the space was deleted.


The example shows the space remaining visible while Formist reports that the space list could not be refreshed. Treat the message as a connectivity or backend-state problem, not evidence that the displayed space has been deleted.
Check the scope of the failure
- Open the public health page or the API health endpoint used by your deployment.
- Confirm that Login works and note whether all spaces fail or only one.
- Verify that the frontend is using the correct API base for the selected region. Formist can route different spaces to different regional backends.
- Retry after the backend, database, and Redis are healthy.
If one space fails
The space may point to an unavailable region, the membership may have changed, or a space-scoped request may be failing. Return to the space picker and try another accessible space. Ask an Admin to verify membership and regional routing.
Local development
Start PostgreSQL and Redis, apply migrations, start the API, then start Vite with its API base configured. Use a consistent loopback host for frontend and backend so session cookies and SSE use the same browser context.
Avoid creating replacement spaces until the existing database and region have been checked.
Frequently asked questions
Does "Backend unreachable" mean my space was deleted?
No. It means the product could not complete the API requests needed to restore your spaces; it does not imply the displayed space was deleted.
Why does only one of my spaces fail to load?
A single failing space usually points to an unavailable region, a changed membership, or a failing space-scoped request, not a platform-wide outage. Try another accessible space and ask an Admin to check membership and regional routing.
What should I check before retrying?
Confirm Login still works, note whether all spaces fail or only one, and verify the frontend is using the correct API base for the selected region before retrying.
Last verified: