Printable View
I can only get here through tapatalk; if I try from any computer going to forums.smartcanucks.ca (with or without any 's') it tells me that the site is down and there is no cached version.
My mobile is using the same internet connection, and I have tried 3 different computers, different OS (XP & 7), and wired & wireless
~~Sent from my mobile using Tapatalk~~
Update: IE is now loading the site, but not FF v 12 (which hasn't changed for me)
Going to update FF & see what happens
~~Sent from my mobile using Tapatalk~~
Well that was useless - FF 16.0.1 still has the issue too, going to post a pic in a bit
~~Sent from my mobile using Tapatalk~~
This is what I get in FF with ANY link on SC that begins with 'forum' (forum.smartcanucks.ca)
http://i616.photobucket.com/albums/t...Designs/sc.png
So I found this:
http://support.cloudflare.com/cgi/kb...ilable-message
I hate IE with every fibre of my being, so I guess I'll be using tapatalk for awhile until FF can load the site again.
So, KrazE, you see this only when using Firefox but not if you use IE? Do you have a proxy set in either browser?
Does anyone else ever see this message?
I'm using FF right now and no issues - hope urs gets resolved soon Kraze!
Like I posted before, nothing has changed here, no proxies. Still researching cause it's flipping annoying to meQuote:
Originally Posted by dataiv
~~Sent from my mobile using Tapatalk~~
Seems to be a known issue with FF & Cloudflare on numerous versions - almost as though FF is trying to go to an https rather than http
Woot! Fixed it!
I had to toss absolutely everything from my history & cache in FF including the bookmark to get it to stop misbehaving; sheesh that was annoying
wondering if it was related to the firefox problem a day or so ago, i went back to whatever version
was before as apparently where was a security thingy.
saw this about 16.0.1:
http://www.mozilla.org/en-US/firefox.../releasenotes/
can understand the frustration KrazE
Not sure, it started in V12, so I don't think it was related to 16.0.1 since I upgraded after having the issue initially.