Insights
Raspberry Pi remote access: choose and set up your connection
Choose SSH, VNC or Raspberry Pi Connect for remote access. Set up local or browser access and check that it works after a restart.

On this page
You can access your Raspberry Pi with Secure Shell (SSH)Opens in a new tab for terminal commands, Virtual Network Computing (VNC) for its desktop, or Raspberry Pi ConnectOpens in a new tab for either through a browser. For access away from home, Connect handles the network setup without opening router ports. For local terminal access, enable SSH and connect with your Pi's local Internet Protocol (IP) address and your user account.
In short:
- Use SSH: Choose it for terminal commands over a network that can reach your Pi.
- Choose desktop access: Use VNC with a compatible server and viewer, or Connect with a running Wayland desktop.
- Use Connect away: Get browser access across networks without finding network addresses or changing your router.
Choose a terminal or a desktop
Choose the method by what you need to control and how you'll reach the Pi.
| Access method | What you control | Local connection | Away from home |
|---|---|---|---|
| SSH | Terminal commands | SSH client and Pi's local address | A network route that reaches the Pi |
| VNC | Desktop screen share | Compatible server, viewer and Pi address | A reachable route and suitable VNC setup |
| Raspberry Pi Connect | Terminal or existing desktop | Browser and linked Pi | Browser, internet access and linked Pi |
SSH and VNC are protocols, which define how devices communicate. Connect is a browser-based service that handles the connection setup. Your Pi's local address doesn't, by itself, give you access from outside your home network.
Connect's remote shell works on Raspberry Pi OS LiteOpens in a new tab, so you don't need a desktop for terminal access. Screen sharing requires Wayland, the window server used for the desktop, and an existing desktop session. Connect shares that session instead of starting a new one.
Set up browser access with Raspberry Pi Connect
Only configure a Pi you own or administer. Keep local access or a separate working remote method available so you can recover if setup fails.
1. Turn on Connect and link your Pi.
On an existing Raspberry Pi OS installation, turn on the Connect client and link the device to your Connect account. Follow the official Connect setup instructions for your installation.
For a new installation, Raspberry Pi Imager can configure Connect. You don't need to rewrite a working SD card to use it.
2. Sign in from your other device.
Open Raspberry Pi Connect in a browser on your computer, tablet or phone. Sign in with your Raspberry Pi ID, then open the Devices tab.
Your Pi should appear among the devices linked to your account. That listing confirms the account link, not that a desktop session is ready.
3. Choose the interface you need.
Select Connect via beside your Pi. Choose Remote shell for commands or Screen sharing for the desktop.
If screen sharing isn't available, try the remote shell if it's allowed. Then check that the Pi uses Wayland and has a desktop session running.
4. Check that the session responds.
Use the shell or interact with the desktop. A responsive session shows that your chosen interface works from that device and network now.
Connect supports both local and external networks. A direct local connection is faster and more responsive than a route over the internet or through a relay server, which passes traffic between devices.
Set up SSH on your local network
Only change a Pi you own or administer. Keep local access available until you've confirmed that SSH works.
1. Enable SSH on the Pi.
For a new Raspberry Pi OS image, open Raspberry Pi Imager's Customisation > Remote Access tab and turn on Enable SSH. Choose Use password authentication to use your Pi account's username and password.
Choose Use public key authentication if you want to configure an SSH key for login. An SSH key lets your client prove its identity using a key pair instead of the account password.
For an existing installation, follow the SSH setup instructions in Raspberry Pi's official remote-access guidance. You don't need to reinstall the operating system just to enable SSH.
2. Find the Pi's local address.
Check the Pi's network information or your router's device list. Use the address for the Pi's current connection.
Connect your other device to the same local network for this check. Don't treat the local address as an internet-access route.
3. Connect with your own account.
In an SSH client, enter the Pi's local IP address and the username you configured on it. Use that account's password or configured SSH key.
Don't assume a universal default username or password. The account you created on your Pi is the one to use.
4. Confirm terminal access.
A successful login should give you a terminal session on the Pi. That proves your account can get terminal access over this route, not that you can connect from outside your home network.
If you get a connection timed out error, recheck the address and whether your client can reach the Pi. The timeout alone doesn't identify the cause.
For file transfers, Secure Copy Protocol (SCP) sends files over SSH. You can copy files between your Pi and another computer without opening a desktop session.
Check access before you leave home
Run these checks only on a Pi you own or administer. Have another device and an authorized connection from another network ready, and don't restart until you have local access or an independent way to recover.
Connect runs under your user account, so an active user session matters. Lingering keeps the user's services running without another login session, allowing Connect remote shell access after logout. Raspberry Pi recommends lingering for headless Raspberry Pi OS Lite setups, where you use the Pi without a local desktop, to keep access after a remote reboot.
-
Check your intended interface. Open the terminal or desktop you'll actually need and confirm that it responds. This proves that interface works now, not that it will survive a restart.
-
Test Connect from another network. Use an authorized connection outside your home network and try the same interface. Success confirms access through Connect from that network. If only the local test works, resolve external access before relying on it away from home.
-
Restart the Pi and reconnect. Try the same interface from the network you intend to use. Success confirms access after a restart under those conditions. If you need shell access without another login session, also test after logging out of that session.
-
Check user sessions if the shell disappears. If Connect stops working after logout or restart, check the documented user-session and lingering requirements. Turning on the client alone isn't proof that it will remain available without a login.
-
Check the desktop if only the shell works. A working shell with unavailable screen sharing points you toward the desktop requirements, not a blanket network failure. Check that Wayland is in use and a desktop session is running.
To start a desktop session at boot, Raspberry Pi documents Desktop Autologin under System Options in raspi-config. Consider who can physically access the Pi before enabling automatic login.
Don't disable both Connect screen sharing and remote shell from your only remote session. Restoring access then requires the device itself or another remote method, such as SSH.
You're ready to rely on the setup when you can reach the intended interface from the intended network after a restart and know how to recover if it fails. That check doesn't guarantee future availability or prove that other accounts have the same permissions.
Where doxx.net fits. doxx.net is a private network where people and agents share private channels on one network, run on its own IP space, Domain Name System (DNS) root and hardware. For your wider private networking needs, you can create a doxx.net account, download the app and connect a device or agentOpens in a new tab.