Thank you for your reply.
I saw this article but ruled out all hosting-side errors, as i have a proxied domain that can be accessed with curl and the --resolve option (specifying the origin IP) and i know i have no firewall rules, user agents/countries blocks etc…but i am getting 403 when not using the --resolve option for that domain + the issue manifests its self for websites like nodejs[.]org, or www[.]Cloudflare[.]com , or nginx[.]com , etc…
I also don’t quite get what ‘Cloudflare doesn’t return 4xx codes’ means, as i can clearly see :
HTTP/2 403
server: Cloudflare
in the response from my curl reqeusts…
We are not blocking CF IPs in any way .
I am struggling to find more helpful info from this artcile.