Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I wasted a bunch of time debugging the HTTP 500 errors on my site before I realized everything is 100% OK on my end, and that it's Cloudflare returning the error not my servers.


Ditto - I'm sitting here, wtf I'm not running Nginx on my blog, but I'm getting an Nginx response, hit IP directly....oooh.... right that doesn't make sense it's working fine. Cloudflare can't be down, that's next to, wait, status page (to their credit it's got a status note). HN here we go...


Sorry about that.


Would it be possible to adjust that 500 page to include an indication that it originates from Cloudflare, for the case that an outage like this happens again in the future?


I was surprised by that also. Will ask.


As we'd say, no worries mate! One little blog is probably the least of the s*tstorm you guys just had to deal with :)




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: