"curl: (22) The requested URL returned error: 429" not going away

Troubleshooting
1

Hello there! I’ve enabled now Docker container one day ago. Somehow, probably due to misconfiguration, it created a burst of registrations (I saw nearly 7 new devices registered). I removed all those orphan devices, but now I’m getting this:
[remote-it-malynka] INFO: Pulling container remoteit/remoteit-agent:latest …
[remote-it-malynka] INFO: Pulling complete!
[remote-it-malynka] INFO: Starting container remote-it-malynka…
[remote-it-malynka] INFO: Container remote-it-malynka started!
[remote-it-malynka] INFO: Command block not found in container configuration
[remote-it-malynka] INFO: Waiting for container to start …
[remote-it-malynka] INFO: Container is now running!
[remote-it-malynka] INFO:
[remote-it-malynka] INFO: * /proc is already mounted
[remote-it-malynka] INFO: * /run/openrc: creating directory
[remote-it-malynka] INFO: * /run/lock: correcting mode
[remote-it-malynka] INFO: * /run/lock: correcting owner
[remote-it-malynka] INFO: /sbin/rc-update
[remote-it-malynka] INFO: Service ‘machine-id’ needs non existent service ‘dev’
[remote-it-malynka] INFO: OpenRC 0.55.1 is starting up Linux 6.11.4-301.fc41.aarch64 (aarch64) [LXC]
[remote-it-malynka] INFO:
[remote-it-malynka] INFO: * Caching service dependencies … [ ok ]
[remote-it-malynka] INFO: /sbin/rc-update
[remote-it-malynka] INFO: curl: (22) The requested URL returned error: 429
[remote-it-malynka] INFO: curl: (22) The requested URL returned error: 429
[remote-it-malynka] INFO: curl: (22) The requested URL returned error: 429
[remote-it-malynka] INFO: curl: (22) The requested URL returned error: 429
[remote-it-malynka] INFO: curl: (22) The requested URL returned error: 429
[remote-it-malynka] INFO: curl: (22) The requested URL returned error: 429
[remote-it-malynka] INFO: curl: (22) The requested URL returned error: 429
[remote-it-malynka] INFO: curl: (22) The requested URL returned error: 429

I waited for nearly a day, but the problem still persists. I already tried re-generating a registration code, re-created docker container, took a pause, but nothing helped so far :frowning:

Did I get banned?

2

When you get a 429 error it is a too many requests error which means you are generating too many requests in a short period of time. This is averaged over a 5 minute period of time.

Are you still having this issue?

3

I’ve removed everything, put down host for a few hrs, then created and configured container again. And the problem is finally gone.

Thanks for the reply and support!

1 Like
4

I just wanted to add that if for some reason the remoteit docker container was flapping that it would cause this rate limit problem. For example, the docker container was set to restart always and for some reason it was crashing on start then every time it restarts it would try to register again. This would rate limit you with a 429.