Once Starlink hardware is powered and the dish can talk to the router, connecting a device is ordinary networking: join the Starlink Wi-Fi, plug into Ethernet, or put a third-party router behind the kit. This guide starts after the dish and power path are installed.
If the hardware is on but nothing reaches the internet, skip ahead to Starlink connected without internet. If the app sits on “Optimizing connection,” use that status guide. Use the official app and hardware manual for model-specific buttons and port layouts.
Start from powered hardware, not from the roof
Assume the dish and router (or an all-in-one Mini-style kit) already have power, the outdoor cable is seated, and the router has finished booting. Lights or the app should show that the local network exists. You are connecting clients to that network.
You need three facts from the kit, not from a forum:
- The Wi-Fi name (SSID) the Starlink router is broadcasting.
- The Wi-Fi password the app shows for that network.
- Whether this hardware exposes Ethernet, and which port is LAN versus a special adapter.
Those values live in the Starlink app after the kit is paired. If you never completed pairing, do that before you chase device settings.
The Starlink app is the control plane
Install the Starlink app from the official store for your phone. The app is how you see kit status, Wi-Fi credentials, optional bypass settings, and obstruction tools.
Typical first join:
- Power the kit and wait until the router is broadcasting Wi-Fi. That can take a few minutes after a cold start.
- On the phone, open Wi-Fi settings and join the Starlink network the kit created. Some setups use a temporary network or a Bluetooth assist for the first pairing; follow the in-app prompt rather than a third-party screenshot.
- Sign in with the Starlink account that owns the kit.
- Confirm the app shows the dish and router as present. A phone that is on Starlink Wi-Fi with an empty app is not fully commissioned.
After pairing, the app is also how you rename the SSID, rotate the password, and see whether the kit thinks it has service. Keep the phone on Starlink Wi-Fi when you are changing those settings so you are not editing a neighbor’s memory of an old password.
If the app cannot find the kit, you have a local-network or power problem, not a “how do I enter the password on my laptop” problem. Resolve the kit first.
Connect a phone or tablet over Wi-Fi
This is the common path.
- Open the device Wi-Fi list.
- Select the Starlink SSID from the app.
- Enter the password exactly as shown. Extra spaces and a wrong keyboard layout are the usual failures.
- Wait until the device says it is connected. Then load a simple page or run a known app.
On iPhone and Android, “Connected” can still mean “connected to the router only.” If the Wi-Fi icon is on and every site fails, you are in the connected-without-internet case. Stay on this page only if pages load.
Guest networks, device isolation, and “private Wi-Fi address” features rarely prevent a basic join. They can confuse parental-control setups and some office devices. If one phone joins and another does not, forget the network on the failing phone and join again before you reset the dish.
Keep the Starlink router’s Wi-Fi name distinct from an old home router you left plugged in. Two networks with similar names produce a phone that “connects to Starlink” while it is still on the leftover ISP box in the closet.
Connect a computer over Wi-Fi or Ethernet
Wi-Fi on a computer is the same SSID and password. Prefer 5 GHz or the band the app recommends when you are in the same room as the router. A laptop in a far bedroom is a coverage test, not a Starlink test.
Ethernet is the cleaner path for a desk, a TV, a wired access point, or a third-party router.
- If the Starlink router has a LAN Ethernet port, plug the computer in and set the computer to automatic (DHCP). Do not invent a static IP unless you already run a managed network.
- Some kits need an official Ethernet adapter. If there is no port, look up that hardware’s current adapter rather than cutting a cable.
- Use a known-good cable. A failed cable mimics a Starlink outage on one PC and nowhere else.
When the computer shows a valid address on the Starlink network and a browser loads, you are done with “how to connect.” Tuning Wi-Fi mesh, VLANs, and office firewalls is ordinary LAN work. It is not unique to Starlink.
If the computer connects and then drops every few minutes, that is keeps disconnecting, not a missing password.
Use a third-party router without turning this into a lab
Many households want their own Wi-Fi mesh, firewall, or existing SSID. Starlink can feed that router. Exact menu names change by kit generation, so treat this as the shape of the setup, not a button-by-button script.
Overview:
- Get a working Starlink path with the official router first. If the official kit cannot reach the internet, a third-party box will not either.
- Connect the third-party router’s WAN port to a Starlink LAN Ethernet port (or the official adapter).
- If you need the third-party router to be the only DHCP server, put the Starlink router in the bypass / bypass-style mode the app offers for that hardware. The point of bypass is to stop double NAT and two competing Wi-Fi systems. The name in the app may differ; the idea does not.
- Disable the Starlink router’s Wi-Fi if you are fully replacing it, so devices do not roam back to the old SSID.
- Reconnect phones and computers to the third-party SSID. They are no longer “on Starlink Wi-Fi”; they are on your LAN, which uses Starlink as the WAN.
Do not daisy-chain extra routers “just to see.” Double NAT plus two meshes is a reliable way to make calls worse while the dish is fine.
Bypass has a cost: some Starlink app features expect the official router to be in the path. If you still need the app’s local statistics, read the current in-app notes for bypass before you commit. Overview is enough here: official kit works, Ethernet to your router, one DHCP domain, one Wi-Fi system.
Travel routers and “Starlink to Ethernet to hotel TV” gadgets follow the same rule. They are clients or they are the WAN router. They should not be both.
Confirm the join, then stop
A successful connection is not a feeling. It is a device that:
- holds a Wi-Fi or Ethernet association to the network you intended,
- receives an address automatically,
- loads a page that is not cached,
- and, if you care about quality, survives a measurement.
Run a Starlink speed test from the same phone or computer you just connected. That is the primary next step: you are checking that this device has a real path, not chasing a plan-speed myth. How to read the results keeps download, upload, and delay from collapsing into one number.
If the test never starts, you are not connected in the internet sense. Go to the no-internet checklist. If the test starts and looks chaotic only far from the router, fix Wi-Fi coverage. If it looks chaotic on Ethernet next to the kit, you have an access-path issue, not a join issue.
You do not need TNET to complete a Wi-Fi join. After the device is on, the connection outlook is for planning a place and time, and how the service works is for what TNET will and will not claim. Neither page replaces the Starlink app on the router table.