I am trying to configure SuperContainer v2.631 to work with FileMaker Server 10 on Microsoft Windows Server 2003 (Web Edition, SP 2). I have installed and licensed SuperContainer. When I attempt to connect to the container, either through the FMP 10 client or a web browser, I get the following error.

Could not connect to SuperContainer server:

java.io.IOException: Unable to connect to https://[...my_server_name..]/SuperContainer/Files. The SSL Certificate on this server could not be verified.

IIS Manager seems to be happy with the cert (Default Web Site -> Properties -> Directory Security Tab -> View Certificate).

The link on the wiki seems to point to the wrong page, so I don't know where to turn:

http://wo.360works.com/cgi-bin/support/productsupport.cgi/SuperContainer#SuperContainer51

Any suggestions would be wonderful.

Thanks!

-Tanya

Tanya, the error message about certificate not being verified will happen if you use a self signed certificate, which would not be a valid certificate.

Dear Valentin,

Thanks for the reply. After doing some more sleuthing, it appears that my server's SSL certificate authority (ipsCA) is not recognized as trusted by Java. I am going to request a certificate from another CA, and see if that helps.

Users can check which CAs are recognized by Java using the Java keytool utility:

http://www.java-samples.com/showtutorial.php?tutorialid=210

Cheers,

Tanya

Tanya and/or 360Works,

I am now getting the exact same error after installing SC on my SL server, using a GoDaddy (Starfield Secure Cert. Auth) Certificate for my SSL. Our CA is not self-assigned, but has been replaced with a signed cert from GoDaddy. The link you provided above for how Java is unable to trust this CA, is far beyond my skill set in understanding how to actually remedy this problem. Do either of you have any recommendations for fixing this?

Thanks, Mike

Hi Mike

Can you please post an https link, I'll take a look at your certificate.

https://dme-cg.com/

thanks,

Mike