0 Members and 2 Guests are viewing this topic.
The site does load in https, but every link takes me back to the non-https version. Does that happen to anyone else, or is it just on my end?
Switching to HTTPS sure causes extreme server loading. It took 28 hours to load this page. Oh wait nvm that was the host being down. Seriously I seriously hope you get some free months from this cuz it was kinda bad.Also Moderation center is fixed, so I can't see it anymore. I didn't try to see if last post by the same IP errors still occur, though. I just noticed the site is back now.
Nice but isn't this only a client <-> cf thing ? What about cf <-> omni ?
The last post from same ip still occurs, I had it when posting the above message which forced me to rewrite it.
Nightly now claims of some stuff being insecure and thus refuses to load like the stylesheet. EDIT: I fixed it
Quote from: Sorunome on December 09, 2014, 05:55:56 amNightly now claims of some stuff being insecure and thus refuses to load like the stylesheet. EDIT: I fixed it something keeps changing the board url setting back to http at random intervals
Quote from: Eeems on December 09, 2014, 10:08:28 amQuote from: Sorunome on December 09, 2014, 05:55:56 amNightly now claims of some stuff being insecure and thus refuses to load like the stylesheet. EDIT: I fixed it something keeps changing the board url setting back to http at random intervals Is this on the server side or on your client?
Quote from: TravisE on December 08, 2014, 02:08:29 pmThe site does load in https, but every link takes me back to the non-https version. Does that happen to anyone else, or is it just on my end?Should have been fixed when I cleared all the old pretty url cached links. Could it be a chrome caching issue (if you use chrome)?
Quote from: Eeems on December 08, 2014, 03:10:55 pmQuote from: TravisE on December 08, 2014, 02:08:29 pmThe site does load in https, but every link takes me back to the non-https version. Does that happen to anyone else, or is it just on my end?Should have been fixed when I cleared all the old pretty url cached links. Could it be a chrome caching issue (if you use chrome)?I use Firefox, but it seems to be fixed now.