> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/fabricate/self-hosting-fabricate/deploying-and-managing-a-self-hosted-instance/using-docker-compose/troubleshooting-a-docker-compose-deployment.md). # Troubleshooting a Docker Compose deployment Here are common issues you might run into when you use Docker Compose to set up a self-hosted Fabricate instance, with suggestions for how to troubleshoot them:
IssueHow to troubleshoot
Container fails to start

Inspect the logs:

  • docker compose logs -f db
  • docker compose logs -f web
Fabricate host is not reachable through HTTP or HTTPS

Make sure that:

  • The DNS points to the correct destination with host fabricate.example.com and isn't cached by your resolver.
  • The load balancer or proxy listens on 80 or 443.
  • The firewall or security group allows inbound traffic on 80 and 443.
  • Fabricate responds locally to wget http://127.0.0.1:3000.
  • Fabricate's healthcheck path returns a 200 status from wget http://127.0.0.1:3000/up.
Fabricate returns 403 Forbidden HTTP errorMake sure that origin host header matches the host from the environment variable FABRICATE_HOST.
After signup, Fabricate returns a 500 Internal Server HTTP errorCheck the logs for errors.

The SMTP server might be misconfigured, and Fabricate failed to send the invitation email.
Load balancer returns 502 Bad Gateway HTTP error

Make sure that:

  • The Fabricate web container is running and listening. The load balancer might be ready to accept traffic, but Fabricate might still be starting. Wait a few seconds after the first start.
  • The load balancer terminates the TLS handshake at the edge and proxies requests to the Fabricate web container over HTTP locally and over private VPC for the last mile. For full end-to-end encrypted communication with the web container, you must provide and configure a certificate that is signed by a trusted CA. Refer to the .env template.
JS execution fails with: idfd_getfd(pidfd, 4) - Operation not permitted (os error 1)

Make sure that:

  • All required syscalls are exposed to the container using cap_add.
  • The container uses the default runc Docker runtime. Refer to the docker-compose.yml template.
--- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.tonic.ai/fabricate/self-hosting-fabricate/deploying-and-managing-a-self-hosted-instance/using-docker-compose/troubleshooting-a-docker-compose-deployment.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.