OttoFMS in Docker – “Use proxy” error when accessing port 3061

OttoFMS
1

I’m running OttoFMS inside a Docker container (alongside FileMaker Server).
On Linux 24 Ubuntu
The Otto UI works correctly via the /otto proxy path.

However, when I try to access Otto directly on port 3061 from outside the container, I receive:

{"error":"Can not connect from a remote address. Use proxy"}

Port 3061 is published from the container and the service is listening, but direct access still returns that error.

Is port 3061 intentionally restricted to local/proxy-only access in Docker setups?

Is the supported approach to always use the /otto proxy path instead of calling 3061 directly?

2

Hey @christoalberts ,

OttoFMS intentionally restricts access directly to the port to prevent access without SSL or without going through the FileMaker web server. The intended method is to access via port 443 at the /otto path.

-Kyle