I am new to OttoFMS and I recently installed latest version OttoFMS 4.11 using the install script option on FileMaker Server version 21.1.5 running on Ubuntu 22.04.
I logged into the OttoFMS dashboard using the link https://[host].com/otto and my FileMaker server admin console credentials. However, when I click on any tab on the left pane such as FileMaker server or any button, I get an error message as shown in the attachment below.
I have tried using different web browsers and I get a 500 error with different error messages in each of them. For instance, on Safari, I get “500 something unexpected happened - The string did not match the expected pattern.”, whereas on Firefox, I get “500 something unexpected happened - JSON.parse: unexpected character at line 1 column 1 of the JSON data” error message and on Arc browser, I get “500 something unexpected happened - Unexpected token ‘Y’, “Your machi”… is not valid JSON”
Additionally, when I logged into the OttoFMS dashboard, I was not prompted to download the OttoDeploy.fm12 file so I am stuck and I do not see any of the hosted files under the FileMaker server section.
Any thoughts or insights on how to fix this error and proceed is appreciated.
Thank you.
Also if your Filemaker server has IP Address restriction on it, that might be part of the problem. If restrictions are on and you are accessing OttoFMS from a computer that doesn’t have an acceptable IP address that might cause this. Try connecting from a machine that does. Or temporarily turn off IP restrictions to see of that fixes it.
FileMaker server access is restricted by IP address and I am accessing the OttoFMS from the machine whose IP address has been whitelisted already. When I turned it off, I did not get the 500 error and could proceed with the deployment but the deployment failed (please see the logs below).
you could try adding 127.0.0.1 to the list of allowed IP addresses. That probably shouldn’t be necessary, but I suspect that it might solve that problem.
The other problem is that your Source Server Can’t connect to your Destination server. It can’t see the server over the network.
Did you try Test Connection before you ran the deployment?
Adding 127.0.0.1 to the list of IP addresses did not fix the issue. I was still getting the 500 error. The only way to proceed is to turn off the restricted access on FMS.
I did test the connections before I ran the deployment as shown below.
It was nice to meet you during the office hours today. I updated the source i.e. dev server to the latest version and still got the 500 unexpected happened error. Therefore, having both the source and destination servers to have the latest version of OttoFMS 4.11 didn’t really fix the issue.
I am following up to see if there is any fix for the restricted access issue. I have both the source and destination servers running the latest version of OttoFMS 4.11. Any insight is appreciated.
Sorry, We are still looking into it. So far we have not been able to confirm it as an issue. As soon as we make some progress and can figure out if it is something we can fix we will let you know.
I have the same problem starting version 4.11 on 2 machine ! reisntall open all, no works, say that the port 443 is close but is not ! waiting update ! Thank You
In 4.11.0 the admin api proxy now calls back out to the servers hostname (previously it called directly to the admin server port). Does your server have the ability to call back to itself? Sometimes servers don’t have the DNS set up for that callback. That is the only change in 4.11.0 I could see causing this issue.
also for keep attention taht when you upgrade on apple silicon, the instalaltion not remove the old drive access disk not apple silicon, i was obbliged to remove manually
