Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
So, I wanted to check out the forums, and on EVERY page I got something like this:
can someone explain what's happening?
Offline
Everything is fine for me.
I know some others are having issues too.
same here when I'm logged in on Tor, firefox, or chrome.
different's tryina fix it. i think.
proc's discorb stylish themes for forums/the game
꧁꧂L O V E & C O R N꧁꧂ ᘛ⁐̤ᕐᐷ
danke bluecloud thank u raphe [this section of my sig is dedicated to everything i've loved that's ever died]
?
Offline
As far as I can tell cloudflare is crapping itself. Nothing in the logs indicate that this is being done by the server itself, and with caching and MIME type issues, that have never been a problem before, it seems like cloudflare is the likely suspect.
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
Slapped a band-aid on it for now by hosting the CSS off-site where cloudflare can't get its hands on it, but smileys and the theme changer will be broken until cloudflare gets its act together.
EDIT: Avatars, too.
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
Well, having a theme you don't like beats not being able to browse the forums. Thanks for helping.
Offline
Not sure why this is locked but I'm working with some of CloudFlare's Support Engineers to possibly figure out what happened. Is there anyone who was affected last night who uses the HTTPS Everywhere add-on, or just generally uses HTTPS when browsing the forums who was affected?
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
How about "Is there anyone who wasn't affected last night who uses the HTTPS Everywhere add-on"?
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
How about "Is there anyone who wasn't affected last night who uses the HTTPS Everywhere add-on"?
I don't think I do
I don't use https and I wasn't affected.
thx for sig bobithan
Offline
I don't use https and I wasn't affected.
You don't live in the US, do you? How about you, Anak?
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
nope, uk
thx for sig bobithan
Offline
UK as well
It's a cached page. Try deleting your cache, including history.
Delete all cookies as well.
It's a cached page. Try deleting your cache, including history.
Delete all cookies as well.
I suggested that and it was not the solution.
I'm in US and I don't see https.
thanks zoey aaaaaaaaaaaand thanks latif for the avatar
Offline
I'm in US and I don't see https.
Don't see HTTPS or didn't see the forums fall to pieces while using HTTPS?
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
Assuming it would be in the URL, like on all other HTTPS pages, I don't see it.
thanks zoey aaaaaaaaaaaand thanks latif for the avatar
Offline
Assuming it would be in the URL, like on all other HTTPS pages, I don't see it.
Well, I was more asking if there was anyone who does use the HTTPS version of the site who was affected, not whether or not people are using HTTPS. HTTPS isn't the default.
But, times change and now the question is "Is there anyone at all outside the US who was affected?"
And for everyone who was affected, what state do you live in? Also, for anyone who was affected, if you're using an outdated browser, I recommend that you run a virus scan or two to make sure that it wasn't compromised. Apparently what happened last night was an attack that ended up getting cached by cloudflare, it didn't originate from cloudflare. Not sure how it ended up getting served at all, but I'm taking a much closer look at the server to see if I can find anything at all.
"Sometimes failing a leap of faith is better than inching forward"
- ShinsukeIto
Offline
maybe no one was affected
thx for sig bobithan
Offline
Pages: 1
[ Started around 1738489762.2076 - Generated in 0.117 seconds, 13 queries executed - Memory usage: 1.64 MiB (Peak: 1.83 MiB) ]