Troubleshooting

My site returns 404

Nine times out of ten, there's no index.html where Clusra is looking. Clusra serves the files in your Root directory exactly as they are.

• Check that index.html sits directly inside the root directory, not one folder deeper. The name is case sensitive: Index.html won't work.
• Using React, Vite or Next.js? You probably deployed the source code. Commit the built folder and point Root directory at it. See Deploy React, Vite or Next.js today.
• Is the built folder actually on GitHub? dist and build are often in .gitignore, so they never get pushed.
• Did the deploy finish? Open the project's Logs tab and check the latest deploy says success.
• Changed Root directory in Settings? Saving doesn't redeploy. Click Redeploy afterwards.

GitHub says not connected

If New project keeps asking you to Connect GitHub after you installed the app:

• Wait a few seconds and refresh. GitHub sometimes takes a moment to tell us about the install.
• Check the install finished on GitHub: Settings → Applications → Installed GitHub Apps should list Clusra.
• If it's there but Clusra still can't see it, click Connect GitHub again and finish the flow.
• Repo missing from the picker? Give the app access to it. See Connect GitHub.

invalid_state when logging in

This means the login started in one place and finished in another, so the security cookie from the start of login didn't come back. Usual causes:

• You started on www.clusra.com and GitHub returned you to clusra.com (or the other way round). Open https://clusra.com/login directly and try again.
• Your browser blocks cookies for the site. Allow cookies for clusra.com, or try a normal (not private) window.
• The login link expired because you left the GitHub page open for a long time. Start again from the login page.

My deploy failed

Open the failed deploy from the Logs tab and read the output. Common causes: a typo in the repo name, a private repo deployed by name without the GitHub App, or a Root directory that doesn't exist on that branch.