I have two Sharepoint web applications running on the same server. Each one needs its own ssl certificate. We did not purchase the wildcard certificate. One https site runs on one internal/external IP address on port 443 and the other website runs on a different IP address on port 4430. Both ports are open and working fine since we're already tested that. In fact, I've already set it up once on the same server with two separate certificate but one was already in production and the other one was temporarily using a self-signed certificate. Now, I'm working on getting the second web application to be in production as well so I need to use the correct, official ssl certificate. When I go to IIS for the second site and select that official certificate (actually it also happens when I select that self-signed certificate I used before), I'm getting the following message:
"The binding is already being used by a product other than IIS. If you continue, you might overwrite the existing certificate for this IP Address/Port combination. Do you want to use this binding anyway"
I don't want to click Yes because I'm not sure what this is going to overwrite. Right now I only have one ssl certificate bound and that's for the first web application that is already in production, but that app is on a separate IP address and a separate port (it's using port 443). This site is for a different IP address and port 4430 and right now there is no ssl certificate bound to that (at least to my knowledge). When I selected "All unassigned" as the IP address as opposed to selecting that second IP Address that I was supposed to use then I was able to select the certificate and click OK with no problems. However, I want that second website to use the second IP address we designated for it. I can't figure out why it won't let me do it.
Any help will be greatly appreciated.
thanks,