> For the complete documentation index, see [llms.txt](https://docs.lingoql.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lingoql.com/introduction/troubleshooting-deploys.md).

# Troubleshooting Deploys

LingoQL deploy troubleshooting follows the same shape most PaaS platforms do.

Problems usually fall into one of four buckets:

* the app does not build
* the app builds but does not stay up
* the custom domain does not resolve cleanly
* the repository is too large to clone

### Buildpacks on LingoQL

LingoQL supports two buildpacks:

* `Railpack` — the default option
* `Nixpacks` — the alternative option

LingoQL can deploy any app supported by these buildpacks.

If one buildpack fails to detect or build your app correctly, switch to the other one and redeploy.

Useful references:

* [Railpack docs](https://railpack.com)
* [Nixpacks configuring builds guide](https://nixpacks.com/docs/guides/configuring-builds)

### Start with these checks

1. Confirm the app builds locally in production mode.
2. Confirm the app starts with the same environment variables used in production.
3. Confirm the process binds to `HOST:$PORT`.

LingoQL injects both `HOST` and `PORT` at runtime.

If your framework requires a literal host value, bind to `0.0.0.0` and read `PORT`.

### Troubleshooting guides

* [Deploy checklist](/introduction/troubleshooting-deploys/deploy-checklist.md)
* [Build failures](/introduction/troubleshooting-deploys/build-failures.md)
* [Runtime and startup failures](/introduction/troubleshooting-deploys/runtime-and-startup-failures.md)
* [Custom domains and DNS](/introduction/troubleshooting-deploys/custom-domains-and-dns.md)
* [GitHub cloning limits](/introduction/troubleshooting-deploys/github-cloning-limits.md)
* [Services you can deploy](/introduction/services-you-can-deploy.md)

### The usual recovery flow

1. Read the first failing line in the logs.
2. Fix the build, startup, DNS, or repository issue it points to.
3. Redeploy after each change so you isolate the real cause.

{% hint style="info" %}
A failed deploy does not replace a healthy one. Fix the issue, then redeploy.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lingoql.com/introduction/troubleshooting-deploys.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.