Subscribe not working on port 443

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
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