The Movie Database Support
Support → API Support
Request Count is over allowed limit of (40)
posted by EazyshawnSTAFFMOD on August 29, 2017 at 5:35 PM
Hello, im going to the following url in my browser https://api.themoviedb.org/3/movie/550?api_key=
but i am getting the follow error, {"status_code":25,"status_message":"Your request count (1901) is over the allowed limit of 40."}
The request count increases everytime i refresh my browser and eventually resets back to a number below 40, then refreshing my browser jumps the request count back to 100+
Any ideas what might be going on?
Thank you, Shawn
Reply by twnage23
on August 30, 2017 at 12:45 AM
{"ngx.var.remote_addr":"10.183.104.217"}
Reply by Travis Bell
on August 30, 2017 at 12:50 AM
Ya, so what's happening is either Nginx or ELB (I'm not entirely sure which) is creating pseudo ipv4 addresses created within the protected 10.x IP namespace. There's a little bit about this online but it's hard to get much information about. What's happening with these "fake" IP addresses is that a lot of you are sharing an IP address. I bet if you reload that debug URL, you might even get a different IP at different times.
I admit to not fully testing this because everything worked properly on the website but there's an important difference that I didn't think of which is CloudFront. We use CloudFront on the website and not the API.
I'm going to revert today's ipv6 change and disable it again on the API until this gets figured out. It might be another few hours before ipv6 is disabled properly on
api.themoviedb.org.You can try to use
api.tmdb.organd see if it makes any difference but I suspect it won't but it is something you can try.Reply by shaneqi
on August 30, 2017 at 12:52 AM
@travisbell Thank you for the investigation.
Reply by Travis Bell
on August 30, 2017 at 1:19 AM
ipv6 should be disabled on
api.themoviedb.orgonce more.Reply by shaneqi
on August 30, 2017 at 1:21 AM
api.themoviedb.org and api.tmdb.org both are back working for me.
Reply by brent4w
on August 30, 2017 at 1:22 AM
{"ngx.var.remote_addr":"76.210.202.101"} ... as requested. It is working now for me. Thanks again.
Reply by tmdb26695382
on August 30, 2017 at 2:41 AM
Normalized for me, thanks for the great service.
Reply by Sterling Diaz
on January 9, 2019 at 9:07 PM
Same problem here. Any solution so far?
Reply by Travis Bell
on January 9, 2019 at 9:26 PM
@sterlingdiazd Please create a new thread and discuss the issue you're having in detail. ipv6 has not been re-enabled on the API and that was the problem being discussed in this thread.
Thanks!