Therefore, I'd like to put .htaccess security in front of that.
htaccess really doesn't have anything to do with it.
You need to:
1) Get a static IP setup from your ISP that will point to your network.
2) Route port 80 and 443 traffic from your router to your server.
3) Install an SSL certificate on your FileMaker Server
Once you get that WAN access setup so that your filemaker server is answering to the outside world, then you should just be able to type in:
and get the webdirect login page from anywhere outside of the network.
Filemaker server manages it's own .htaccess files and they really shouldn't be casually fiddled with.
Very helpful. I have 1 static IP address pointing to my firewall. I create Static NATs so that FQDNs that have 'A' records at my registrar find their way to the correct box internally when they traverse the firewall from our one external IP address.
I'm a little concerned about the SSL cert. .I hope I can use a self-signed one..
Self-signed certificates or not installing a valid certificate could result in your users receiving SSL errors in their browser. It should be something that they can override, but doesn’t offer the true security of a valid SSL.
I do not have budget to buy a cert from a third party CA. My users are used to self-signed certs on some internal services. I have my FQDN all set, my DNS all set and my SNAT on the firewall all set. I have generated serverKey.pem and ServerRequest.pem files from FMPro server. I'm at a standstill w/r/t creating and the cert to upload.
Any directions appreciated.