掲示板 Forums - Renshuu expired certificate

Yes, same here. Chrome now displays an interstice on web and my Android app doesn't open anymore.

Same here, couldn't login on the website and the app is crushing also after reinstalling.

I found this which micheal-san posted
"The servers use Let’s Encrypt for SSL certificates (along with 100s of millions of other websites/services). A few years ago, they announced plans to upgrade various aspects of their certification system … Essentially, the upgrades use a newer form of certificate that is not recognized or supported by Android 7.0 or older. Instead, renshuu (as well as all other apps/sites that use it) will appear as if the certification is not valid, and therefore will not be loaded"

The browser must be misinterpreting th certificate chain as expired because the root or intermediate Certificate Authority is not recognised by your device.

another one:
"it appears to be an update to the "Threat Protection" feature on NordVPN. This is something that "lives" inside of your web browser and alters the content of the webpage, and is not something that renshuu (or any webpage, for that matter) can detect or recognize. Until (if?) NordVPN fixes this, there is most likely nothing I can do to fix it.

If you were sent to this thread from a DM from me, then I need your help!

It appears that a small number of browser (Chrome, Firefox, etc.) users have something present in their browser (most likely an add-on or extension, perhaps a content/ad blocker) that is causing issues with renshuu. It is rewriting parts of renshuu (inside of the browser, not renshuu itself), which is causing renshuu to appear that is bugging out. It is most likely due to an update in the browser that happened roughly 7-10 days ago.

In order to resolve this, I'd love to get the following information from you (if you are experiencing this issue):

1. What browser you are using

2. If you have an extensions installed that are meant to change the way the websites that you visit appear.

3. If you have anything in #2, try disabling it for renshuu and see if the problem goes away.

There is no need to run these types of extensions on renshuu - we have 0 ads, and no trackers of any kind that might be considered undesirable, third-party or otherwise. In fact, I'll be happy to list all of the non-renshuu scripts that are run on renshuu:

1. typesquare - this is the font-delivery service that we use to get most of our awesome Japanese fonts!

2. sentry.io - this is loaded to report any browser errors that appear so I can hopefully fix them. The data picked up by this is stored in a private account on sentry.io that only I can view

3. If you are on renshuu.org (and not the app) and you visit the renshuu pro page, scripts for Stripe (credit card purchases) and Paypal are loaded to assist in creating the payment buttons.

This post will be updated if and most likely when we isolate what is causing it."
Can be found in forums

They might have recently switched from E5 to E8, and that's causing problems on some devices. The old one (E5) should be expiring around this time. On Chrome can you check your certificate? On Firefox it's the lock icon, same on Safari (pretty sure).

-

Mine is up-to-date (current valid chain).

If you're seeing E5, your device is trying to validate a chain that no longer exists.

Try this on Chrome: Hit F12, right-click on the refresh button, and then "Empty cache and hard reload" :

Anyway, it should get fixed on Renshuu's end. Assuming this is the problem.

The issue is present for the users, who have the Global server selected, which forces them to use https://app.renshuu.org/, that has an expired certificate since today morning.

To fix this for mobile apps, till the certificate is renewed, it will be required to:

1. Open the renshuu in some browser (preferably, the https://app.renshuu.org )

2. Authenticate and accept the warning on untrusted certificate (as you will be redirected to the website based on the server setting)

3. Open profile Settings -> Experimental and pick the Main Server

Fixed for me on mobile. Thank you!