We are getting {“error”:{“message”:“Access denied. Please check your network settings.”}} in our production servers.
We are using fly.io.
Fun way to spend Christmas eve.
Hi there, this happens between Cloudflare and the server making the API call — we block IP ranges from sanctioned countries, but sometimes Cloudflare’s rules get a bit eager.
Which Fly region(s) are you using - and could you please share the IP ranges of your Fly machine, and any network / cf-ray data you can get from the Fly machine?
For a quick fix: could you spin up another region and see if that one works?
I use Fly.io on my own projects and frequently makes calls to Groq without a problem, so this might be specifically related to your Fly machine instance’s region. Could you also reach out to Fly’s support to see if they have other Cloudflare issues with that region?
Not sure Fly.io uses Cloudflare. Our requests are leaving from Fly.io servers to Groq API.
Most our servers are in the states and some are in Germany, UK, Brazil and Australia.
Since then the API blocked over 5K requests.
This is probably Cloudflare blocking your fly.Not a code problem, but an io egress IP issue. A lot of the time, this happens when a region’s IP range gets flagged.
Try spinning up a different fly.io region quickly to see if it works. If it does, that means it’s a network or geographic issue. Get the cf-ray header from the failed request and see if you’re on shared or dedicated IPv4 (shared gets hit more).
The long-term solution is for Fly to move you to cleaner IP space or for the provider to whitelist fly.io ranges. A classic Cloudflare surprise for the holidays.
Cloudflare is not blocking fly.io instances. 403 coming from Groq API.
We moved to a different provider.