Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Title
    FileMaker Developer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Jay's Achievements


Rookie (2/14)

  • First Post
  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges



  1. Excellent questions, Wim. It is in fact something.com without the www. I am not sure if it's a wildcard cert, but the domain will not be hosting any web sites or other services, nor will it have other TLD's. Just plain something.com dedicated to FileMaker. The goal is for filemaker client access from across the internet, through SSL to our FileMaker Server. I am assuming that we will (eventually) enter something.com under Open Remote instead of the IP address. When hitting the server via the IP address, it connects, but of course gives us a warning about a certificate mismatch - I am assuming that's because we are using the server's IP instead of something.com. I believe the only thing we would need to do is mess with the DNS at the registrar, tell them that something.com needs to resolve to a specific IP address and then that's it, it should work at that point?
  2. Sorry, incorrect phrasing for brevity. This has been done. It's been generated and imported. That part is long complete. My question remains: How to we "make the connection" between the domain name we used for the certificate (www.something.com) and the actual IP address of that server? Thank you
  3. I've done a search in this forum for "SSL" and it returns no result. So I'll start this thread: Has anyone posted a step by step guideline on how to implement SSL for FileMaker Server? If not, it would be very helpful, at least for me. I am familiar with generating the request from the FileMaker Server Admin Console. I am familiar with submitting the generated pem key to the GoDaddy service, who then generates a certificate for a price. I am familiar with placing said certificate in the correct folder on the server. However, that's where I leave off. There's some final steps missing, I don't know what they are. But we need to somehow "connect" the domain name we submitted when buying the certificate (www.something.com) , to the actual server we are using (it only has a static IP address), somehow. No idea what those steps would be. Any insight would be appreciated. Thank you
  4. Hello folks Need to hire someone to work on your solution? I offer 14 years experience and I am FileMaker Certified. Reasonably priced. Fast and accurate work. I am Seattle-based, but you can be located anywhere within the US. Please inbox me here on this site if you are interested in discussing your project. Thank you Jay T.
  • Create New...

Important Information

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