Hi,
my client runs their FileMaker Server in their home, and recently moved to Comcast. It's a big bandwidth improvement, but it appears that Comcast blocks port 80, so Subscribe no longer works. We want to use port 443, which looks like it should work. However, while https://client-ip-address shows the filemaker web server test page, https://client-ip-address/seedcode_subscribe_engine/ results in "The requested URL was not found on this server. The link on the ">referring page seems to be wrong or outdated. Please inform the author of ">that page about the error. If you entered the URL manually please check your spelling and try again." We're using the self-signed certificate.

Is there something else I have to do ( besides toggle HTTPS in Subscribe Setup ) to get this to work? Will adding a public signed cert address this issue?

Thanks,
-jb

Hi JB,

Thanks for reaching out to us here. It looks like our documentation may not be up-to-date on where the seedcode_subscribe_engine folder should be placed, if you are using HTTPS with FileMaker Server on a Mac. Are you using a Mac machine for your server? If so, move the seedcode_subscribe_engine folder (or copy it) to this folder (subfolder of where the engine is currently located):

/Library/FileMaker Server/HTTPServer/htdocs/httpsRoot

Please let me know if this change gets Subscribe working for you using HTTPS!

All the best,

That works great.

Thanks for your help,
-jb

Awesome, JB!

Thanks so much for confirming. I've updated our docs on the installation of the seedcode_subscribe_engine folder with the required file path for using HTTPS on Mac.

Thanks again,