Same if i try with Postman. When I open otto console from otto deploy on both servers everything looks ok. Am I missing something? COuld there be a problem since I am (dev) in EU and server (prod) in US?
Using OttoDeploy to connect to both servers is not the same as the two servers connecting to each other. There has to be a network path BETWEEN the two servers to do a just in time build. If this test doesn’t return “success” then the path does not exist. I don’t know why there isn’t a path. But the fact that you are in Europe and the the production server is in the US is not the reason.
If you can’t get that resolved, you won’t be able to use a just in time build. But you can still do deployments
You could run the build on your server a head of time and move it manually to the production server and put it in the Inbox manually. Then do the deployment. OttoFMS will notice the file is already in the inbox, and it will not bother to ask the other server to make the build.
Check out these docs for information on builds, advanced options, and deployment patterns.
Thanks I will go through this. Does anything else come to your mind what I could be missing or what could be the reason that servers are not able to see each other?
It could be a VPN, a firewall, a misconfigured DNS, or some other network issue. Your best option is to work with the people who provide the IT support for those two servers.
Sorry i am lost ! I think you comments are in the wrong topics ! On my cases, i can confirm to you that i have install 2 new server ( M4 24/512/10GB) filemaker 21.1.1.40. and 1 m2 pro tooo = total 3!
No issue !
About ottofms:
your installer form terminal not work give an error !
download the mac os x installer, the first time insatll rosetta, after it say taht it is correctly installed but not !
Probably thsi issue ar eonly on new M4 machine !
now i have 1 not able to lunch it , and anothere one taht lgin but after 3 secodn appear the message attached !
The original poster , @John was able to resolve the problem with help from their network admininstrator. Port 443 was not connecting through to the Ottomatic server.