Post 1989426 by pea@fuckonthefirst.date
 (DIR) More posts by pea@fuckonthefirst.date
 (DIR) Post #1989423 by TMWReviews@mastodon.social
       2018-12-14T14:49:56Z
       
       0 likes, 0 repeats
       
       REVIEW: Simmiland shows that part of why it's hard to be a God is humans, being jerks. Interesting variation of the God-Game formula by SokPop. https://themadwelshman.co.uk/simmiland-review/
       
 (DIR) Post #1989425 by Nentuaby@wandering.shop
       2018-12-14T18:46:10Z
       
       0 likes, 0 repeats
       
       @TMWReviews FYI, Chrome does not like your site over https
       
 (DIR) Post #1989426 by pea@fuckonthefirst.date
       2018-12-14T18:47:14.497817Z
       
       0 likes, 0 repeats
       
       @Nentuaby @TMWReviews it's not just chrome, ff too
       
 (DIR) Post #1989451 by Nentuaby@wandering.shop
       2018-12-14T18:47:57Z
       
       0 likes, 0 repeats
       
       @pea @TMWReviews Hmm yeah, I tried it once in firefox and it worked, but now that's being sticky too.
       
 (DIR) Post #1989452 by TMWReviews@mastodon.social
       2018-12-14T18:48:22Z
       
       1 likes, 0 repeats
       
       @Nentuaby @pea Yes, I am unfortunately aware of this. Alas, the host provider assures me the SSL Cert is valid. A friend who probed it says it should be working fine. Nobody who's looked at it can seemingly give me any answers as to why this is happening.
       
 (DIR) Post #1989458 by pea@fuckonthefirst.date
       2018-12-14T18:49:18.237723Z
       
       0 likes, 0 repeats
       
       @TMWReviews @Nentuaby it's nothing to do with the SSL cert, something to do with the ciphers supported I guess, I'll give it a try in curl, see if i can get some more info
       
 (DIR) Post #1989666 by Nentuaby@wandering.shop
       2018-12-14T18:49:43Z
       
       0 likes, 0 repeats
       
       @TMWReviews @pea Yeah, this won't be a cert issue, it'll be with the configuration or version of the server software. It doesn't speak any encryption protocols the browsers like; probably it's old software and it only speaks protocols that have been deprecated by the browsers.
       
 (DIR) Post #1989667 by TMWReviews@mastodon.social
       2018-12-14T18:50:49Z
       
       0 likes, 0 repeats
       
       @Nentuaby @pea Thanks, because while it hasn't been reported to me *often* , it's been reported enough that it's concerning.If it's config of the server software, then I'm basically fucked for the foreseeable, as switching hosts from Servage/replacing SSL takes dough I *very much* don't have rn.
       
 (DIR) Post #1989668 by pea@fuckonthefirst.date
       2018-12-14T18:58:46.041606Z
       
       0 likes, 0 repeats
       
       @TMWReviews @Nentuaby it definitely seems to be a deprecated cipher issue afaict? FF and chrome stopped supporting legacy ciphers a bit backI can't imagine servage only supports legacy ciphers though