A push fails or does nothing
Cipher checks four conditions before it will start a push, and reports which one failed rather than failing generically.
Push is disabled
| Reported | Fix |
|---|---|
| Source folder not found | The folder moved or was renamed. Update it in the project’s General pane. |
| Frontend folder not found | Same, for the attached frontend build. Often a dist/ that was cleaned and not rebuilt. |
| No environment selected | Attach an environment to the project first. |
| No serving domain | Add a domain for that environment. The interpreter routes by Host header, so it needs to know which requests belong to this project. |
Push succeeds but the site is unchanged
Almost always a build that was not rebuilt. LockFlare packs the folder as it stands at the moment you push — it does not run your bundler. Run your build, then push again and check the version hash changes.
If the hash is identical, the content is identical, and the problem is upstream in your build.
Push succeeds but the server serves an error
The build reached the server and failed to start. Check the engine logs — the application’s own startup error appears there.
Common causes on a first deploy, all covered in Known Limitations:
- Node: a bare
require()for a package outside the shared set. Bundle it into the artifact. - Node: code writing to a local file at startup — a log file, a cache directory, SQLite.
- .NET: outbound network not enabled for that environment, so the first database call fails.
- .NET: code reading
Assembly.Locationor building a path from it. - Either: the starting file is not the file that actually launches your server.
Only some servers picked it up
A push fans out to every server in the environment and each confirms independently. If one did not, that machine is still serving the previous build and the environment is no longer uniform.
Check it in Monitoring — an unreachable server is the usual cause. See A server will not come online.