Short answer: Error 131 is a licence failure. Paramount+ decided it could not serve you the video — and in the great majority of cases the reason is your network, not the app. A VPN, a custom DNS, an ad blocker, or an ISP route that looks unusual will produce it while everything else on your internet works normally.
That is why force-closing the app so often does nothing. Start with the test below; it takes a minute and tells you whether you are dealing with a network problem, an account problem, or a device problem.
The one-minute test
Turn off Wi-Fi and play the same title over mobile data, on a phone, with any VPN switched off.
| Result | What it means | Section |
|---|---|---|
| Plays on mobile data, fails on Wi-Fi | Network — VPN, DNS, or your router. Most common by far | 1 |
| Fails on both, on every device | Account session or a Paramount+ outage | 2 |
| Fails on the TV only, phone is fine | Device-specific — app or firmware | 3 |
| Only one title fails, others play | Licensing on that title. Nothing to fix | — |
1. Network causes (start here)
Paramount+ checks that your connection matches the region your account is licensed for. Anything that obscures or reroutes your traffic can fail that check, and the app reports it as 131 rather than telling you what happened.
Turn the VPN completely off
Not just disconnect — switch off any always-on setting or kill switch as well, and confirm no VPN profile is still active in your system settings. Paramount+ actively blocks known VPN and datacentre IP ranges. This applies even if the VPN server is in your own country: it is the IP range that is flagged, not the location.
If you need the VPN running for other reasons, most clients offer split tunnelling, which lets you exclude the Paramount+ app from the tunnel while everything else stays protected.
Reset custom DNS
Custom DNS is the cause people miss, because it is usually set once and forgotten. Streaming services resolve to region-specific servers, and a DNS provider that answers from the wrong region breaks licensing checks. Set DNS back to Automatic in three places: on the device, on the router, and — on Android — under Private DNS in network settings, which is separate from Wi-Fi DNS.
So-called Smart DNS services, sold specifically for unblocking streaming regions, are the most reliable way to trigger 131 of all.
Ad blockers and network filtering
Pi-hole, AdGuard, NextDNS and router-level filtering block the tracking and licensing endpoints Paramount+ calls during playback. Blocked licence call, error 131. Disable filtering entirely as a test rather than trying to whitelist a domain, since the endpoints vary.
Router and IPv6
Restart the router by unplugging it for 30 seconds. If the error persists on Wi-Fi but mobile data works, try disabling IPv6 in the router settings — a partially configured IPv6 setup lets most traffic through while breaking specific services.
2. Account and outage causes
If the error follows you across devices and networks, the network is not the problem.
- Sign out completely and sign back in. A stale authentication token is a genuine 131 trigger. Sign out on the device that fails, not just in the app on your phone.
- Check whether Paramount+ is down. A status tracker will show a spike within the last hour. Error 131 appears in clusters during outages.
- Check your subscription is active. A failed payment can present as playback failure rather than a clear billing message.
- Confirm you are in a supported region. Travelling abroad restricts the catalogue, and blocked titles can return 131 rather than a regional notice.
3. Device-specific fixes
If the error is confined to one device, the fix depends on which:
| Device | What to try first |
|---|---|
| Fire TV / Fire Stick | Settings → Applications → Manage Installed Applications → Paramount+ → Clear cache, then Force stop. Clear data only if cache alone fails. |
| Roku | No cache option exists. Remove the channel, restart the Roku from System → Power, then re-add it. |
| Samsung / LG smart TV | Reinstall the app, then check for a firmware update. Older TV firmware fails DRM checks that newer devices pass. |
| Xbox / PlayStation | Clear the persistent storage (Blu-ray settings on Xbox), then reinstall the app. |
| Apple TV | Delete and reinstall, and check tvOS is current. |
| Browser | Disable extensions, allow third-party cookies for the site, and test in a private window. Chrome and Edge handle the DRM module more reliably than Firefox. |
| Cable box (Xfinity and similar) | The app is maintained by the provider, not Paramount. A box restart, then contacting the provider, is the only route. |
4. If nothing above worked
- Test the same account on a friend’s network. If it plays there, your ISP’s routing is the cause and Paramount+ support can flag it.
- Test a different account on your device. This separates account problems from device problems immediately.
- Check the device’s date and time are automatic — a wrong clock breaks DRM certificate validation.
- If only one show fails, it is a licensing gap on that title and no fix applies.
When you contact support, tell them you have already tested on a second network and a second device. It moves the conversation past the script immediately.
Frequently asked questions
What does error code 131 mean on Paramount Plus?
It is a playback licence failure — the app could not obtain permission to play the stream. It is usually caused by something on your network altering or obscuring the connection, such as a VPN, custom DNS or an ad blocker, rather than by a fault in the app.
Does a VPN cause Paramount Plus error 131?
Frequently, yes. Paramount+ blocks known VPN and datacentre IP ranges, and blocked traffic surfaces as 131. This happens even when the VPN server is in your own country, because the IP range is what gets flagged.
Why does error 131 appear on my TV but not my phone?
Because they are running different app builds and often different DRM implementations. Older TV firmware fails licence checks that phones pass. Reinstall the app on the TV and check for a firmware update.
Is error 131 a billing problem?
Not usually, but a failed payment can present as a playback failure rather than a clear billing message. Check your subscription status if the error appears on every device and network.
Does clearing the cache fix error 131?
Sometimes on Fire TV and Android, where a corrupted cache can break playback. It will not help if the cause is a VPN, DNS setting or outage — which is why the network test above should come first.
What is the difference between Paramount errors 131 and 3005?
Both are playback failures, but 3005 more often points to a connection dropping mid-stream, while 131 points to the licence request itself being refused. The network checks in section 1 apply to both.
More streaming fixes: Netflix error m7361-1253 and TikTok videos not loading.
