Problem 1: providing your address in an open forum and stating the server isn't secure...
Well, if I don't mention it it's never gonna be secure.
And it doesn't currently contain data that is private.
Besides all the information I gave is public information anyway correct? A simple traceroute should expose it all or am I missing something?
I masked out the data in the original post now. Hope that helps.
My server.mydomain.com is forwarded to the https://207.XXX.XXX.XXX
How is it forwarded? In order for SSL to work the server.mydomain.com has to be set up in DNS to go the IP address, not just being forwarded.
Do you mean with an A record in the DNS record?
It's currently only forwarded to the IP.
Yes, create an A record in DNS.
Ok done. Still not working though.
I think the problem exists in my intermediate certificate.
When I download my SSL from GoDaddy I get two files. certificatename.crt and a bundlecertificatename.crt (I think this is the intermediate).
Problem is that I can't get it installed with the bundledcertificatename.crt in place, only without. Getting an error when I try with.
For 16 you do need to use both. The wizard on FMS to import the cert has a place to import both the cert and the intermediate.
What error do you get?
Certificate could not be imported: Config_DBServer_CertificateDialog_ErrorGo Daddy Secure Certificate Authority - G2
3 of 3 people found this helpful
Mike Duncan posted this in another thread. Go to the link, save the file as gdig2.crt, and import it as your intermediate.
For godaddy, you can get the intermediate cert here:
Didn't work for me unfortunately.
Now I did found more certificates like root, intermediate, cross etc in the https://certs.godaddy.com/repository which might be handy.
Because according to the help file on this link Configuring security for FileMaker Server 15 and higher | FileMakerhttp://help.filemaker.com/app/answers/detail/a_id/14176/~/configuring-security-for-filemaker-server-15-and-higher
you have to create your own chain.pem file consisting the following data and respecting the order:
Intermediate certificate 2
Intermediate certificate 1
Only problem. I can't make it work for some reason. Keeps giving the same error. Even when I combine the rootcert and intermediatecert into 1 file.
2 of 2 people found this helpful
Step 1: Go to the Security Tab of Database Server.
2. Hit the Create Request button.
3. That file contains text. Select all of the text, copy it.
4. Go to GoDaddy, to the SSL Certificates area. Paste the text where it says. For the Server option, select "Other".
5. You'll receive two files from GoDaddy. The one with just letters and numbers is your certificate. You don't need the other one.
6. When you go to that link that I pasted earlier, you'll see all of the text. Select it, and paste it into a text editor, save the file.
7. Go back to your Server Admin console. Import certificate. Use the non-"bundle" file as you certificate, the gdig2 as your intermediate, and select your private key.
8. That should do it.
Don't combine any files. Just import them as is. Hope that helps.
You needs a DNS A record for server.domain.com. Do you have that? There should be no 301 redirects To the IP address.
I use the bundle as the intermediate.
I found that rekey rekey after every failure might help.