“I created the self-signed cert, double clicked on it and added it to the Trusted Root Certification Authorities.” Sorry I missed this. In that case, I stand corrected. The other next likely possibility is hostname mismatch.
On Tue, Jul 2, 2024 at 6:03 PM Dmitri Maziuk <dmitri.maz...@gmail.com> wrote: > On 7/2/24 16:40, Rahul Goswami wrote: > > > > > Since you are using a self-signed certificate, the browser won't have a > > corresponding CA certificate for it and hence flags it. The connection is > > still encrypted as with usual SSL. > > wrong: > > >> I created the self-signed cert, double clicked on it and added it to the > >> Trusted Root Certification Authorities. > > There are a few possibilities e.g. the hostname in the cert not matching > the hostname in the url, but we won't know without seeing the cert and > the actual error. > > Dima > >
