Hi, I got a Zero Trust question. I created a tunnel TR. It works fine. My cloudflared seems running fine. I created a public hostname to be mapped to an internal(local LAN) site with an internal IP. When I go to the public hostname I got bad gateway error from Cloudflare. Error code 502
Where should I check for mis configurations? Many thanks
Just received even more alerts about performance issues with CF services. No reply on the ticket yet, it's been ongoing for over almost 4 days now... since it's monday I am getting even more people to notice these issues
@Erisa | Support Engineer Apologies for the ping - but since ~10 min there are lots of performance issues and 502 bad gateways. Have updated the ticket and I was able to get some traces to R2 too (with a slow response time).
Also Discord (which is behind CF) returned these 502's, no trace for that one but has been logged.
Again, apologies for the ping - really won't do this normally. Appreciate the help!
Updated the ticket with cf-rays just now. Seeing issues more in the wild too, some community members are noticing it too so it appears to be more widespread atm.
Cloudflare dashboard also returning 502's now. More people are sharing their issues now, still all from NL. Really hope anyone can dive into it with a bit more urgency
That's some good news at least - lost my patience a bit after the last 4 days of having these issues, have to apologise for that - but hopefully they'll be resolved soon
Sorry about that, its been very intermittent/hard to track down and we run on a reduced team over the weekend so getting to everything isn't always easy
Yea completely understandable. No worries, in the end, we're all just doing our jobs. Let me know if you need anything else, will be online for some hours still.
Also you can check the Cf-Cache-Status header which should say HIT not DYNAMIC - if it's DYNAMIC then Cloudflare is intentionally not caching for some reason
You could with a Worker yes, but keep in mind POST and GET are different for a reason. GET can have bodies but isn't supposed to and some reverse proxies will strip it if they see it. GET can also be cached and POST shouldn't be (which matters for things like form submissions).