
Starlink Is Online but Websites Show Certificate Errors: Check Device Time First
Troubleshooting & Fixes
If Starlink shows online but a browser or app reports a certificate error, “connection is not secure,” or a failed login, check the device clock before changing the dish, router or DNS.
A device with the wrong date or time can reject a website certificate that is not valid yet or has already expired. It can also make sign-in tokens look invalid. The internet path may be working normally.
Start with a two-device check
- On the affected device, write down the exact error and the displayed date, time and time zone.
- Connect a second phone or computer to the same Starlink network.
- Open the same website or app on both devices.
- Try one unrelated, well-known website as a control.
Use the result to choose the next step:
- Only one device fails: treat the device clock, browser session, security software or local network settings as the first suspects.
- Several devices fail with the same certificate error: check the router, firewall, DNS filtering and any captive-portal or content-filtering system.
- Nothing loads on any device: this is more likely a connectivity, power, obstruction or service problem than a certificate problem.
Do not disable certificate warnings to get around the error. They are useful evidence, and bypassing them can expose passwords and private data.
Set the date, time and time zone automatically
The menu names vary by operating system, but the goal is the same: use automatic time and the correct time zone.
Windows
Open Settings > Time & language > Date & time. Turn on automatic time and, if appropriate for the device, automatic time zone. Use Sync now if it is available. Check the displayed date, clock and time zone after synchronisation.
macOS
Open System Settings > General > Date & Time. Enable automatic date and time, then confirm the selected time zone. If the Mac repeatedly loses time after shutdown, investigate its power and clock hardware rather than repeatedly changing the time by hand.
iPhone or iPad
Open Settings > General > Date & Time and turn on Set Automatically. Confirm that the time zone is correct. If the control cannot be changed, check whether Screen Time, device management or another restriction is controlling it.
Android
Open Settings > System > Date & time, or search Settings for “date and time.” Turn on the options that use the network-provided time and time zone where your device offers them. Android menu names differ between manufacturers.
After making the change, close and reopen the affected browser or app. A previously failed sign-in session may need a fresh attempt.
If automatic time will not synchronise
A managed router, firewall or DNS filter can interfere with time synchronisation even when ordinary web browsing works.
- Check whether the device can resolve ordinary website names.
- If you administer the network, verify that outbound Network Time Protocol traffic is allowed. NTP normally uses UDP port 123; it should be allowed out to an approved time service, not forwarded from the internet into your home.
- Temporarily compare the affected device on another trusted connection, such as a phone hotspot. Do this as a diagnostic test, not as a permanent workaround.
- If time works on the alternate connection, review the home router, firewall or DNS-filter logs.
- If the clock falls behind again after every reboot, check the device battery, power state, management policy or operating-system health.
Do not change the system clock to make one expired certificate appear valid. Fix the time source instead.
Retest without making the problem harder to read
Once the clock is correct:
- Reopen the website or app.
- Retry the sign-in from a new session.
- Test a second unrelated website.
- Check whether the error appears on another device on the same Starlink network.
- Record the local time and the exact message if the problem remains.
Avoid factory-resetting the Starlink router or changing several DNS settings at once. Those actions can erase useful evidence and do not fix a clock that is wrong on one computer or phone.
When to continue with Starlink troubleshooting
Move beyond the device clock when:
- The date, time and time zone are correct on every affected device.
- Multiple devices fail in the same way.
- A different connection produces the same error.
- The error is a DNS refusal, HTTP 403, timeout or complete loss of connectivity rather than a certificate or secure-connection warning.
At that point, check DNS filtering, firewall rules, browser or app-specific settings, and the Starlink app's service status. Keep the original error text and the two-device comparison; they are more useful than a generic screenshot saying that the internet is “not working.”