💻 Setup Remotely — Browser-Based Remote Support
Deploy a self-hosted remote desktop and IT support platform. Remotely lets you support users from any browser — no third-party cloud required.
📦 Resources & Setup Scripts
Grab the automated bash script from GitHub to follow along with the video.
Quick Install:
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/remote-access/remotely/remotely-ubuntu.sh
chmod +x remotely-ubuntu.sh
sudo bash remotely-ubuntu.shTutorial Steps
1 Download & Run the Script
wget https://raw.githubusercontent.com/mhmdali94/Docker/main/remote-access/remotely/remotely-ubuntu.sh
chmod +x remotely-ubuntu.sh
sudo bash remotely-ubuntu.sh2 Access the Web UI
On first visit, register your admin account:
http://<your-server-ip>:50003 Install the Agent on Client Machines
From the Remotely dashboard, download and install the lightweight agent on any Windows or Linux machines you want to support. The agent connects back to your self-hosted server.
4 Start a Remote Session
In the dashboard, click on a connected device and start a remote desktop or terminal session directly in your browser.
Ports Used
| Port | Purpose |
|---|---|
| 5000 | Remotely Web UI |
Overview
Remotely is a self-hosted remote support and access solution that works entirely in the browser. It is designed for IT helpdesk teams who need to take control of user machines for troubleshooting. It supports Windows and Linux, offers screen sharing, file transfer, and a remote command console — all from a clean web dashboard.
Why Use It
Remotely is a self-hosted alternative to commercial remote support tools like Bomgar, ConnectWise ScreenConnect, or TeamViewer for IT support. It eliminates per-seat licensing costs while giving your helpdesk team full remote control of Windows and Linux machines directly from a browser. Because you host it yourself, sensitive session data stays within your infrastructure. The persistent agent model means machines are accessible for unattended maintenance even when the user is away.
When You Need It
Who Should Use It
Real Use Cases
Main Features
How to Use After Installation
Security Best Practices
Ports and Firewall Notes
Remotely's web UI and agent communication run on port 5000 by default (TCP). This port should be reverse-proxied to HTTPS on port 443 — do not expose port 5000 directly. The Remotely agent connects outbound from managed machines to the Remotely server over WebSocket on port 443. This means no inbound ports need to be opened on managed machines — the agent always initiates the connection. Only the Remotely server needs to be reachable from the internet if managing machines across different networks.
Backup and Maintenance
Common Mistakes
Troubleshooting
Alternatives
ScreenConnect (ConnectWise) and Bomgar (BeyondTrust) are the enterprise-grade commercial equivalents with more features, better support, and compliance certifications — at significant per-seat cost. RustDesk provides self-hosted remote desktop but is designed for peer-to-peer access and lacks the helpdesk workflow features. Guacamole is a better fit for infrastructure access via SSH and RDP but not helpdesk-style agent-based support. For lightweight remote command execution without screen sharing, Ansible or psexec may be simpler and more scalable.
When Not to Use It
Remotely is best for helpdesk-style support of user machines. If you primarily need SSH access to Linux servers, a VPN with direct SSH or Guacamole is simpler. If you manage hundreds of machines with complex policy enforcement, dedicated Unified Endpoint Management platforms like Microsoft Intune handle more scenarios. Remotely also lacks the geographic redundancy and SLA guarantees that enterprise PAM tools provide — for high-stakes regulated environments, the cost of a commercial tool may be justified.
Need Help Setting Up Remotely?
PrismaTechWork provides end-to-end infrastructure services — from initial deployment and security hardening to ongoing monitoring, automated backups, and dedicated support. Whether you need a single-server setup or a multi-site network, our team ensures your infrastructure is built right, secured properly, and maintained reliably.
Frequently Asked Questions
Does Remotely require the end user to be present to connect to their machine?
No. The Remotely agent installs as a persistent Windows service, so machines are available for unattended access even when no user is logged in. This is the key difference from quick-assist tools — you can connect to patch or maintain a machine after hours without scheduling time with the user.
Can I run Remotely alongside RustDesk or Guacamole?
Yes — they serve different purposes. Guacamole is for connecting to existing RDP/SSH services on servers. RustDesk is for peer-to-peer remote desktop. Remotely is for agent-based helpdesk support of managed machines. You can run all three on the same server — they don't conflict.
How do I deploy the Remotely agent to many machines at once?
Generate an installer package from the Remotely dashboard and deploy via Group Policy (Windows), SCCM, Ansible, or any software deployment tool. The generated installer is pre-configured with your server URL and key. For small deployments, the download link from the dashboard works fine for manual installs.
Does Remotely work on Linux machines?
Yes. The Remotely Linux agent supports screen sharing on machines with a desktop environment and full terminal access on headless servers. Install using the script provided in the dashboard. The agent runs as a systemd service and reconnects automatically after reboots.
Is session data stored on the Remotely server?
Session metadata and logs are stored in the SQLite database on your server. Screen content is not stored by default unless you have session recording enabled. Recordings are stored in the application's data directory. All data stays on your server — nothing is sent to external services.
Can technicians see each other's active sessions?
Technician accounts with admin privileges can see all active sessions. Regular technician accounts see only their own sessions. The admin can review session logs for all technicians. This makes Remotely suitable for quality assurance monitoring of helpdesk interactions.
What happens if the Remotely server goes down while an agent is connected?
Active sessions disconnect immediately when the server is unavailable. The agent on managed machines continues to retry connection to the server. When the server comes back online, agents reconnect automatically within 30-60 seconds. No manual intervention is needed on the managed machines.
Can I use Remotely to support Mac devices?
Mac support in Remotely is limited compared to Windows. The macOS agent has basic functionality but lacks some features present in the Windows version. For Mac-heavy environments, consider adding a dedicated Mac remote support tool alongside Remotely. The project is primarily optimized for Windows helpdesk scenarios.