Cause: Scraping too many pages rapidly from a datacenter IP.
Solution:
The built-in scraper has automatic exponential backoff with jitter and pauses before retrying.
If a scrape run halts due to rate limits, it is marked as Resumable. You can click Resume Scrape anytime from the Scrape page to continue from the exact page where it stopped without duplicating posts!
Fix: Ensure MongoDB container is healthy. Verify DATABASE_URL=mongodb://mongo:27017/instagram?replicaSet=rs0&directConnection=true is set in the app container.
Cause: Prisma uses MongoDB transactions for multi-document operations and profile initialization, requiring a replica set (rs0).
Fix: Ensure your MongoDB container runs with --replSet rs0 and has been initiated via rs.initiate(). The included docker-compose.yml, dokploy-compose.yml, and coolify-compose.yml templates automatically configure and initialize this on first startup. If running MongoDB manually, execute:
Explanation: Instagram URLs include temporary CDN tokens that expire after several days.
Fix: Connect a free Cloudinary account in Settings → Cloudinary CDN (or during initial Onboarding) and run Sync All Media to permanently mirror all media assets to Cloudinary.
Q: Can I run multiple Instagram accounts?
A: Yes! Click on the profile switcher in the top navigation or sidebar to create additional profiles. Each profile maintains its own session cookie, bookmarks, timeline, and scrape runs independently.
Q: Will scraping get my Instagram account banned?
A: The scraper operates in read-only mode, only requesting the /feed/saved/ endpoint at human-like intervals. However, using a secondary burner account to save posts is always good practice.
Q: Can I export my saved accounts to CSV?
A: Yes! On the Accounts page, click Export CSV to download a complete spreadsheet of all discovered accounts, follower status, verification, and saved post counts.
