Making Connections


You can make connections to services using either (web portal), the Desktop app, CLI or Mobile app.

The web portal is only capable of proxy connections which will last for 8 hours or until 15 minutes of inactivity, whichever comes first. 

The Desktop App and CLI provide the ability to make Peer to Peer (P2P) Connections as well as Proxy connections (the default is Peer to Peer with Proxy Failover). They also provide a fixed url and port for connections where the connection will go idle after inactivity, but reconnect on demand. When able to connect via P2P, connections are quicker connection times, faster data throughput, and higher security.

The Mobile App is able to make Peer to Peer and Proxy connections. When a proxy connection is established, it will also timeout with the same rules as the web portal.

Making Connections

To make a connection in the web portal or Desktop App, first navigate to the Devices or Networks page. If you are a member of an Org or have items shared to you, you may have access granted via Device list or Networks. Click on the Device or Service you wish to connect. Click the Start or "Connect and Launch" button.


Optionally there may be advanced configurations that you can set for your connection such as routing, launching connection via application or url, launch url (for example, if you need to add a path to your HTTP(S) url), and other configurations that may be available for the service type such as username.



The Connections Page

The Connections Link in the left nav is helpful for keeping track of your current and most recent connections. On this page you can see all of the Services you are connected to in one place, so you don't have to sort through your Device list to find your connections.


The Networks Page

The Networks Link in the left nav is helpful to group a set of services which you can share in Organizations or via Guest.


Using a Connection

Once you create a connection, you can use the url that Remote.It provides in your application that will use it. For example, if it is an HTTP/S connection then you can use the full url (including ":x" which is the port). For some applications you may only enter the host part of the url (the portion before the :) and enter the port separately.






Was this article helpful?
1 out of 1 found this helpful