Firecrawl•2w ago

docker (firecrawl-api-container) debug

Hi guys, first time firecrawl user here. I just installed it using docker on my ubuntu ec2 instance. The docker compose build command ran without any issues and then i ran docker compose up -d which gave me this output:

[+] Running 4/4
 ✔ Container firecrawl-playwright-service-1  Running                                         0.0s
 ✔ Container firecrawl-redis-1               Running                                         0.0s
 ✔ Container firecrawl-nuq-postgres-1        Running                                         0.0s
 ✔ Container firecrawl-api-1                 Started

[+] Running 4/4
 ✔ Container firecrawl-playwright-service-1  Running                                         0.0s
 ✔ Container firecrawl-redis-1               Running                                         0.0s
 ✔ Container firecrawl-nuq-postgres-1        Running                                         0.0s
 ✔ Container firecrawl-api-1                 Started

I ran curl http://localhost:3002/test to check the status but i got this error: curl: (7) Failed to connect to localhost port 3002 after 0 ms: Couldn't connect to server. The container status was this: docker ps -a

CONTAINER ID   IMAGE                          COMMAND                  CREATED         STATUS                          PORTS                                       NAMES
bafad8e70a36   firecrawl-api                  "docker-entrypoint.s…"   7 minutes ago   Exited (1) About a minute ago                                               firecrawl-api-1
c40c420ee5e4   redis:alpine                   "docker-entrypoint.s…"   7 minutes ago   Up 7 minutes                    6379/tcp                                    firecrawl-redis-1
8d3aa0610267   firecrawl-nuq-postgres         "docker-entrypoint.s…"   7 minutes ago   Up 7 minutes                    0.0.0.0:5432->5432/tcp, :::5432->5432/tcp   firecrawl-nuq-postgres-1
1a79196b749f   firecrawl-playwright-service   "docker-entrypoint.s…"   7 minutes ago   Up 7 minutes                                                                firecrawl-playwright-service-1

CONTAINER ID   IMAGE                          COMMAND                  CREATED         STATUS                          PORTS                                       NAMES
bafad8e70a36   firecrawl-api                  "docker-entrypoint.s…"   7 minutes ago   Exited (1) About a minute ago                                               firecrawl-api-1
c40c420ee5e4   redis:alpine                   "docker-entrypoint.s…"   7 minutes ago   Up 7 minutes                    6379/tcp                                    firecrawl-redis-1
8d3aa0610267   firecrawl-nuq-postgres         "docker-entrypoint.s…"   7 minutes ago   Up 7 minutes                    0.0.0.0:5432->5432/tcp, :::5432->5432/tcp   firecrawl-nuq-postgres-1
1a79196b749f   firecrawl-playwright-service   "docker-entrypoint.s…"   7 minutes ago   Up 7 minutes                                                                firecrawl-playwright-service-1

It seems that the firecrawl-api container is dying even if i run the docker compose up -d command repeatedly. Can you guys please help me with this? I'd really appreciate it. Also please @ me if you're replying so that i can get notified. Thanks. 😄

4 Replies

Gaurav Chadha•2w ago

@codename-root could you please do docker logs bafad8e70a36 and did you also tried restarting the server? also please ensure the .env is correct.

codename-rootOP•2w ago

docker logs says this:

message.txt

codename-rootOP•2w ago

the .env file is a copy of the apps/api/.env.example file. i'll reboot the server now. @Gaurav Chadha I restarted my machine and ran docker compose up -d. Logs show this error:

worker       Can't accept connection due to RAM/CPU load
worker       2025-09-19 15:35:55 info [queue-worker:workerFun]: Can't accept connection due to RAM/CPU load
worker       2025-09-19 15:35:55 error [queue-worker:workerFun]: WORKER STALLED {"module":"queue-worker","method":"workerFun","cpuUsage":0.16624685138539042,"memoryUsage":0.8798459358843047}

worker       Can't accept connection due to RAM/CPU load
worker       2025-09-19 15:35:55 info [queue-worker:workerFun]: Can't accept connection due to RAM/CPU load
worker       2025-09-19 15:35:55 error [queue-worker:workerFun]: WORKER STALLED {"module":"queue-worker","method":"workerFun","cpuUsage":0.16624685138539042,"memoryUsage":0.8798459358843047}

i'm running a t3.small EC2 instance. I guess this is too weak to run this and i have to spin up a bigger instance?

amplitudes•2w ago

yeah, that’s not enough - you should be looking at 4c/4gb ideally

Gaming

Programming

docker (firecrawl-api-container) debug

Did you find this page helpful?