Communication satellite dishes and antennas on a building roof

Starlink App Can't Find Your Dish? A Step-by-Step Troubleshooting Guide

Troubleshooting & Fixes

Independent owner's guide: Starlink Tips is not part of Starlink. Hardware, app menus, service and offers can vary by market and change over time.

Claim Your Free Month

Order through my referral link and activate your service. Your second month of Starlink service will be free.

The Starlink app is useful only when it can reach the right local network and the right Starlink system. If it says it cannot find your dish, shows no equipment, or keeps returning to a connection screen, do not jump straight to a factory reset. The failure may be the phone's network, an app permission, the account selected, a third-party router, or the Starlink hardware itself.

This guide gives you a safe order of checks for the common "app cannot find my dish" problem. Menu names can move as the app changes, and hardware generations differ, so use the current Starlink instructions for your exact kit whenever a screen or connector does not match.

First, identify what the app can and cannot reach

There are two separate connections to test:

Phone to local router: Your phone must be on the Wi-Fi network that can reach the Starlink router.
Starlink system to the internet: The router, dish and service must then be able to complete the satellite connection.

The app may be able to see the router even when Starlink service is offline. It may also show a local network connection while a VPN, guest network, client isolation setting, or third-party router prevents some controls from working.

Write down the exact symptom before changing anything:

The app stays on "connecting" or "searching".
The app says it cannot find a Starlink system.
The app can see the router but reports the dish or service as offline.
The app works on one phone but not another.
The app sees an older or different Starlink system.
The app opens, but local controls and statistics are missing.

That distinction prevents you from treating a phone problem as a dish failure.

1. Check the phone's Wi-Fi connection

Stand close to the main Starlink router and open the phone's Wi-Fi settings.

Confirm the phone is connected to the Starlink Wi-Fi network, not a neighbour's network, a mobile hotspot, a guest network, or a distant mesh node.
If you use a third-party router, connect to the network that actually manages the Starlink connection. During testing, the original Starlink Wi-Fi is the simplest path where it is available.
Turn Wi-Fi off and on once, then reconnect.
If the network name is missing, troubleshoot the router's power and Wi-Fi broadcast before focusing on the app.
If the phone shows "connected without internet", keep testing local app discovery. Internet access and local router access are not the same thing.

If you can, try a second phone on the same Wi-Fi. If the second phone can find the system, the first phone's permissions, VPN, saved network or app installation is more likely than a dish fault.

2. Confirm the app can use the local network

Phones can block local-device discovery even while ordinary internet browsing works.

Check the operating system settings for the Starlink app and allow the local network or nearby-device permission when the operating system offers one. Also check that the app is not restricted from using Wi-Fi or local network access.

Then:

Close the Starlink app completely.
Reopen it while connected to the intended Starlink Wi-Fi.
Keep the phone close to the router while the app searches.
Update the app from the official app store if an update is available.
Restart the phone only after the simpler checks have failed.

If you use a VPN, security filter, private relay, or network-protection app, pause it briefly for one controlled test. Re-enable it afterwards. Do not remove security software permanently just to make the app connect.

3. Check the account and service selection

The app must be signed in to the account that owns or manages the Starlink system.

Check that:

The email address or sign-in method is the one used for this kit.
You have not accidentally opened a different saved account.
The correct service line or location is selected if the account contains more than one system.
The app is not showing an old installation that was moved, replaced, or transferred.
Any account or payment alert is read before changing hardware settings.

If the app can see the local router but shows no service details, the issue may be account selection or service status rather than local discovery. Capture the message and check the account in a browser before resetting the router.

4. Remove the common local-network blockers

The Starlink app needs a usable path to the local router. The following can interrupt discovery:

A guest Wi-Fi network with client isolation enabled.
A mesh node that prevents devices from communicating across nodes or bands.
A third-party router connected behind the Starlink router.
A firewall rule that blocks local device discovery.
A VPN or security application that routes local traffic away from the router.
A phone using mobile data while Wi-Fi appears connected.
A temporary Wi-Fi extender with an incompatible isolation mode.

For one test, use the simplest network you can:

Connect the phone directly to the main Starlink Wi-Fi.
Disconnect optional mesh nodes, switches and third-party routers from the test path if doing so is safe and practical.
Turn off mobile data temporarily so the result is unambiguous.
Open the app beside the main router.
Restore the normal network one device at a time after the app works.

