6/14/2023 0 Comments Filemaker server ports![]() But for our developers, it means yet another VPN app to manage, and remember which client uses which app. In theory, the dedicated app makes it easy for your users. The difference is if the VPN works with one of the open standards supported by the macOS built-in Network Preferences, or if it has dedicated app that is required to connect. This is another good option, depending on your specific firewall/VPN, as some are not as friendly a others, from our perspective. For instance, if you want to give our developers access, but not anyone else, you can limit access to only the LuminFire office IP. If you don’t want access from anywhere on the internet, you can limit port 5003 access to only certain IP addresses. That way, your users will get the green lock icon in FileMaker and won’t see warnings about the server not being secure. com as an A record to your public DNS and point it to the public static IP of your FileMaker server. For local traffic, you’ll want a local DNS entry pointing at the internal IP as well. Configure DNSįor a custom certificate, your DNS administrator will need to add. Here, all that is required is that your FileMaker Server have a static IP on your LAN (likely already done), and whoever manages your router/firewall then needs to open port 5003 and point traffic to the server. Plus about 1-2 hours for installation and renewals. Here are some ballpark costs that you can expect: In that case, your server address would be. You can save some money by using our shared (called a wildcard) certificate. You can have this be whatever you want as long as you own the domain name. An example that many people use is to tack “fms.” on the front of their domain, so the server address would be something like. If you choose a custom certificate, the main thing to decide here is what your server name should be. You can either buy a custom certificate or user our shared certificate. Purchase and install an SSL certificate on the FileMaker server.Ī certificate for your FileMaker Server can be purchased from LuminFire. There are a few steps that need to be followed for this method. If you open a hole in your firewall, you need to make sure that you do so in a secure way. If you know anything about network security, there should be alarms going off in your head right now. It involves opening a port on your router/firewall between the outside world and your FileMaker server. This is the preferred option, as it provides the easiest access for our developers to work on your system. Option 1: Native remote access via port 5003 We’ll go into the details of what is required for each option, and our preferences. Remote desktop access to a workstation on your network. ![]() Native direct access to FileMaker Server via port 5003.There are three main options for providing remote access, each with various benefits and trade-offs. If you hire us to build or enhance your FileMaker app, that someone is us. But at some point, someone will need access. That’s another conversation, so we won’t judge you too harshly now. Another possibility is that your app doesn’t have a proper security model, so it shouldn’t have outside access. It could be that your users don’t need (or you don’t want them to have) access to the system when they aren’t on-premise. Perhaps you just like maintaining your own server hardware (we can respect that). Maybe you have a very large, complex system, that demands local network speed, or it is an older system that isn’t build on current best practices, so it doesn’t scale well. While an increasing number of business are moving their FileMaker custom apps to the cloud, there are still valid reasons for self-hosting with your own on-site FileMaker Server. This article will outline what you need to enable secure remote access for your on-site/on-premise FileMaker Server for your users and developers. ![]()
0 Comments
Leave a Reply. |