Diagnose and fix FireCrawl common errors and exceptions. Use when encountering FireCrawl errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "firecrawl error", "fix firecrawl", "firecrawl not working", "debug firecrawl".
View on GitHubjeremylongshore/claude-code-plugins-plus-skills
firecrawl-pack
plugins/saas-packs/firecrawl-pack/skills/firecrawl-common-errors/SKILL.md
February 1, 2026
Select agents to install to:
npx add-skill https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/main/plugins/saas-packs/firecrawl-pack/skills/firecrawl-common-errors/SKILL.md -a claude-code --skill firecrawl-common-errorsInstallation paths:
.claude/skills/firecrawl-common-errors/# FireCrawl Common Errors
## Overview
Quick reference for the top 10 most common FireCrawl errors and their solutions.
## Prerequisites
- FireCrawl SDK installed
- API credentials configured
- Access to error logs
## Instructions
### Step 1: Identify the Error
Check error message and code in your logs or console.
### Step 2: Find Matching Error Below
Match your error to one of the documented cases.
### Step 3: Apply Solution
Follow the solution steps for your specific error.
## Output
- Identified error cause
- Applied fix
- Verified resolution
## Error Handling
### Authentication Failed
**Error Message:**
```
Authentication error: Invalid API key
```
**Cause:** API key is missing, expired, or invalid.
**Solution:**
```bash
# Verify API key is set
echo $FIRECRAWL_API_KEY
```
---
### Rate Limit Exceeded
**Error Message:**
```
Rate limit exceeded. Please retry after X seconds.
```
**Cause:** Too many requests in a short period.
**Solution:**
Implement exponential backoff. See `firecrawl-rate-limits` skill.
---
### Network Timeout
**Error Message:**
```
Request timeout after 30000ms
```
**Cause:** Network connectivity or server latency issues.
**Solution:**
```typescript
// Increase timeout
const client = new Client({ timeout: 60000 });
```
## Examples
### Quick Diagnostic Commands
```bash
# Check FireCrawl status
curl -s https://status.firecrawl.com
# Verify API connectivity
curl -I https://api.firecrawl.com
# Check local configuration
env | grep FIRECRAWL
```
### Escalation Path
1. Collect evidence with `firecrawl-debug-bundle`
2. Check FireCrawl status page
3. Contact support with request ID
## Resources
- [FireCrawl Status Page](https://status.firecrawl.com)
- [FireCrawl Support](https://docs.firecrawl.com/support)
- [FireCrawl Error Codes](https://docs.firecrawl.com/errors)
## Next Steps
For comprehensive debugging, see `firecrawl-debug-bundle`.