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:

Issue	How 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 error	Make sure that origin host header matches the host from the environment variable FABRICATE_HOST.
After signup, Fabricate returns a 500 Internal Server HTTP error	Check 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.