UniLang

Posted: **2016-05-10, 20:05**

We now have a proper SSL certificate for https://unilang.org and https://forum.unilang.org, for which you now longer need to add a security exception. Use of https is strongly recommended as it means your traffic is encrypted and can not be intercepted by any third party.

(SHA1 certificate fingerprint: FB:BA:6B:DB:38:BC:96:09:CE:74:81:35:32:C3:57:AA:E8:A2:26:C9)

Posted: **2016-08-03, 22:24**

Certificate refreshed, this will happen every three months.

(new SHA1 fingerprint: EE:BE:1B:44:54:70:83:6E:9F:4D:CE:F2:A8:F9:73:75:B4:7A:F0:BC)

Posted: **2017-10-16, 9:08**

Updated: 68:9A:30:7D:75:FF:7C:4F:43:62:85:9B:D0:DA:18:EF:2E:B4:24:AB

Posted: **2017-11-30, 22:09**

proycon wrote:Updated: 68:9A:30:7D:75:FF:7C:4F:43:62:85:9B:D0:DA:18:EF:2E:B4:24:AB

Hey proycon, not sure if you're aware, but when I try to go directly to https://www.unilang.org, I get an error. I'm using Chrome, but I think the same might be happening on any browser? Anyway, this has been going on for a while - longer than since the last update. Here are the details of the error:

Your connection is not private

Attackers might be trying to steal your information from www.unilang.org (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID

Back to safety

ADVANCED
This server could not prove that it is www.unilang.org; its security certificate is from anaproy.nl. This may be caused by a misconfiguration or an attacker intercepting your connection.

Proceed to www.unilang.org (unsafe)

It seems that once I clicked on proceed anyway, Chrome now automatically redirects and doesn't show me the error.

Posted: **2017-11-30, 22:16**

That has happened to me from time to time on Firefox as well.

Posted: **2017-11-30, 22:17**

I just checked on Firefox, and it happens to me there even now.

Posted: **2017-11-30, 22:26**

Yeah on the UL FB group, someone posted about this about a month ago. I replied to use https://forum.unilang.org, which is what my bookmarks are set to.

Posted: **2017-12-01, 9:43**

Hmm, I see.. This is caused by the certificate being valid for 'unilang.org' and 'forum.unilang.org', but not 'www.unilang.org'.

I partially fixed this now by redirecting at least http://www.unilang.org to https://forum.unilang.org , the problem still will occur if you explicitly go to https://www.unilang.org (use https://unilang.org or https://forum.unilang.org instead). I'll try to add this old subdomain in the next SSL certificate renewal iteration.

Posted: **2017-12-02, 1:49**

Sounds good; thanks!

Posted: **2017-12-02, 10:33**

proycon wrote:Hmm, I see.. This is caused by the certificate being valid for 'unilang.org' and 'forum.unilang.org', but not 'www.unilang.org'.

I partially fixed this now by redirecting at least http://www.unilang.org to https://forum.unilang.org , the problem still will occur if you explicitly go to https://www.unilang.org (use https://unilang.org or https://forum.unilang.org instead). I'll try to add this old subdomain in the next SSL certificate renewal iteration.

If you are using Lets Encrypt, you can expand the certificate with new domains without reissuing it, as far as I know.
Unless you have it on a cronjob and don't want to interfere.

UniLang

SSL certificate renewed (https support)

SSL certificate renewed (https support)

Re: SSL certificate renewed (https support)

Re: SSL certificate renewed (https support)

Re: SSL certificate renewed (https support)

Re: SSL certificate renewed (https support)

Re: SSL certificate renewed (https support)

Re: SSL certificate renewed (https support)

Re: SSL certificate renewed (https support)

Re: SSL certificate renewed (https support)

Re: SSL certificate renewed (https support)