3 ms·
See my blog entries here (beware, something about the certificate for the web server is broken right now, will try to fix it right away): https://www.multicore
by johndoe0815 4y ago
See my blog entries here (beware, something about the certificate for the web server is broken right now, will try to fix it right away):
https://www.multicores.org/blog/tag_Smalltalk.html https://www.multicores.org/blog/tag_Smalltalk.html
- slim 4y agonothing is wrong with your certificate, it's just self signed and browsers don't support that correctly. They just show the same unsecure usual message.
- johndoe0815 4y agoThanks for the feedback! You're correct, but I seem to remember that I configured a letsencrypt certificate for nginx, which should be recognized as fully verified as far as I know.
- AlbertoGP 4y agoWell, right now I’m getting a self-signed certificate with a validity of one year, not the letsencrypt one. Issuer name Country: de Organization: multicores Email Address: engel@multicores.org
- layer8 4y agoThe problem is that the certificate is issued for multicores.org, but not for www.multicores.org. Removing the "www." from the URL makes it work. You need to have the certificate issued for all subdomains you want to use it for (or for a wildcard subdomain).
- johndoe0815 4y agoUh, good catch, thanks - that explains it!