If you don't mind running Firebug and checking the response headers on the root request when it errors out, it would help to see them.
If nothing else, the "X-*" headers would really help.
Don't get me wrong, I applied some code changes but I wasn't expecting them to resolve the errors.
+9
Options
EsseeThe pinkest of hair.Victoria, BCRegistered Userregular
edited December 2013
Okay, I just grabbed Firebug and attempted to trigger a "something has gone wrong" in one of my tabs... and sadly, I did. I'm pretty sure it was after your post. And I just got "Whoops!" trying to post this. Having not used Firebug before, where should I be looking for the info you want?
Edit: Wait, I think I found the correct spot. Hold on.
Essee on
0
Options
EsseeThe pinkest of hair.Victoria, BCRegistered Userregular
edited December 2013
I think this is what you were looking for, @IcyLiquid?
Accept-Ranges bytes
Age 0
Connection keep-alive
Content-Length 714
Content-Type text/html; charset=utf-8
Date Tue, 10 Dec 2013 21:00:36 GMT
X-Cache MISS
X-Cacheable NO:Got Session
X-Varnish 156827286
I have my network console out and it's showing the front, I'll post the headers once I get another one of those. Do you also want some of pages that work, or strictly the "something broke" pages ?
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
Just the broken ones. I'm trying to see if its an individual app server consistently causing them. So far the error logs are empty which is why we're having to do the prehistoric troubleshooting.
Sorry, since Icy indicated they seemed to be nailing down a fix I thought maybe it happening a lot more all of a sudden would be significant information.
It's cool. At this point Icy has enough feedback from us and he will let us know if he needs more.
I know these errors are obnoxious (they annoy me anyways), and I am sure that nobody is more irritated by them than Icy. Just be patient and hopefully they'll be ironed out soon.
Weirdest thing, I haven't gotten an error all day, but occasionally have been getting the squigly face icon in the Chrome tab on normal pageloads instead.
I haven't gotten the squally faced error but I am getting the "Whoops, there was an error." sometimes when this autodraft thing tries to work. Is that from the same problem or something different?
0
Options
Dhalphirdon't you open that trapdooryou're a fool if you dareRegistered Userregular
Posts
Choose Your Own Chat 1 Choose Your Own Chat 2 Choose Your Own Chat 3
If nothing else, the "X-*" headers would really help.
Edit: Wait, I think I found the correct spot. Hold on.
I still have the error up if you need more.
I've got so many jokes here that I can't choose one.
Same thing essee was getting it seems. Front is missing from this one.
I did get that status code. Not sure if that means anything extra to you, 2XX is supposed to be success anyways? But 256 is undefined afaik.
The Remote IP was 192.91.146.234:80 though.
e: IP means nothing. Happened on another one.
I know these errors are obnoxious (they annoy me anyways), and I am sure that nobody is more irritated by them than Icy. Just be patient and hopefully they'll be ironed out soon.
Sorry Icy.
That'll do.
For the moment.
It has definitely happened to me in the last 12 hours.
D3 Steam #TeamTangent STO
(i'm knocking REALLY HARD on wood here)
steam | Dokkan: 868846562