I was unable to access JCJP all day yesterday because that happened again (picture). But what… - Feed Post by rblopes

I was unable to access JCJP all day yesterday because that happened again (picture). But what amazes me is how other friends of the site are still able to use JCJP without problems at all when these issues occur. As for me, well, I guess it's day 1 of my day streak again... ʕ ಡ ﹏ ಡ ʔ

posted by rblopes July 11, 2017 at 10:31pm

• 
  pooperscoop

  I also couldn't use it, but mine looked a little different. It looked like a bad html only page.

  July 12, 2017 at 2:46am
• 
  mog86uk

  I know. I've lost my streak a couple of times recently when this has happened.
  
  I think the reason some people can still get in can depend on which browser they are using.
  
  Even in Chrome though, there are technical ways you can still get onto the site when this happens. You can add the command-line argument "--ignore-certificate-errors" to your Chrome shortcut target, to tell Chrome to ignore this type of security warning and just let you onto the site. It's certainly not recommended you do this, because this will also take effect on actual dangerous sites too, but it does work. I doubt many of the people still getting onto the site are doing it this way though... :P
  
  Beeant has been out of the country for a couple of weeks. I think this may have been what caused this issue, and it's likely the reason why he hasn't been able to sort things out as quick as usual. But I believe he may now be back. Should hopefully stop seeing this problem now. ^^

  July 12, 2017 at 2:46am
• 
  rblopes

  @pooperscoop That screenshot is actually from the CDN server, otherwise accessing the main site was all the same, only mark-up with no styling.
  
  @mog86uk I tried the Chrome CLI flag to no avail. I tried to log in using Firefox with no success too. That was due some unusual SSL issue. In comparison, today we have the same "Let's Encrypt" signed cert, while yesterday, I got that one on the screenshot. Now I wonder if either Chrome (and FF) are "too secure" or other browsers are "too unsafe", to be honest.
  
  About the streak, I knew that could happen anytime, and I'm okay with that, that wouldn't my first time, but 1st in JCJP to carry on with the tradition for sure :)

  July 12, 2017 at 4:20am
• 
  beeant

  I'm really sorry about this problem... :(
  I was on a flight back to Japan so I couldn't fix it right away. This problem was caused by late payment to the CDN server...

  July 12, 2017 at 5:31am
• 
  akarihoshi16

  Be patient 😂

  July 12, 2017 at 6:01pm
• 
  rblopes

  @akarihoshi16 I wouldn't be able to get this far if I wasn't ;)

  July 12, 2017 at 10:24pm