The problem:
Suddenly, de images loaded from site A whe showing properly, while the ones from B weren't loding at all an this error begin to show up
The problem was that site B had a self-signed certificated create with IIS with a domain we could not specify, as you see, the only field i can fill was de friendly name but the domain was out of my control
The solution:
We created a other self-signed certificate but especifing the domain we need in this page
http://www.selfsignedcertificate.com/
Download this files
Problem 2:
To be able to set the newly create certificate in the ISS site we need to convert it into a .PBX file
Solution 2:
We converted the .cert file to .PFX using this page
https://www.sslshopper.com/ssl-converter.html
In 1. The certificate downloaded in
In 2. The certificate downloaded in
In 3. we select Standard PEM and 4. we select PFX/PKCS#12
In 5. we enter any password we like
Then all we need to do is import the .pfx file in the IIS and set it to out B site
Have good luck... ;)
I wanna tell you the reason why i ended doing this. We were trying to build two site that comunicate with each other and share information though web services and resources like images...so basically what we did was to load images hoste in site A from site B like this:
<img src="www.B.com/image.png" >
Suddenly, de images loaded from site A whe showing properly, while the ones from B weren't loding at all an this error begin to show up
The problem was that site B had a self-signed certificated create with IIS with a domain we could not specify, as you see, the only field i can fill was de friendly name but the domain was out of my control
So Google Chrome (and IE) didn't want to load the images hosted in site B because the self-signed certificate domain did not match the site domain.
We created a other self-signed certificate but especifing the domain we need in this page
http://www.selfsignedcertificate.com/
Download this files
Problem 2:
To be able to set the newly create certificate in the ISS site we need to convert it into a .PBX file
Solution 2:
We converted the .cert file to .PFX using this page
https://www.sslshopper.com/ssl-converter.html
In 1. The certificate downloaded in
In 2. The certificate downloaded in
In 3. we select Standard PEM and 4. we select PFX/PKCS#12
In 5. we enter any password we like
Then all we need to do is import the .pfx file in the IIS and set it to out B site
Have good luck... ;)
