Whoops!
Okay, so obviously the site is broken at the moment. I tried to update the page to be HTTPS compliant and for some reason that jacked up the CSS, sooooo, yeah. I’m working on it. Part of trying to fix it involved rolling back the database a bit which might have nixed a few hours of comments. Sorry about that if something you posted got lost.
Thanks for your patience.
I wondered why the feed was messed up.
RSS feed has lots of duplicated items. I was happy at first when I saw so many unread ones :-)
Same, except that it was because I thought it was an Ava’s Demon update (it usually updates in batches of 10).
I only got 1 RSS notice, to this Whoops! page. Are we still going to see how Sydney gets off the space station tomorrow or maybe a conclusion to Cora’s flashback?
‘comments’ button not visible on mobile yet.
Also, I replied to Aaron, landed on Bergi.
Well you must have done something right because currently the page is running in https to this whoops message.
I’m trying to remember if it did before or not.
If you have a bookmarked link to the HTTP site that’s the one you will get. Clicking on any of the links on that page however will give you in HTTPS page. Once people update their bookmarks then they’ll get the HTTPS page automatically.
Although the certificate signer that you chose only gave you a certificate that is valid for three months.
Although, the certificate provider that you chose to sign your certificate, only made the grant for 3 months. It currently expires on April 2nd. So you’ll need to reauthorize the Grant and replace the certificate file before then otherwise people will get all sorts of weird errors when visiting your site.
His CA’s CA root (Say that 3 times fast) is only valid till 2021…. So they got that going for them as well.
This is intentional. Let’s Encrypt only issues certificates with 90 days validity to limit damage and (more importantly, IMHO) to encourage (read: force) site administrators to automate renewal.
Had noticed the… odd look to the page this morning, thought it was something the DamnBots did so closed the page down
There are still warnings about mixed content. Did you get all the images via https?
@DaveB, try changing the
http://
in every script and external image being loaded to just//
.Also try removing the
www.
in everywww.grrlpowercomic.com
because the certificate is only valid forgrrlpowercomic.com
; and no,www.grrlpowercomic.com
is not the same asgrrlpowercomic.com
.Removing just the scheme, i.e. //grrlpowercomic.com/x/y/z/foo.html is technically valid under current specs.
( https://url.spec.whatwg.org/#scheme-relative-special-url-string ) but almost always too verbose when /x/y/z/foo.html works. The old spec didn’t support abbreviating file: scheme urls with ///x/y/z/foo.html since the old spec (RFC 1738, RFC 3986) requires a hostname in that abbreviation, regardless of the base, so it makes sense to abbreviate as /x/y/z/foo.html which then works similarly. (Although it would be weird (and insecure) to have a web server have the same docroot as the root of the local filesystem.)
Hey DaveB, I’m still getting a mixed content warning. I’d be happy to help you if you need it. TLS problems are 20% of my day job.
The TopWebComics site isn’t HTTPS, so there will be warnings until they update.
Egh switching over to HTTPS was such a pain. All the links with the full path that shouldn’t be, all the external javascript and css references.
I was lucky I had a local copy in an IDE so I could search and replace for “http:” and still it was a pain.
Hm, Archive is not working right now…I see no images at all using ether http or https (march 24)
On related note the cast page is gone again.
@ DaveB the portraits link to cast while the working button cast links to castpage. Please fix.
*Meep* … ROFL
You still play CounterStrike: Source? Me too!
Had noticed the… odd look to the page this morning, thought it was something the DamnBots did so closed the page down