HTTPS Connections to M-Files Server

The communication between M-Files Server and the M-Files clients can be accomplished by using various connection protocols. Cloud-based servers (as well as the M-Files Web client and the M-Files mobile applications) only accept communication via the HTTPS protocol, whereas the default way for M-Files Desktop to communicate with an on-premises M-Files server is to use the Remote Procedure Call (RPC) protocol (TCP/IP, port 2266). Since this mode of communication does not require any additional configuration steps, it is usually the preferred way of communicating inside the organization's internal network.

In some situations, however, it is preferable to enable M-Files Desktop to communicate with M-Files Server via the HTTPS protocol instead of RPC. This is especially useful if clients are connecting from outside the company's internal network. HTTPS connections are always encrypted and are typically not blocked in hotel networks or other public networks.

For instructions on how to enable "RPC over HTTP with SSL" communication between M-Files Desktop and M-Files Server, refer to the document Enabling RPC over HTTPS connections to M-Files Server. With the configuration described in the document, all traffic from M-Files Desktop is encrypted and tunneled through TCP port 443.

Once the "RPC over HTTP with SSL" connections have been enabled on the server, end users will be able to use the HTTPS protocol while adding or editing a document vault connection in M-Files Desktop Settings.