We’ve got a client server that has OttoFMS running on it, and we can access that perfectly fine. But when trying to add that server in Otto Deploy, we get an error where the OttoFMS version comes back as unknown. We’ve tried using OttoDeploy locally and on a couple of other servers, using both local IPs and public (no DNS available – they hide most things behind VPNs. Is that part of the issue?). Ports 80 and 443 are open completely.
Pretty sure you cant use local loopback as that is not covered by SSL
If your firewall is set up correctly using the FQDN will loopback internally so the traffic is not going out of the building and back
Yeah, the loopback was just a trial, and I assumed there’d be a routing issue with that. Public IP yeilds same result, as does access from secondary machine on local network.
The SSL part is a good point though. Does it have to be a FQDN protected by SSL? I thought I had used IPs in the past, but can’t reproduce that now.
Yes it does, you can over-ride the lower level of security with FileMaker client, but not with any API-style calls (Connect, Studio, OttoFMS etc etc)