Jump to content
doubleclicker

SSL Certificates IP Address vs FQDN

Recommended Posts

I have installed an SSL on FileMaker Server to access databases securely via WebDirect. All works well when I use the IP address however I cannot get the FQDN to work  (server name.domainname.net.au). I'm obviously missing some integral part in setting up the FQDN on the Mac hosting the FM Server. Can anyone point me in the right direction please? Thanks

Share this post


Link to post
Share on other sites

Are you accessing filemaker server via FM Pro, Go, or WebDirect?

If via WebDirect, and you are getting a certificate mismatch error in your browser, you can click for more information which may tell you the IP address/Domain Name being used.

Share this post


Link to post
Share on other sites

Sorry. I am using FileMaker Server/Pro 13 and accessing via Webdirect using Safari as the browser. I can see that it is accessing the IP address OK. I just need help in setting up the Fully Qualified Domain Name on the Mac so I can use that in the URL to access the databases in my browser. I suspect it is something to do with my router????

Share this post


Link to post
Share on other sites

Do you know where you manage your domain name? (servername.domainname.net.au in your example)

You need a DNS server to provide the translation from IP address to FQDN.  If the domain is managed externally by someone like melbourneit.com.au then you would get things configured on their DNS manager.  You would create an A record for servername.domainname.net.au and point it to your external IP address, assuming 1. your IP address is static, and 2. isn't already set up for some other reason.  If it is setup already then it is a routing issue, not a DNS issue.

Now if this isn't an externally facing solution and only used on your internal network then you need to have your own DNS server on your network if you don't already.  A quick google search and out of the box you need Mac OS X server to have a Mac act as a DNS server. (However, I did find an app that could do it on standard OSX http://passingcuriosity.com/2013/dnsmasq-dev-osx/).  Once your network DNS server knows that servername.domainname.net.au is local and what IP address it maps to anyone on your network would be able to get to your FM server via the FQDN.

This all assumes static IP for either internal or external configurations and that all the firewall routes are setup correctly, but if IP address is working I would think they are setup.

Share this post


Link to post
Share on other sites

Thanks all for your input. I think it is related to the router. I will post with an update soon. Thanks again for your responses and time taken.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Who Viewed the Topic

    1 member has viewed this topic:
    Lee Smith 
  • Similar Content

    • By HHMacGuffin
      Hi,
      I just installed the custom SSL certificate as part of the update of my FMS13 to 13.0v9, and I noticed the open url script step on my FileMaker Pro client stopped working since the certificate was installed. I have since proceeded with the update and completed it successfully, but the open url issue remained. I'm at a loss as to why this is the case and would appreciate any suggestions to resolve the issue.
      I know the open url script stopped working after the certificate was installed but before the update was carried out because I happen to have need of using it at that point. The issue appears specific to my FMP client as the same script runs smoothly on FMG as well as on Web Direct. There is no other script steps involved: It's just open the url given in a record (it's a table of websites).
      Many thanks for your time and help.
      Cheers, The MacGuffin
×

Important Information

By using this site, you agree to our Terms of Use.