@eastdakota I'm getting #500InternalServerError - I didn't think that this should happen with @CloudFlare
-
-
Replying to @BryanMHaines
@BryanMHaines@eastdakota Definitely appears to be an issue with your host & you should contact them. I'm seeing 508s from your back end.1 reply 0 retweets 0 likes -
Replying to @Cloudflare
@CloudFlare@eastdakota Okay, I'll check with@LiquidWeb. I thought that the cloudflare service would keep this from happening.1 reply 0 retweets 0 likes -
Replying to @BryanMHaines
@BryanMHaines@eastdakota@LiquidWeb We're not going to fix back end issues on your server:(1 reply 0 retweets 0 likes -
Replying to @Cloudflare
@CloudFlare@eastdakota@LiquidWeb Obviously. I thought that "Always Online™" meant that my site would be#alwaysonline. I misunderstood?1 reply 0 retweets 0 likes -
Replying to @BryanMHaines
@BryanMHaines@eastdakota@LiquidWeb Always Online is only designed to work with 502 and 504 errors. It won't work with 500 or other 50x.1 reply 0 retweets 0 likes -
Replying to @Cloudflare
@CloudFlare So it's kind of more like "Online (as long as nothing comes up)™"?2 replies 0 retweets 0 likes
@BryanMHaines It doesn't work with 500 errors. That's an error that we would want to display to the site owner so they know issue is on
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.