When I try to add a server that has port forwarding setup, it doesn’t seem to be able to connect. I know the server has OttoFMS Installed, and I’m able to successfully access the server’s OttoFMS console using the port, but it doesn’t seem to work when I try to add the server to OttoDeploy. When I type in the URL I’m specifying the port number at the end, like this:
https://example.exampe.com:8022
It’s forwarding 8022 to 443 in this example. I get the following error:
Hello,
Yes, port forwarding is not currently supported. We worked really hard on getting rid of the port 3030 requirement. We just didn’t think of allowing other ports. But I can see the value of allowing it. We’ll see if we can add it. In the meantime you could use something ngrok - https://ngrok.com/ to expose your server over a different domain.
Thanks
Todd
Awesome, thank you so much!!
Hi, Just wondering if there has been any progress on this. I am hoping to set up Otto at a client site where they use ports 80 and 443 for webmail.
Thanks
Tim
Hi Tim,
We did look into it, and while I understand why it might be useful, it is pretty far down the list of priorities. Like probably all the way down at the bottom.
FileMaker Server uses ports 443, and we are going to stick with that for the foreseeable future.
Sorry
Todd
Ok, Thanks Todd.
Congratulations on the Innovation Excellence award - well deserved.
I have tried to set this up with a vpn (see my post https://community.ottomatic.cloud/t/ottofms-not-installed-message-when-verified-running-vpn-issue/1130?u=tima) .
If you have any suggestions …
Cheers
Tim
Hi @toddgeist
I’d just like to add a +1 to this - I know you said the priority was low and I completely understand that, however I’ve now got two clients who are using port mapping on their firewall such that the FMS admin console is accessible via port 8443 and I’d love to be able to get to OttoFMS on that server over that port.
Thanks
Steve
