Cloudflare Workers cannot connect to Vultr's API
Connecting to Vultr's API through Cloudflare workers causes a 403 forbidden. The 403 forbidden seems to be coming from Cloudflare directly looking at the developer tools. Is there anyway to get any insight into what's causing this? Vultr have confirmed they have no banned or blocked any of Cloudflare's IPs and 403 is not expected.
4 Replies
Vultr are the ones who would need to help with this, Cloudflare doesn't randomly return 403
https://test.walshy.dev/subrequest?url=https://api.vultr.com/v2/account
yeah that's a 403 from their origin
You can confirm this based on the
cf-cache-status: DYNAMIC that is only set if we go to origincool - they say its not them
and i can't say it's coming from a specific IP either so it's kind of a battle
i will see what they say, thx for replying 🙂
why would the server header be cloudflare? Vultr's API is not behind Cloudflare at all so I wouldn't expect to see that header.
That's just how Workers subrequests are because they still go through Cloudflare
But it's pretty clear this is not a cf page and the headers support that
sure thing, I know cf was going away with nginx but I have seen cf report that page in the past so it’s not a huge stretch. I’ve passed all this on to them.