If you normally use bypass mode, the Starlink app may expose fewer router controls because your own router is doing the routing and Wi-Fi work. Test from the local network that reaches the Starlink hardware, and consult your third-party router's settings if local discovery is filtered.

5. Check power and accessible connections

Before touching cables, save a screenshot of the app message and note the time.

With power removed and without climbing onto a roof or opening equipment:

Confirm the router and power supply are connected to a known-good outlet.
Bypass a power strip, extension lead, UPS, inverter or generator for one test where safe.
Look for loose housings, sharp bends, crushed cable, water, corrosion, unusual heat, burning smells or melted plastic.
Reseat only the connectors that your exact kit instructions identify as user-accessible.
Do not force a connector, probe it, use contact cleaner, or substitute a power supply because the plug appears similar.
Keep the router ventilated and the equipment dry.

If there is a burning smell, visible damage, repeated breaker or RCD/GFCI trips, water inside a connection, or a cable that will not seat correctly, stop using the equipment and contact Starlink support. Do not dismantle the router, power supply or dish.

6. Perform one controlled restart

A restart is reasonable after you have recorded the symptom and checked the simple local causes.

Use the app's restart control if the app can reach the router. If it cannot, follow the current instructions for your exact hardware and use one normal power cycle rather than a rapid sequence of unplugging and reconnecting.

After power is restored:

Wait for the router and dish to complete their startup.
Keep the phone near the main router and connected to the intended Wi-Fi.
Reopen the app and check whether local discovery returns.
Test one other device before reconnecting optional networking equipment.
Allow enough time for the system to acquire service before judging the result.

Avoid factory-resetting at this stage. A reset erases Wi-Fi and network settings, and it will not repair a damaged cable, power problem, account issue, obstruction or wider service event.

7. Use the result to choose the next step

The app works on a second phone

Focus on the original phone:

Check local-network permissions again.
Forget and rejoin the Starlink Wi-Fi network.
Disable one VPN or security filter for a controlled test.
Update or reinstall the app from the official app store.
Confirm the phone is not connected through a guest network or isolated mesh node.

The app cannot find the system on any phone

Focus on local access:

Confirm the main router is powered and broadcasting Wi-Fi.
Test the outlet and accessible cable connections.
Remove optional routers and mesh equipment from the path.
Check the router's status and any visible alert.
Wait for a complete boot cycle after one controlled restart.

The app sees the router but the dish is offline

Focus on the Starlink side of the connection:

Read the exact alert and service status.
Check the dish cable and power path for safe, visible problems.
Review obstruction, weather and outage information when the app makes it available.
Check the account and service line in a browser.
Do not repeatedly restart while the system is booting or reporting a wider event.

The app works but has missing controls

A third-party router, bypass mode, account role, unsupported hardware combination, or app version may explain the difference. Compare the behaviour on the main Starlink network and check the current Starlink support instructions for the exact kit.

What to collect before contacting support

Useful evidence is more valuable than repeated resets. Prepare:

The exact app message and a screenshot.
The date, time and timezone when the problem started.
The Starlink hardware or kit details.
Whether the phone was on Starlink Wi-Fi, a third-party router or a guest network.
Whether a second phone or computer could connect.
Whether the router appeared powered and whether the network name was visible.
Any power, cable, account, installation or network changes made shortly beforehand.
The one restart or other checks already completed.

Do not post your account email, precise service address, device identifiers or screenshots containing personal information publicly.

Quick checklist

[ ] Connected the phone to the main Starlink Wi-Fi.
[ ] Tested close to the primary router.
[ ] Tried a second device.
[ ] Checked local-network permissions.
[ ] Paused a VPN or network filter for one test.
[ ] Confirmed the correct account and service line.
[ ] Removed guest-network, mesh and third-party-router variables.
[ ] Checked power and accessible cables safely.
[ ] Recorded the symptom before one controlled restart.
[ ] Avoided a factory reset until the cause is clearer.
[ ] Collected screenshots and test results for support.

The useful question is not only "Can the app find the dish?" It is "Which part of the path is failing: the phone, the local router, the account, the dish connection, or the Starlink service?" Isolate one part at a time, keep changes reversible, and stop when a check becomes unsafe.

For official help, use Starlink Support and include the evidence from this checklist.