Apologies in advance if I am missing something in plain sight. I am trying to add a server to OttoDeploy, however, when trying to test the server before adding, it will tell me that I don’t have OttoFMS installed on the server. It does recognize my FMS version though.
Below is a screenshot of the error and also a screenshot of the OttoFMS login in page showing my FMS version along with the OttoFMS version. Any ideas on what I am potentially missing?
Screenshot of error: ( I masked the URL but it is in there)
Are you by any chance White Listing IP addresses through the Admin Console? Because if you are, you will need to add your computer’s IP address to that for OttoDeploy to connect to the server fully.
Thank you for getting back to me, I appreciate it!
I just went in and checked and have no white listed IP addresses through the admin console. I even went ahead and added both IP addresses, whitelisting both our Production server IP address and our Development server IP address and tested at that point and I still get an error that OttoFMS is not installed on either server.
I can try uninstalling OttoFMS potentially and re-installing, but I’m not sure if that would be even remotely helpful.
I am using https and I am currently using the Claris self-signed cert. I am not entirely sure how to go about getting a proper ssl cert, although I would prefer to, especially if it will resolve this issue.
I have a similar problem. I use self-signed certificates on two test servers in my local network. If I try to add these machines I get this error. When I try to add a server located in AWS with a proper SSL certificate - all work well.
Sorry but we do not support self signed certs at this time. We are working towards some options for handling this in the future, but we don’t have any time line for this yet.
Right now, the easiest thing to do here is to just get a valid cert or use something like ngrok.
Question, should this work via just IP address without SSL at all, or is SSL required? When we try to add a FM server were seeing the FM version, but its claiming that OttoFMS is not installed when adding a server using 192.168.2.15 for example.
Thanks for the reply, Todd, if I may suggest a few things; your previous comment asking if http or https was in use sort of lead me to believe that http would be supported, which is also suggested by this document Coming from Otto v3? | OttoFMS where its mentioned that V3, and presumably newer, work on the same port as file maker, 80/443, which also seems inaccurate since 80 is plain text no SSL. I also did not see anything in the setup documentation that mentioned this requires a FQDN and proper, not self signed, SSL.
This is not particularly useful. For example, I have an FMS at home just for development purposes, so I don’t need a certificate since no one is accessing it from outside. However, it would be quite useful if I could deploy solutions to my clients’ servers through Otto.
Hi @toddgeist .
i have the same problem, but i’m using normal Lets Encrypt SSL certificate.
OttoDeploy can find FM Server version, but Otto version us unknown.
I dont have any IP Filtering.
Trying to connect from OttoDeploy on the same server, also from other servers, still the same issue.
Any ideas what can be a problem?
Thank you.
Let’s encrypt certs should work just fine. So maybe you have a different problem.
I am going to lock this thread as it has become quite long and bit unfocused. Could you please start a new thread, and answer this questions about your problem.
Can you access the OttoFMS web console from your server?
Can you access the FileMaker Server Admin Console?
What does OttoDeploy show when you try to connect? Can you send a screenshot?
Title the thread something like “Can’t connect using Let’s Encrypt Cert”
We can work out what is going on there. It will be much more valuable to the community as a separate discussion.
Thank you, sorry to ask you to do a bit of extra work, but it will really help us keep the content here useful.
