Short answer: Paramount Plus error code 131 is a playback license failure. The app asked Paramount+ for permission to play the stream and was refused, and in the great majority of cases the reason is your network, not the app: a VPN, a custom or “smart” DNS, an ad blocker, or an ISP route that looks unusual. That is why force-closing the app so often does nothing. Run the one-minute test below first; it tells you whether you have a network problem, an account problem, or a device problem, and sends you to the right fix.
The one-minute test
Turn off Wi-Fi and play the same title over mobile data on your phone, with any VPN switched off.
| Result | What it means | Go to |
|---|---|---|
| Plays on mobile data, fails on Wi-Fi | Network: VPN, DNS, ad blocker, or router. Most common by far | Section 1 |
| Fails on both, on every device | Account session or a Paramount+ outage | Section 2 |
| Fails on the TV only, phone is fine | Device-specific: app cache or firmware | Section 3 |
| Fails inside PlayOn, DVDFab, or a screen recorder | DRM protection is doing its job | Section 4 |
| Only one title fails, others play | Licensing gap on that title. Nothing to fix | Section 5 |
What error 131 actually means
Every stream on Paramount+ is protected by DRM. Before the video plays, the app requests a licence key from Paramount’s servers, and the server checks that the request looks legitimate: the account is active, the connection matches a region the account is licensed for, and the device passes its DRM checks. If any of those fail, the licence is refused and the app reports error 131 instead of explaining what went wrong. This is why the error appears on a connection where every other website and streaming service works normally. Netflix, Hulu, and Disney+ run the same kind of check, but each reports it under a different code, which is why one service can fail while the others play.
1. Network causes
Turn the VPN completely off
Not just disconnect. Switch off any always-on setting or kill switch, and confirm no VPN profile is still active in your system settings (iPhone: Settings → General → VPN & Device Management; Android: Settings → Network → VPN). Paramount+ actively blocks known VPN and data-centre IP ranges, and 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 run a VPN for privacy and want to keep it on, use split tunnelling in the VPN client to exclude the Paramount+ app (or your browser) from the tunnel. Users of ProtonVPN, NordVPN, and similar services report that a single flagged server produces error 131 while another server from the same provider works, so switching servers is worth a try before you give up. Be aware that Paramount’s terms prohibit using a VPN to watch content from outside your licensed region.
Reset custom DNS
Custom DNS is the cause people miss, because it was set once and forgotten. Streaming services resolve to region-specific servers, and a DNS provider that answers from the wrong region breaks the licence check. Set DNS back to Automatic in three places: on the device, on the router, and on Android under Private DNS (Settings → Network & internet → Private DNS), which is separate from Wi-Fi DNS. “Smart DNS” services sold specifically for unblocking streaming regions are the most reliable way to trigger error 131 of all.
Ad blockers and network-level filtering
Pi-hole, AdGuard Home, 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, because the endpoints change. Browser extensions do the same thing on a smaller scale (see Section 3).
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, and Paramount+ is a frequent casualty. Also check that your router is not running a “gaming” or “streaming” QoS profile that reroutes traffic.
Mobile hotspot and campus or hotel Wi-Fi
Some carrier hotspots and most hotel, dorm, and office networks route traffic through a shared or foreign IP. Paramount+ treats those like a VPN. If you are travelling, this is the likely cause, and using your phone’s own mobile data is the workaround.
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. If you can, sign out of all devices from your account page on the Paramount+ website, then sign in fresh.
- Check whether Paramount+ is down. Error 131 appears in clusters during outages and during live events such as UFC fights, NFL games, and big premieres. A status tracker will show a spike within the last hour. When that is the case, there is nothing to fix on your side.
- Check that your subscription is active. A failed payment can present as a playback failure rather than a clear billing message. If you subscribed through Apple, Google, Amazon, or Roku, check the billing status there, not on the Paramount+ site.
- Confirm you are in a supported region. Travelling abroad restricts the catalogue, and blocked titles return 131 rather than a regional notice.
3. Device-specific fixes
If the error is confined to one device, the fix depends on which one.
| 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. If the Stick itself is misbehaving, see our Fire TV Stick not working guide. |
| Roku | No cache option exists. Remove the channel, restart the Roku from Settings → System → Power → System restart, then re-add the channel and sign in again. |
| Samsung / LG / Vizio smart TV | Reinstall the app, then check for a firmware update. Older TV firmware fails DRM checks that newer devices pass. On very old sets the app is no longer supported at all, and a streaming stick is the only fix. |
| Apple TV | Delete and reinstall the app, and make sure tvOS is current. |
| iPhone / iPad | Offload or delete and reinstall the app (iOS has no cache-clear button). Check Settings → Screen Time → Content & Privacy Restrictions is not blocking the app’s age rating, and that iCloud Private Relay is off for the test (Settings → your name → iCloud → Private Relay). |
| Android phone / tablet | Long-press the app → App info → Storage & cache → Clear cache. Turn off Private DNS. If it still fails, clear storage and sign in again. |
| Xbox / PlayStation | Clear the persistent storage (Xbox: Settings → Devices & connections → Blu-ray → Persistent storage), then reinstall the app. |
| Browser | Disable all extensions, allow third-party cookies for paramountplus.com, and test in a private window. Chrome and Edge handle the Widevine DRM module more reliably than Firefox. Do not use a browser with DRM disabled or a “de-Googled” browser. |
| Cable box (Xfinity, Cox, Spectrum) | The app is maintained by the provider, not Paramount. A box restart, then contacting the provider, is the only route. Xfinity users in particular have reported long-running 131 issues that only the provider could fix. |
4. Error 131 in PlayOn, DVDFab, StreamFab, or a screen recorder
A large share of the people searching this error are not watching in the official app at all. They are using a recording or downloading tool, and it started returning error 131 after an update. In that situation the error is not a fault you can fix on your side: Paramount+ has tightened its DRM, the tool’s current version cannot obtain a licence, and the official app on the same connection will play normally. Check the tool’s own forum for an update, and understand that downloading protected streams is against Paramount’s terms of service. Nothing in Sections 1 to 3 will change the result.
5. 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 set to automatic. A wrong clock breaks DRM certificate validation.
- If only one show or episode fails, it is a licensing gap on that title and no fix applies. Try again in a day.
- When you contact support, say that you have already tested on a second network and a second device. It moves the conversation past the script immediately.
Other Paramount+ and streaming error codes
Error 131 has siblings. Paramount Plus error code 3005 is a playback failure that usually points at the device rather than the network. If you see the same behaviour on other services, we have guides for Netflix error M7361-1253, Hulu error P-DEV320, HBO Max error 1400500, and Disney Plus error code 83. The pattern is the same across all of them: licence refused, network first, device second.
Frequently asked questions
What does error code 131 mean on Paramount Plus?
It is a playback licence failure. The app could not obtain permission from Paramount’s servers to play the stream. It is usually caused by something on your network altering or hiding 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?
Yes, and it is the single most common cause. Paramount+ blocks known VPN and data-centre IP ranges even when the server is in your own country. Turn the VPN fully off, including any kill switch, or exclude Paramount+ with split tunnelling.
Why does error 131 appear on my TV but not my phone?
Because the phone is usually on mobile data and the TV is on your home Wi-Fi. If the TV fails and the phone works on the same Wi-Fi, the cause is the TV’s app cache or firmware. If the phone also fails on Wi-Fi but works on mobile data, the cause is your network.
Is error 131 a billing problem?
Occasionally. An expired card or a lapsed subscription can show as a playback error rather than a billing notice. Check the subscription status where you pay for it, which may be Apple, Google, Amazon, or Roku rather than Paramount+ itself.
Does clearing the cache fix error 131?
Only when the error is confined to one device. If the error appears on every device on your network, clearing the cache will not help, because the licence is being refused before the app gets that far.
What is the difference between Paramount errors 131 and 3005?
Error 131 is a licence refusal and almost always traces back to the network. Error 3005 is a playback failure that usually traces back to the device, app version, or a temporary server issue. The one-minute mobile-data test separates them.
Why does DVDFab or PlayOn show error 131 when the Paramount app works?
Because Paramount+ has updated its DRM and the tool can no longer obtain a licence. The official app passes the check; the recording tool does not. Only an update from the tool’s developer can change that.
