We are on FRA1 region, and working with a. This server could not prove that it is its security certificate is not trusted by your computer's operating system.This may be caused by a misconfiguration or an attacker intercepting your connection. What is weird is that the first error is contradictory - the given wildcard certificate should be just fine for our origin URL. This may be caused by a misconfiguration or an attacker intercepting your connection. This may be caused by a misconfiguration or an attacker intercepting your connection.įinally, by using an automatic DO Let’s Encrypt certificate, and going to our custom URL, the same error arises: This server could not prove that it is its security certificate is from *. When enabling the CDN, and going to the given edge URL, another error is given (still, both Firefox and Chrome): This server could not prove that it is 3. its security certificate is from *. The given error is: This server could not prove that it is 3. its security certificate is from *. When creating a new Spaces on Digital Ocean and going to the given origin URL, both Firefox and Chrome warns that the SSL certificate is invalid. It is impossible to get a working SSL with Spaces.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |