Fixed "Instance has no auth tokens, or is fully rate limited." error #1278
Description
I started up a new Nitter service on a VPS (after setting up a new account with 2fa per instructions) and immediately got " Instance has no auth tokens, or is fully rate limited."
Docker log showed:
Fetch error, API: search, errors: (errors: @[(code: locked, message: "Authorization: Denied by access control: To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.")])
At first I thought the problem might be an auth issue related to a newly created account. However, after unlocking my account and some experimenting, I found that reducing httpMaxConnections in nitter.conf from default value of 100 to 5 fixed the issue. It's working as expected now.
Hope this helps someone. Perhaps the default value for httpMaxConnections in the example .conf file should be changed?