The WEZ didn't go down because it is superior to CIS.
I am still researching the issue and why CIS was not accessible. One thing to note is the WEZ is hosted by CIS and it had no downtime so the server itself was fine. There are some configuration differences between the two which likely lead to CIS not being accessible.
I am still researching the issue and why CIS was not accessible. One thing to note is the WEZ is hosted by CIS and it had no downtime so the server itself was fine. There are some configuration differences between the two which likely lead to CIS not being accessible.
I mostly use my iPhone to connect to this site (mobile version). Now I'm back on my laptop (Windows; Firefox w/noscript, adblock+, Ghostery, CS Lite) and it's doing something that's started only today. When in a thread, the "connecting" spinner (in the tab) never stops, although everything looks and works fine. Noscript is allowing CIS, cloudflare, and amazonaws. Noscript is blocking googlesyndication, and scorestream.
Just tossing that out, if it's any help.
I am still researching the issue and why CIS was not accessible. One thing to note is the WEZ is hosted by CIS and it had no downtime so the server itself was fine. There are some configuration differences between the two which likely lead to CIS not being accessible.
I mostly use my iPhone to connect to this site (mobile version). Now I'm back on my laptop (Windows; Firefox w/noscript, adblock+, Ghostery, CS Lite) and it's doing something that's started only today. When in a thread, the "connecting" spinner (in the tab) never stops, although everything looks and works fine. Noscript is allowing CIS, cloudflare, and amazonaws. Noscript is blocking googlesyndication, and scorestream.
Just tossing that out, if it's any help.
The things you are blocking only affect how it is rendered on your computer and it wouldn't have stopped the entire page from loading. I am not sure why it keeps spinning but it could be because one of the javascripts are blocked. I am not sure why you are block scorestream, it is just a high school scoreboard. Right now for what I can tell it looks like it was related to an attachment that GD had issues processing.
I am still researching the issue and why CIS was not accessible. One thing to note is the WEZ is hosted by CIS and it had no downtime so the server itself was fine. There are some configuration differences between the two which likely lead to CIS not being accessible.
I mostly use my iPhone to connect to this site (mobile version). Now I'm back on my laptop (Windows; Firefox w/noscript, adblock+, Ghostery, CS Lite) and it's doing something that's started only today. When in a thread, the "connecting" spinner (in the tab) never stops, although everything looks and works fine. Noscript is allowing CIS, cloudflare, and amazonaws. Noscript is blocking googlesyndication, and scorestream.
Just tossing that out, if it's any help.
The things you are blocking only affect how it is rendered on your computer and it wouldn't have stopped the entire page from loading. I am not sure why it keeps spinning but it could be because one of the javascripts are blocked. I am not sure why you are block scorestream, it is just a high school scoreboard. Right now for what I can tell it looks like it was related to an attachment that GD had issues processing.
I only allow what's necessary. BTW, the back button doesn't always work.
Server in South Carolina, or maybe Hilary's basement?
I am still researching the issue and why CIS was not accessible. One thing to note is the WEZ is hosted by CIS and it had no downtime so the server itself was fine. There are some configuration differences between the two which likely lead to CIS not being accessible.
I mostly use my iPhone to connect to this site (mobile version). Now I'm back on my laptop (Windows; Firefox w/noscript, adblock+, Ghostery, CS Lite) and it's doing something that's started only today. When in a thread, the "connecting" spinner (in the tab) never stops, although everything looks and works fine. Noscript is allowing CIS, cloudflare, and amazonaws. Noscript is blocking googlesyndication, and scorestream.
Just tossing that out, if it's any help.
The back button on my Logitech mouse; which is the same as the screen back button. It always stops working after a post, and at other random times.
I am still researching the issue and why CIS was not accessible. One thing to note is the WEZ is hosted by CIS and it had no downtime so the server itself was fine. There are some configuration differences between the two which likely lead to CIS not being accessible.
I mostly use my iPhone to connect to this site (mobile version). Now I'm back on my laptop (Windows; Firefox w/noscript, adblock+, Ghostery, CS Lite) and it's doing something that's started only today. When in a thread, the "connecting" spinner (in the tab) never stops, although everything looks and works fine. Noscript is allowing CIS, cloudflare, and amazonaws. Noscript is blocking googlesyndication, and scorestream.
Just tossing that out, if it's any help.
The things you are blocking only affect how it is rendered on your computer and it wouldn't have stopped the entire page from loading. I am not sure why it keeps spinning but it could be because one of the javascripts are blocked. I am not sure why you are block scorestream, it is just a high school scoreboard. Right now for what I can tell it looks like it was related to an attachment that GD had issues processing.
The back button on my Logitech mouse; which is the same as the screen back button. It always stops working after a post, and at other random times.
disable you add-ons and see if it works. The back button works for me for what it is worth.