You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use Vorlon to debug my Outlook add-in through Chrome. I need Chrome on OS X to accept my self-signed certificate (using instructions from ssl.md), but I am still getting a "Not Secure" error.
I've installed the certificate to the system keychain:
and set it to 'Always Trust':
But Chrome refuses to trust the cert:
Safari, on the other hand, trusts the certificate:
Any ideas? Please let me know if I'm missing anything; I would very much prefer to debug on Chrome over Safari as I am much more familiar with it.
The text was updated successfully, but these errors were encountered:
Important: You may still face issue with the Browsersync self-signed SSL certificated since the certificate is signed for domain "Internet Widgits Pty Ltd" instead of localhost. See this issue for more details and temporary workaround.
I'm trying to use Vorlon to debug my Outlook add-in through Chrome. I need Chrome on OS X to accept my self-signed certificate (using instructions from ssl.md), but I am still getting a "Not Secure" error.
I've installed the certificate to the system keychain:
![image](https://user-images.githubusercontent.com/3527178/33291805-b4fe9df6-d38c-11e7-94a4-f588eed275e4.png)
and set it to 'Always Trust':
![image](https://user-images.githubusercontent.com/3527178/33291898-ffb45b1a-d38c-11e7-84be-d9035c835b78.png)
But Chrome refuses to trust the cert:
![image](https://user-images.githubusercontent.com/3527178/33291650-23983b1a-d38c-11e7-954e-0794d2402197.png)
Safari, on the other hand, trusts the certificate:
![image](https://user-images.githubusercontent.com/3527178/33291949-2fef83ae-d38d-11e7-93ec-0b9015eadc04.png)
Any ideas? Please let me know if I'm missing anything; I would very much prefer to debug on Chrome over Safari as I am much more familiar with it.
The text was updated successfully, but these errors were encountered: