On every Server of our customers the communication between FMS and FMP Adv. (on the Server) slowed down dramatically after installing SSL Certificate. Does anybody know how to solve this problem?
A couple considerations with using the IP Address and an SSL:1. The SSL cert will not resolve. Hypothetically, if there were someone trying to spoof the server, you wouldn't know, because you wouldn't see the Green secure lock icon.
2. I've found that connecting via IP address to be slower than the FQDN on the internal network. We just set the DNS to redirect to the correct IP address. This also lets us easily move the server, and update the DNS settings without breaking all of the launch files on every machine, or having to worry about maintaining the same IP address when we move to a new server.
We use GoDaddy SSL certs and have no slowdown whatsoever on our multiple FMS15 servers hosted locally, on Azure and on AWS. Is it your SSL provider that's causing an issue or perhaps something else entirely?
Thank you for your answer, Eric,
we also exclusively use GoDaddy SSL certs. Communication between FMS and FM Adv. only on the same machine slows down, communication between different machines - even via Port 5003 over the internet - are doing well. The Windows 2008 or 2012 Servers of our customers run on real or virtual machines with the latest Version of FM 15 Server and FM Advanced.
Could it be a side-effect of using SSL and not the SSL itself? If you were connecting to the FMS server by IP address before and now because of the SSL cert you have to connect to its Fully Qualified Domain Name then the slowdown could come from your DNS and not from the extra encryption overhead.
Thank you Wim,
to save time we always use a FileMaker File "bb Start.fmp12" on the Desktop that automatically opens remote file "fmnet:/192.168.99.99/bb.fmp12". So we connect locally via IP-address - not via Server Name. On the Server machine we aren't able to connect via Domain Name like all the others from different machines do. Is that wrong?
Erwin_Eibel_eibel.businesssoftware wrote: Thank you Wim, to save time we always use a FileMaker File "bb Start.fmp12" on the Desktop that automatically opens remote file "fmnet:/192.168.99.99/bb.fmp12".
to save time we always use a FileMaker File "bb Start.fmp12" on the Desktop that automatically opens remote file "fmnet:/192.168.99.99/bb.fmp12".
Emphasizing what jormond says: by using the IP address in your launcher file you are negating the benefit of an SSL cert. You will not get a green lock for your user's connection to FMS. If you have an SSL cert you need to make the clients connect using the name on the cert. That way the client can verify the name of the server on the cert against the name it was asked to connect to.
Thank you all!
I'm sorry of have kept you waiting for my response. We have done what you proposed: always connect using SSL cert. Route domain name of ssl cert to ip adress of FMS.
Retrieving data ...