Hi,
I have 2 servers with ottofms installed on the same network. OttoDeploy can add one just fine. The other it cannot find the otto version. I suspect this is some sort of port forwarding issue. What do I need to do to make this work?
Hey Matt,
OttoFMS should install the necessary port forwarding when it gets installed on the server. It is accessed via port 443 and reverse proxys to 3061.
Are you able to access OttoFMS at the /otto url for that server? I would double check that everything is running properly as well.
Presumably any network limitations would also cause problems with FileMaker Server, so it is likely something going on with the server itself.
-Kyle
1 Like
Hi Kyle, I am able to load otto from both servers but the server that isn’t working in ottodeploy I must go to https://server2.acceleratedapplications.com:444/otto/ for it to load (appending port 444 to the url which I have forwarding to internal port 443 on my router. Otherwise these urls:
https://server2.acceleratedapplications.com/otto
https://server1.acceleratedapplications.com/otto
both bring up otto from server1
Hello,
I don’t think OttoDeploy can’t handle ports other than 443 at the moment. I have to confirm that, but I am pretty sure it is just going to ignore the port you put in and connect to 443. It is something we can look at tackling in a future version, but for right now I don’t think that is going to work. Sorry.
If everything is inside your network, you could setup custom DNS or use a hosts file to route different urls to the different servers. This won’t work if you are trying to get access from out side the network.
You could also use something like ngrok, to get urls that point at those servers.
Hope that helps
Todd