Similar to Unable to verify credentials #ottodeploy, same images applies.
I’ve tried completely wiping OttoFMS off the system.
I’ve tried resetting the password.
It has a valid SSL cert.
The ports are perfectly accessible from the outside (with NAT), admin-console and webdirect work with no issue.
The OttoFMS dashboard is available from the outside source, but the “FileMaker Server” section of the UI (the one that manages the live Databases) has no files listed despite the dashboard showing the files and users connected properly.
It let’s me create Admin API keys but OttoDeploy doesn’t take them.
Do you have any sort of IP filtering set up on FileMaker Server? It sounds like OttoFMS is having trouble communicating with FileMaker. Is there anything in the otto-info or otto-error logs?
-Kyle
The server is on a firewall that has 443 and 5003 whitelisted to certain public IPs, including the machine currently sending the request through Otto Deploy.
Does a certain OttoFMS ip need to be whitelisted? This has worked on all of our other servers with no problem.
otto-error:
2025-06-16T15:52:33.120Z error Error calling admin api proxy: connect ETIMEDOUT xx.xx.xx.xx:443 2025-06-16T15:55:19.851Z error Error calling admin api proxy: connect ETIMEDOUT xx.xx.xx.xx:443
Is this server the first one you’ve tried with OttoFMS 4.11.0? In that version OttoFMS is calling back out to the hostname rather than directly to the Admin Server port (due to some idiosyncrasies with how FileMaker is handling their proxies). If the server doesn’t have the ability to call out to itself something similar would happen.
Reverting to 4.10.3 fixed the problem.
This server in particular cannot call itself locally with DNS, so that could do it.
Could there be a toggle for this option in settings? Most of our setups won’t be affected, but the few servers on networks without local DNS might have some issues.
I will see if I can just edit the host file and fix it for 4.11.0
EDIT: Adding a record for the local IP to the DNS name in the host file worked. For future reference
Glad we found the problem! I’ll take a look at getting an option in there to turn off the callout for the admin api/data api proxy. It is mostly important for the Data API Proxy to ensure that the container data urls are properly constructed. Thanks for the report back Tobias!
-Kyle
Hey @Tobias ,
OttoFMS 4.11.1 removes the callout to the server hostname for the admin api proxy. The Data API Proxy and OData proxy will still call out to the hostname by default, but this behavior can be disabled using an environment variable.
Let me know if you have any further issues with this after upgrading!
-Kyle