Start with the documentation at misiektoja.github.io/instagram_monitor. Installation, Setup & First Run and Configuration cover most first-run problems, and Troubleshooting covers the rest.
The tool diagnoses itself. Run it before asking anything, and include its output when you do:
instagram_monitor --doctorIt checks the environment, configuration, session, targets, notifications and connectivity, and names the line number and reason for anything invalid.
Instagram challenges, sudden empty results or a flagged session are usually anti-detection problems rather than bugs. Anti-detection explains what triggers them and how to recover.
| You want to | Go to |
|---|---|
| Ask a question or discuss an idea | Discussions |
| Report something broken | Bug report |
| Request a capability | Feature request |
| Report a vulnerability | Private security advisory, never a public issue |
| Contribute a change | CONTRIBUTING.md |
Include the version, how you installed it (PyPI, manual script or Docker), your operating system, whether you use a logged-in session and the --doctor output. Run the failing command with --debug and attach the relevant part of the log.
Never post session cookies, Instagram or SMTP passwords, webhook URLs, ntfy tokens or a complete configuration file. Redact monitored usernames if they matter to you. See SECURITY.md.
This is a project maintained in spare time, so replies are best effort with no response time attached. Only the latest release receives fixes, as SECURITY.md describes, so reproduce the problem on the current version before reporting it.
If the project is useful to you, you can support its development through GitHub Sponsors or Buy Me a Coffee.