The error message says to check your internet connection, which you have already done three times, and it is fine. This message is one of the least helpful in consumer software, because apps display it for almost any failure to reach their servers, regardless of the cause. Your connection is usually not the problem.
The short answer
The four real causes are a wrong system clock, a DNS problem, a corrupted app cache, and the service’s own servers being down. Check the date and time first because it is instant and catches a surprising number of cases, then clear the app cache, then change DNS. Check the service status page before spending long on any of it.
Why the clock matters so much
This is the cause people never guess. Streaming apps connect over encrypted connections, and those connections validate a certificate that is only valid within a specific date range. If your device’s clock is wrong by more than a few minutes, the certificate appears invalid and the connection is refused.
The app has no useful way to explain that, so it tells you to check your connection. Devices that have been unplugged for a while, or that lost their clock during a power cut, are the usual victims. Set date and time to automatic, confirm the time zone, and try again.
Check the service is actually up
Look at the service’s status page or social media on your phone. Outages are common enough to be worth thirty seconds of checking before you spend an hour on your own equipment.
Check the date, time and time zone
Set it to automatic. If it is already automatic but wrong, the device is failing to reach a time server, which points at the same network or DNS problem causing the app failure.
Run the device's own connection test
Most TVs and streaming devices have a built-in network test. If it reports a connection but no internet, your problem is DNS or something beyond the router. If it reports a good connection, the fault is specific to the app.
Clear the app cache and data
In the device’s app settings, clear the cache first, then the data if needed. Clearing data signs you out, so have your login ready. A corrupted cache produces exactly this error and is a very common cause on older TVs.
Change the DNS server
In the device’s network settings, set DNS manually to a public resolver instead of automatic. If your provider’s DNS is failing, apps cannot resolve the addresses they need while general browsing may still work from cached entries.
Power cycle the device fully
Unplug the TV or streaming device at the wall for a minute, not standby. This clears memory in a way that a soft restart does not, and on older smart TVs it is the fix more often than anything else.
Turn off any VPN or custom DNS filtering
VPNs are actively blocked by most streaming services, and ad-blocking DNS services sometimes block the domains apps use for authentication. Disable both and test.
Reinstall the app
Uninstall completely, power cycle the device, then install fresh from the store. This resolves a corrupted installation that clearing data does not reach.
Test the same app on your phone using mobile data rather than Wi-Fi. If it works there, the service is up and your account is fine, which narrows the problem to your home network or the device. If it fails there too, the problem is the service or your account.
The DNS problem in plain terms
Every connection starts by converting a name into a numeric address, and that lookup goes to a DNS server. If that server is slow or failing, your device has a working connection and simply cannot find out where the streaming service lives.
What makes this confusing is that some things keep working. Your browser has cached entries, other apps use different domains, and the router may have its own cache. So the connection appears healthy while one specific app cannot reach its servers. Setting DNS manually to a reliable public resolver is a safe change and an instant test.
Account and device-specific causes
- Too many devices signed in. Some services cap this and report it badly. Sign out of devices you no longer use from the service’s website.
- An expired payment method. Occasionally surfaces as a connection error rather than a billing message.
- An app version no longer supported. On older TVs, services drop support and the old app fails rather than prompting an update.
- Region mismatch. If a VPN was used previously, the account may be flagged, and the service refuses to connect.
If the TV is more than about six years old and several apps fail this way, the likely cause is that its platform is no longer supported. No amount of troubleshooting fixes that. An external streaming device on an HDMI port is the practical answer and costs far less than a new television.
Why does the app say check connection when my internet works?
Because apps show that message for almost any failure to reach their servers. A wrong clock, a DNS failure or a corrupted cache all produce it, and none of them are connection problems.
How does the wrong date break streaming?
Encrypted connections validate certificates against the current date. A clock that is wrong makes valid certificates appear invalid, and the connection is refused.
Will changing DNS improve streaming generally?
It can make lookups faster and more reliable, which shortens app startup times. It does not increase your bandwidth, so it will not fix buffering caused by a slow connection.
Why does it work on my phone but not my TV?
Different device, different app version, different network path and different DNS settings. It usually means the service and your account are fine, and the problem is the TV or its network configuration.
Does using a VPN cause this error?
Frequently. Most streaming services detect and block VPN traffic, and the app reports it as a connection problem rather than explaining what happened.
The bottom line
Check the service status and the device clock first, because both take seconds and between them explain a good share of these. Then clear the app cache and change DNS. The error message is misleading by design, so do not waste time testing a connection that is already working.
