mysterious X-RateLimit headers

Hi, I have recently developed a site and due to the amount of resources that I load I am easily maxing out my designated limit (100).

I do not know what is creating these headers though seeing as I have since removed the limiter I had set in place. I was wondering if anyone knew if DigitalOcean imposes this on us and if they do how to increase the limit as 100 is too little for me.

I know that they’re being created on the hosting side of things seeing as when I host it locally they don’t appear.

(I am using a ubuntu server with nginx with a PM2 process manager and I have not created any ngx_http_limit_req_module.)

I also found this but don’t believe this has anything to do with the issue.

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi there,

Indeed the documentation link that you’ve shared is only referring the the DigitalOcean API.

Regarding the header that you are seeing, are you using CloudFlare or any other CDN provider? For example CloudFlare offer this as a service:

Also how did you install Nginx, can you share a link to the article that you followed?

Do you see that header when you try to access your Droplet’s IP address or does it only show for your domain name?

Regards, Bobby