Getting "Too Many Requests" error with Inoreader
I added my Inoreader account to NNW 6 on my Mac yesterday, and all was going well until this morning when I tried doing the same from my iPad (running the NNW 6 TestFlight). At first it successfully synced all of my feeds, but now NNW on all of my devices show some variant of the "Too many requests" error:
I only have ~30 feeds, so I don't think I'm really pushing the boundaries of usage patterns.
That error happens when all users of NetNewsWire combined have exceeded the API limit. I just tested it and it seems to be working fine now. In the past Inoreader has had to bump that limit up for us.
Is it working for you now?
I'm getting the same error with Inoreader right now.

Oops. My successful test was invalid. I forgot that I have a different set of API keys for Inoreader than the public build of NetNewsWire has.
@brentsimmons I think we need to contact Inoreader about getting our API limits increased.
FWIW it's working as expected for me now. Not sure if Brent/someone was able to talk to Inoreader and get the API limit bumped, or if we're running into some 24 hour rotating window based on UTC or something. I guess if it's broken again tomorrow morning (PST) then that'll be a strong hint.
Confirmed: at around 15:30 UTC today I’m seeing the same “Too many connections” error message, while it was fine when I last commented at around 05:00 UTC.
Inoreader has increased our API limit, so this should be resolved (for now).
Additionally, we've made a change that is coming in 6.0.2 for Mac and the next iOS beta that reduces API usage for Inoreader.
Looks like this issue may be back, unfortunately. Just started seeing the same error this morning on my Inoreader-synced devices.
Same here.
I hadn't checked in a few hours, but I just reloaded NNW and, as of this writing, the issue is resolved. I'll keep an eye open to see if it crops up again and will comment here if so.
Is there anything additional that would be helpful? Any logs to collect or such?
I was seeing this earlier today, but it has since resolved.