When Your Self-Hosted Nitter Instance Gets Banned

说明与用途

自动化健康检查和保守的 IP 轮换策略可让自托管 Nitter 实例持续运行数月，避免昂贵的代理池。

问题

Self-hosted Nitter instances often silently stop working due to soft bans or rate limits from Twitter, leaving operators unaware until users notice empty timelines.

结果

A robust, automated health check and conservative IP rotation strategy keeps a self‑hosted Nitter instance operational for months, reducing downtime and avoiding costly proxy pools.

工作流

• 1. Write a Python health‑check script that fetches a known active profile (e.g., NASA) and verifies the presence of timeline items and body size.
• 2. Run the script from a different host (e.g., a $4 VPS) to avoid shadow‑banning.
• 3. Configure systemd unit and timer files to execute the script every 5 minutes with persistence across reboots.
• 4. Monitor alerts via healthchecks.io or a Discord webhook.
• 5. Use a small number of clean VPS IPs with spaced requests (2–5 s) instead of a residential proxy pool.
• 6. Keep the instance private or rebuild a public mirror from an image when it dies.

证据

The script probes a known-active account (NASA is a safe pick because it posts often) and rejects any response shorter than 5KB or missing the timeline-item class.

来源

A cheap residential proxy pool will get your entire /24 flagged within a week.

来源

One or two VPS endpoints from a reputable provider, with request spacing of 2 to 5 seconds, will last months.

来源