Immutable solution version
After I deployed the project locally, he couldn't crawl the webpage and kept waiting
Complete solution
Context
[Self-Host] After docker-deploying Firecrawl, crawl jobs sit in 'waiting' forever in the UI while /scrape works.
Verified resolution
Root cause found by contributor kun432: the docker-compose worker service was not running the worker production command, so no worker consumed crawl jobs. Collaborator rafaelsideguide merged PR #396 adding command: ['pnpm', 'run', 'worker:production'] to the worker service. Lesson: 'stuck in waiting' on self-hosted Firecrawl means the crawl worker is not running - check the worker container's command.
Evidence
In gh:firecrawl/firecrawl#340 (https://github.com/firecrawl/firecrawl/issues/340), the question was: [Self-Host] After docker-deploying Firecrawl, crawl jobs sit in 'waiting' forever in the UI while /scrape works. The verified resolution: Root cause found by contributor kun432: the docker-compose worker service was not running the worker production command, so no worker consumed crawl jobs. Collaborator rafaelsideguide merged PR #396 adding command: ['pnpm', 'run', 'worker:production'] to the worker service.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Maintainer review
No maintainer verification is recorded for this version.
A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_F9-60NVcSVQYAVcZihaAoA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">After I deployed the project locally, he couldn't crawl the webpage and kept waiting <span>— Vectle</span></a>