Click here to Skip to main content
15,892,927 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
I wanted to use https instead of http.

i have own IIS (web hosting). so, i created myself self-signed certificate in IIS.

while createing it asks name, i gave my computer name. then in binding i added https. // lets assume my computer name : xxx

before my site path: http:chri.tool.com

now i used https. now it is showing https://chri.tool.com. But.

i am in two strugle.

when i give like https://chri.tool.com, it shows warming message in browser (chrome) " The site's security is not trusted" then i give proceed, now it is working. but it is showing in red color certificate not verified.

FireFox:"This connectins is untrusted" not working.

IE : the problem with website security certificate then i gave continiue. now working . but it is showing invalid.

1. when i give path like : https://xxx. (which is running my locat system), https shows in green color.

2. when i give path like : https://chri.tools.com (which is running other browser) when i check by clicking https, it opened pop up about certificate details. in that it is showing:
"This CA Root certificate is not trusted. To enable trust, install this certificate in the trusted root certification authorities store".





How i have to overcome to above issues. how to use my site as https://chri.tool.com without redcolor and warning messge. pleave details information about that.
Posted
Updated 26-Dec-13 0:20am
v2

1 solution

You will have to purchase a certificate from a trusted authority. Self-signed certificates are not from a trusted authority. Verisign[^] sells them as do many other vendors.
 
Share this answer
 
Comments
christhuxavier 26-Dec-13 8:11am    
Thank you Mr.RyanDev, but few of them suggested me that you can generate own self-signed certificate if i have own IIS(web hosting provider). i have own web hosting provider.
ZurdoDev 26-Dec-13 8:25am    
Yes, windows server allows you to create a self-signed certificate, but that's all it is. Because it is self-signed and not signed by a world-wide recognized provider the browser will warn the user. If you are doing a site that is for internal use this may be perfectly fine. The encryption will still work correctly, the only problem is the warning in the browser.
christhuxavier 27-Dec-13 6:16am    
Okay Thanks a lot for good clarification Mr. RyanDev.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900