I'm getting a certificate error on the Coppermine-Gallery.net website. Same issue for both Safari and Chrome browsers.
Your connection is not private
Attackers might be trying to steal your information from coppermine-gallery.net (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
I seem to be getting no certificate errors my end on Safari on my iPad and Edge on my laptop. I will test again later and regenerate the certificate if needed.
Quote from: Phill Luckhurst on October 10, 2020, 11:37:22 AM
I seem to be getting no certificate errors my end on Safari on my iPad and Edge on my laptop. I will test again later and regenerate the certificate if needed.
I'm seeing them Phill. Top menu is also broken for me, and is displaying down the page, so certain stuff is being blocked because of it.
Try this link, https://coppermine-gallery.net/team/
I have deleted the existing certificates and generated some new ones. Hopefully that is all good now. Thanks for the report.
This problem appears to be back. Firefox reports:-
"Firefox does not trust this site because it uses a certificate that is not valid for coppermine-gallery.net. The certificate is only valid for www.coppermine-gallery.net."
Using www.coppermine-gallery.net is no solution as it redirects to coppermine-gallery.net anyway, giving the same error.
Des
Hopefully that is working for you now
Still getting certificate errors. Have to force browsers to connect to site. Says the certificates have not been verified by third parties.
Which is odd, as they are working for me. I will have another check
The coppermine-gallery.net site appears to be OK now, but this site, forum.coppermine-gallery.net, is now reporting errors (which it was not yesterday). Firefox reports "forum.coppermine-gallery.net uses an invalid security certificate. The certificate is not trusted because it is self-signed."
Des
I'm aware and working on it
That was painful. It appears we were using an old version of lets-encrypt for generating the certificates. I have had to upgrade both our debian version and many other things to get lets-encrypt v02 api to work. Hopefully everything should now be working as it should. If not I will need to migrate from the current install to a debian install running sympl.host as the old setup is no longer being maintained. That is a lot of work and I will not have time for a couple of days.
Thanks for the heads up.
All appears to be working OK now.
Thanks for your efforts.