“Connected” on a phone is not the same as “the internet works.” Starlink Wi-Fi can hand out a local network while the dish still has no usable path. Searches such as “not connecting” and “won’t connect” often describe the same troubleshooting job from different screens.
The first task is to isolate the failure domain: kit status, power, cables, Wi-Fi, or a device that never actually joined. Your app, lights and a second device provide the fastest evidence.
Name what “connected” is lying about
Pick the sentence that matches the room. Then stay on that path.
A. The device shows Starlink Wi-Fi, but every site fails. The local radio to the router is up. The WAN path is not. This is the classic “connected without internet.”
B. The device will not join Wi-Fi at all. Wrong password, wrong SSID, radio off, or the router is not broadcasting. This is not a satellite problem yet.
C. The Starlink app cannot see the kit, or the kit never leaves searching / offline / optimizing. The hardware is not in a state that can offer service. Connecting a laptop will not fix that.
D. One device fails; another on the same kit works. The kit has internet. The failing device, its VPN, or its Wi-Fi band is the domain.
E. Everything worked, then died together. Power, cable, dish view, or a real access-path failure. Still local until proven otherwise.
If the status is specifically “Optimizing connection,” use Starlink stuck on optimizing connection and come back if it never becomes a working WAN. If the path comes and goes, use Starlink keeps disconnecting. This page is for a stuck dead path or a join that never completes.
Check kit status before you reset the house
Open the Starlink app on a phone that can reach the router’s Wi-Fi, or stand next to the kit.
You want a boring, complete picture: dish present, router present, not sitting in a first-boot state, not waiting on an account that was never finished. If the app asks you to pair, complete pairing. A kit that was never commissioned can still show a default SSID.
Read the words on the screen. “Connected” in iOS Settings is cheap. The app’s dish and network panels are the status that matters.
If the app shows a clear obstruction or a dish that cannot see sky, you do not have a mystery WAN. You have placement. The obstruction map is the next document. A dish in a garage, under a metal patio roof, or behind a window is a frequent source of “Wi-Fi works, internet does not.”
If the app is healthy and a second device loads pages, stop tearing down Starlink. Fix the first device: forget the network, toggle Wi-Fi, disable VPN, try Ethernet.
Power, then cables
No network stack survives a brown-out.
- Confirm the power brick is seated at the wall and at the kit. A night-light on the same strip is not proof; starved radios fail first.
- After storms, look for a tripped GFCI or a generator that is not actually in range of the kit.
- Power-cycle in a defined order: unplug the router and dish power, wait, restore dish/router power, wait for boot, then reconnect the phone. Random tapping on a still-booting kit produces “won’t connect” reports that were only impatience.
Cables are the next domain.
- Reseat the cable at the dish and at the router with power off if you are going to touch outdoor connectors.
- Look for pinch points, animal chew, water in a connector, and a cable that is almost in.
- A computer on Ethernet that also has no internet, while Wi-Fi devices also have no internet, points at WAN or dish, not at one laptop radio.
- A computer on Ethernet that does work, while phones do not, points at Wi-Fi, not at Starlink service.
Do not replace the dish because a $5 cable failed. Do not ignore a cable because the Wi-Fi name still appears. The SSID can survive a dead dish path.
Separate Wi-Fi join problems from WAN problems
Will not connect to Wi-Fi
- Confirm you are choosing the current SSID from the app, not an old mesh node or last year’s travel router.
- Re-enter the password from the app. Avoid a password manager’s stale entry.
- Forget the network on the device, reboot the device, join again. Corrupted Wi-Fi profiles are common after you rotate a password.
- Stand next to the router. A join failure two rooms away can be coverage.
- If no device can see the SSID, the router is not up or Wi-Fi was turned off in the app. That is kit status, not a satellite outage.
Joins Wi-Fi, no internet
- Load a site you do not visit daily, to beat cache.
- Try cellular off, so the phone cannot pretend.
- Try a second device.
- If you added a third-party router, bypass, or extra access point, temporarily return to the official Starlink Wi-Fi. How to connect is the overview for a clean join. Extra boxes are a frequent source of “connected to something that is not the WAN.”
VPN, private DNS, and work profiles can pin a phone to a resolver that never answers on this network. Test without them once.
If pages load but calls glitch, you do not have this article’s problem. You have packet loss or delay.
Reconnect in a sequence that produces information
A reconnect is a test, not a superstition. Change one layer at a time and watch which sentence in section one changes.
- Forget Wi-Fi on the client; join again. If that fixes it, the kit was fine.
- Reboot the client. If that fixes it, stop.
- Reboot the Starlink router only; wait until Wi-Fi returns; join again.
- Power-cycle the full kit, including the dish power path; wait longer than you want to.
- Test Ethernet if you have it.
- Remove third-party routers from the path.
- Only then consider moving the dish to a known-open sky as a test, not as a new roof project.
If the kit returns to optimizing or searching for a long time after a power cycle, that is bring-up, not a missing Wi-Fi password. Follow the optimizing article. If it comes up and then dies on a schedule, follow the disconnecting article.
Account and service states belong after the physical path is sane. An unpaid or paused service can look like a dead WAN with a live SSID. Check that in the official account tools, not on a third-party “outage” screenshot.
What not to do
Do not refresh a social feed until someone says the whole network failed. That habit trains you to skip the cable in your hand.
Do not factory-reset as step two. You will lose Wi-Fi names and still have the same crushed connector.
Do not mix this with a mounting redesign until a clear-sky test says placement is the domain.
After the local path works again, use the Connection Outlook to plan a future window. For current terminal and service status, stay with the Starlink app.
When a page finally loads, run a speed test from the device that failed. You are confirming the path, not celebrating a number. If the test cannot start, you are still in this article.