Timeline for Unable to "trust" self-signed certificate
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 20, 2015 at 15:26 | comment | added | Wassim | As a test, I renamed the hostname on one of my appliances to SMCXXXXXXXXX and the message went away. So you were all right, I need to re-issue the certificates with the correct CN. Thank you all for the help. | |
| Jul 20, 2015 at 15:07 | comment | added | Mike Ounsworth | @Wassim Glad you found your answer. I guess you'll have to re-issue your cert using proper wildcards (or using the exact hostname if you want to get it working quickly). -- Or you could set the hostname of the server to "SMCXXXXXXXXX" to make sure that this is actually the problem. | |
| Jul 20, 2015 at 15:04 | comment | added | Wassim | Okay so, I think my issue is that the CN is SMCXXXXXXXXX (something I have no control over, I think). The wildcard character for CNs seems to be *. | |
| Jul 20, 2015 at 14:57 | comment | added | Mike Ounsworth | If you type "The security certificate presented by this website was issued for a different website's address" into Google, you will get many guides that help you solve your problem. | |
| Jul 20, 2015 at 14:53 | comment | added | Wassim | I am accessing it through its hostname. smc0010f334747c/ui Should the full URL be in the CN ? or the hostname only ? | |
| Jul 20, 2015 at 14:51 | history | edited | Mike Ounsworth | CC BY-SA 3.0 |
edited body
|
| Jul 20, 2015 at 14:45 | history | answered | Mike Ounsworth | CC BY-SA 3.0 |