Troubleshooting

My service never becomes ready

By far the most common first-deploy problem, almost always one of two things:

1. Your app isn't reading PORT from the environment. Infrly assigns a port at deploy time and your app has to bind to it — a hardcoded port (3000, 8080, whatever your framework's default is) will never match what Infrly is actually checking. See Build & Start Commands.
2. A Health Check Path is set, but your app doesn't actually serve 2xx/3xx there. If you haven't explicitly set one, Infrly only checks that something is listening on the port at all (no path involved) — if it's still failing with no Health Check Path set, this isn't your cause; see #1 instead. If you have set one, confirm that exact path really returns success on a working local run of your app. See Deploy a Web Service.

The deployment log includes your app's own recent output when this happens — that's usually the fastest way to see the real error (a crash on boot, a missing dependency, a stack trace) rather than guessing.

My build fails installing dependencies / running the build command

The build log tags every line with the phase it happened in, so start by checking which one failed:

• Failed installing — usually a missing/misnamed dependency, a lockfile out of sync with package.json (or your runtime's equivalent), or a dependency that needs a system library the base image doesn't have.
• Failed building — usually a real compile/type error in your code, or a build command that assumes a file/env value that isn't actually there in this environment.

Confirm the command Infrly is actually running matches what you expect — a copy-pasted install/build command from a different project, or a typo, is a common cause that isn't obvious from the error text alone.

"Not enough resources left in this project to deploy this service"

Each project has a total CPU/memory capacity shared across every service in it, sized generously for a normal project's worth of services. This error means the services already running in that project (each web service, each database — a PostgreSQL database's high-availability setup counts as roughly double its listed plan size, see PostgreSQL) are using all of it, and the service you're trying to deploy doesn't fit in what's left.

To fix it: delete or downsize another service in the same project to free up capacity, then deploy again. If you're confident the project genuinely has room (for example, you're redeploying a service that was already running at the same size, not adding a new one), and you still hit this, reach out — that's worth us looking at directly rather than working around.

My Static Site can't reach my backend

Almost always: the backend URL was set in the service's Environment Variables panel instead of directly in the Build Command. A Static Site's build never receives dashboard-configured environment variables — see Deploy a Static Site for the exact fix.

My frontend gets a CORS error calling my backend

If your frontend and backend are separate services (each with its own *.infrlyapp.com URL, even in the same project), a browser request between them is cross-origin — your backend needs to send CORS headers allowing it. Most frameworks have a one-line CORS middleware for this (e.g. Express's cors package). This isn't something Infrly can configure on your behalf, since it depends on which origins your app wants to allow.

A deep link / client-side route 404s

• Static Site — this shouldn't happen; Infrly falls back to your index.html for any path that isn't a real file, specifically so client-side routers work on a hard refresh. If you're still seeing a 404, double check your Output Directory is actually correct (see Build & Start Commands).
• Web Service — this is on your app, not Infrly: your server needs its own catch-all/fallback route serving the app shell for unknown paths, the same as you'd need running it anywhere else.

Where to look first

• A build or startup failure → the deployment's own log (tagged by phase).
• Your app is up but behaving wrong → its runtime log.
• Neither shows anything useful → double check you're looking at the latest deployment, not a previous one.