Skip to content

FAQ & security ​

General ​

Why do I get rate-limited (429) by Instagram? ​

Instagram fingerprints HTTP clients. gra uses wreq with Chrome TLS emulation, which normally passes, and pauses between paginated requests (ig_delay_ms). Many accounts on short intervals from a datacenter IP will still hit limits. Keep intervals reasonable (≥ 5 minutes) and max_concurrent_checks low. A rate-limited account is reported once and retried on its normal interval.

Why are my stories not delivered? ​

Stories need cookies of an Instagram account that can see them (it usually has to follow the target), and the session must be valid. Check /whoami and /cookies, make sure stories are enabled for the account, and look in the daemon log for the story fetch error. Story failures don't fail the check.

Why don't I see old posts after adding an account? ​

No backfill is intentional: only content published after the account was added is delivered.

Either videos are turned off for that account (⚙️ Settings → 🎬 Videos), or the file exceeds Telegram's bot upload limits (10 MB photos, 50 MB videos). The caption and link are delivered with a note explaining why.

What does "Auto" mean for cookies? ​

The account's credentials resolve to your ⭐ default set, then the server's first 🌐 set, then anonymous. Link a specific set, or None, in ⚙️ Settings → 🔑 Cookies.

How much stats data is kept? ​

One row per change of the counters, so accounts that rarely change take almost no space. Turn 👥 Stats off per account to stop recording.

I upgraded and the daemon refuses my database ​

The schema is versioned and older databases are not migrated. Point db_path to a new file (or move the old one away) and add your accounts again.

Security ​

Where are my cookies stored? ​

In the SQLite database (cookie_sets table), sent only to Instagram, and never logged. Protect the database file like a password store.

Can the bot token leak through logs? ​

No. Telegram request errors are stripped of their URL (which contains the token) before being logged. Set log_level = "debug" only temporarily; the rotating log_file keeps at most 7 files.

Should I run a public instance? ​

If strangers can reach the bot, restrict it:

toml
allowed_user_ids = [11111111, 22222222]   # everyone else is refused

/whoami shows your Telegram id. Even on an open instance, users can only see and change their own accounts and cookie sets; the server's 🌐 sets are usable but never shown in full.

Is this affiliated with Instagram? ​

No. gra is an independent, unofficial tool built on Instagram's web APIs. Content belongs to its owners: archive only what you are allowed to access and respect Instagram's Terms of Use.

Troubleshooting ​

The bot doesn't answer ​

  • Check that gra is running and the log shows connected as @....
  • Only one instance may poll a bot. A second one gets HTTP 409 conflicts.
  • Long polling and webhooks are exclusive; the daemon removes any webhook on start.

useragent mismatch errors ​

Instagram binds sessions to the browser. In /login, send the exact User-Agent of the browser the cookies were exported from. Sending the same cookies again with a new User-Agent updates the set in place.

Where are the logs? ​

log_file (daily rotation, 7 kept) or stderr. Users also get one notice per failing account in the bot.

Released under the MIT License. Not affiliated with Instagram or Meta.