Remote.It Setup & Deployement - FAQ

1. What platforms does Remote.It support?

Remote.It works on Linux, macOS, Windows, Raspberry Pi, OpenWRT, Android, and containerized environments like Docker. It also supports major cloud platforms (AWS, Azure, GCP) for headless deployments.  Complete list of platforms Remote.It supports.

2. Do I need to open ports or configure firewall rules?

No. Remote.It eliminates the need for port forwarding or exposing services to the public internet. It uses outbound-only connections, keeping firewalls closed and secure.

3. Can I use Remote.It behind CGNAT, carrier NAT, or dynamic IPs?

Yes. Remote.It works through any NAT scenario including CGNAT (e.g., Starlink, mobile carriers) and dynamic IP addresses—no static IPs or DDNS needed.

4. How do I register a device with Remote.It?

Install the Remote.It agent on the device, then register it using the CLI or web portal. Once registered, you can define which services (SSH, HTTP, RDP, etc.) to make accessible remotely.

5. What services can I expose through Remote.It?

Any TCP-based service—SSH, VNC, RDP, HTTP(S), MySQL, PostgreSQL, MQTT, custom app ports. You can also use SOCKS5 proxy for broader tunneling needs like browsing or debugging.

6. Can I access devices on a remote LAN from my laptop or mobile?

Yes. Use the Remote.It desktop app (macOS, Windows, Linux) or the mobile app (iOS/Android) to initiate secure connections to your registered services.

7. How do I set up a Jumpbox with Remote.It?

Deploy a lightweight Remote.It-enabled device (e.g., Raspberry Pi or cloud VM) on the remote LAN. Register the device, expose SSH or other tools, and use it to reach private devices in the same network.

8. Can Remote.It be used with Docker containers?

Yes. You can install Remote.It inside a container or on the host, then assign services to container ports. No need to map container ports to the host’s network. You can install our Docker Extension.

9. Does Remote.It support headless or scripted deployments?

Yes. Use the Remote.It Scripting API to programmatically register devices, assign services, and automate fleet onboarding without manual intervention.

10. Is there a way to share access with a teammate or customer?

Yes. You can grant temporary or permanent access to specific devices and services without giving full network access. This supports Zero Trust principles and role-based access.

11. How secure is Remote.It?

Very. No inbound ports are opened. Services are not publicly visible. All connections are encrypted, and you can enable MFA and audit logs for enterprise-grade security.

12. What happens if my device reboots or changes IP?

Remote.It services reconnect automatically—even with IP changes, NAT resets, or reboots. Your connection will remain stable.

13. Can I monitor or audit who accessed my services?

Yes. Audit logging is available for access tracking. For teams, you can also set role-based permissions to limit what users can access and when.

14. How do I scale to hundreds or thousands of devices?

Use Remote.It’s APIs or bulk deployment scripts to register and manage devices at scale. Templates and labels simplify large-scale operations.

15. What’s the difference between a Peer-to-Peer, Proxy, and Jumpbox connection?

• Peer-to-Peer: Direct device-to-device when NAT traversal is successful.
• Proxy: Uses Remote.It relay servers—great for reliability in restricted networks.
• Jumpbox: Access private devices through a secure gateway on the remote LAN.

‍