How to fix streaming error code 232001 in Windows?

Error code 232001 comes from JW Player, the video player many news, sports and streaming sites embed: the player asked the server for the stream's playlist file and no answer came in time. Reload once, then test without your VPN or proxy and on another network, because the cause is almost always the connection path or the website itself.

Facts checked on 14 October 2026. Steps written for Chrome 155, Microsoft Edge and Firefox on Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What error code 232001 means: "This video file cannot be played"

232001 is a code from JW Player, a commercial video player that thousands of websites embed instead of building their own. Its documentation now carries the JWX name. When the player cannot go on, it shows a short message and puts the code in brackets, so the reader sees This video file cannot be played. (Error Code: 232001).

JW Player's reason

"An HLS manifest request timed out."

Text on the screen

"This video file cannot be played."

Group

Media Playback HLS.JS, the part of the player that plays HLS streams in browsers

Kind

An error, not a warning: it stops the player and shows the code to the viewer

Other spellings people search

232 001, 23 2001, 23200 1, error code: 232001, (error code: 232001)

HLS (HTTP Live Streaming) cuts a video into short pieces. Before the first piece can load, the player downloads a small text file, the playlist or manifest, whose address ends in .m3u8. It lists the qualities and the pieces. 232001 says that this very first request did not finish in time. The video file itself was never reached, so the message "This video file cannot be played" is misleading: the file may be perfectly fine.

How long the player waits depends on how the website set it up. In the current release of hls.js, the open-source library behind this part of the player, a manifest request gets 20 seconds to finish and is retried up to 2 times after a timeout. We could not confirm which hls.js version or settings JW Player ships, so the wait you see before the code can be shorter or longer.

What causes error 232001, from most to least common

A timeout has two ends: the server that should answer and the path your request takes to it. The order below is our reading of the code's meaning and of what users report on forums. No vendor publishes how often each cause happens.

Three tests that show whether 232001 is your problem or the website's

Before you change any setting, spend five minutes finding out who can fix it. If the website's server is slow, nothing on your PC will help, and the best move is to wait and report it.

1. Test 1: open two or three other videos on the same website. If none of them plays, the site's video service is the likely cause.
2. Test 2: turn off your VPN, connect the PC to your phone's mobile hotspot, and play the same video. If it plays, the problem sits in your usual network path.
3. Test 3: open the page in a private window (Ctrl + Shift + N in Chrome and Edge, Ctrl + Shift + P in Firefox). If it plays there, an extension or stored site data is involved.

How to fix error code 232001

Fixes 1 to 6 are for viewers, ordered from the most common cause to the least. Fixes 7 and 8 are for people who run a website with JW Player. Use the table to start at the right place.

Fix 1. Wait a minute, reload the page and try another video

2 minutesNo riskEveryone who sees the error for the first time, especially during a live event.

A timeout is often a moment of overload: the server answers again a minute later. A full page reload also asks the website for a fresh player setup and, on many sites, a new stream address.

1. Wait about one minute. Do not press Play again and again: every attempt sends the same request to a server that is already slow.
2. Reload the whole page with F5 or the Reload button, not only the player.
3. Press Play and give the video up to a minute to start.
4. If it fails, open another video on the same site and play it.
5. If no video on the site plays, look at the site's or its social media account's status messages, then go to Still not working to report it.

Fix 2. Turn off the VPN or proxy and try another network

5 minutesNo riskYou use a VPN, a proxy, a work or school network, or a DNS service that blocks ads or trackers.

A VPN or proxy adds a hop between you and the video server. If that hop is slow, overloaded or blocked by the video service, the manifest request waits until the player gives up. Users report 232011 and 232001 together with VPN services, which fits this path.

1. Disconnect your VPN in its own app, or switch it to a server in your own country.
2. In Chrome open More > Settings > System and select Open your computer's proxy settings. Windows opens Settings > Network & internet > Proxy.
3. Under Manual proxy setup, check whether a proxy server is turned on. If it is and you did not set it up, note its address before you change anything.
4. Reload the video page and press Play.
5. If it still fails, connect the PC to your phone's mobile hotspot with the phone's Wi-Fi off, and try again.

If you use a DNS filter such as a Pi-hole or a parental control service, pause it for one test or add the video site's domains to its allow list. A filter that sends the stream's domain into a dead end can turn into a timeout for the player.

Fix 3. Play the video in a private window, then turn off extensions one by one

5 minutesNo riskThe video fails in your normal browser window but you have not tested a private window yet.

Ad blockers, privacy tools and download helpers watch every request a page makes, including the .m3u8 request. Chrome and Edge do not run extensions in private windows unless you allow it, so a private window is a quick test without them.

1. Press Ctrl + Shift + N in Chrome or Edge, or Ctrl + Shift + P in Firefox, to open a private window.
2. Paste the video page's address and press Play.
3. If it plays, go back to a normal window and open chrome://extensions (Chrome), edge://extensions (Edge) or about:addons (Firefox).
4. Turn off one extension with its switch, reload the video page and press Play.
5. Repeat until the video plays. The last extension you turned off is the one that interferes.
6. Turn the other extensions back on. For the culprit, add the video site to its allow list or keep it off on that site.

• Ad blockers and script blockers: most often involved, because video players load ads and the stream from related domains.
• Privacy and tracker blockers: they may hold back requests to a CDN they do not trust.
• Video download helpers and "force HD" tools: they rewrite or repeat stream requests.
• VPN or proxy extensions: they act like Fix 2 inside the browser only.

Fix 4. Find the request that times out in the browser's developer tools

5 minutesNo riskYou want to know for sure whether the manifest hangs before you report it or change more settings.

The browser's Network panel lists every request with its status and timing. The .m3u8 row shows directly whether the player's request waited for the server, failed, or was blocked on your PC.

1. On the video page press F12 (or Ctrl + Shift + I) and open the Network tab.
2. Type m3u8 in the Filter box.
3. Reload the page with F5 and press Play.
4. Watch the rows that appear. Note the Status of the first .m3u8 row and how long it stays without a status.
5. Select the row and open the Timing tab. A long Waiting (TTFB) time means the server is slow to answer. Long DNS Lookup, Initial connection or Proxy negotiation times point to your path.
6. To save proof for the site's support, right-click any row and choose Copy > Save all listed as HAR (sanitized).

Chrome's own network log is a second option for a support ticket. Open chrome://net-export, select Start Logging to Disk, reproduce the error and stop the log. Leave Strip private information selected.

Fix 5. Clear the DNS caches and check the connection on Windows

10 minutesLow riskSeveral sites load slowly on this PC, or the DevTools timing showed a long DNS lookup or connection time.

Video services move their streams between CDN servers. A stale or slow DNS answer can point the browser to an address that no longer answers fast, so the manifest request runs into the timeout.

Start with Chrome's own DNS cache. Open chrome://net-internals/#dns and select Clear host cache. Then reload the video page.

Then clear the Windows DNS cache. These are the first two steps of the network reset; you do not need the full reset for this error. Step by step: Reset the network and flush DNS

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

   

2. Flush the DNS cache. Type the command below and press Enter. Windows forgets the website addresses it looked up earlier and asks for them again.

   ipconfig /flushdns

These steps were written for Windows 11 24H2 and later. The full page with the other versions and what each result means: Reset the network and flush DNS

1. Restart the router if other devices at home are slow too.
2. Run the connection checks in How to check your internet connection in Windows to see whether the PC has a weak link, high latency or packet loss.
3. If you use Wi-Fi, test once with a cable or closer to the router.
4. Reload the video page and press Play.

Fix 6. Delete the site's stored data and update the browser

5 minutesLow riskOnly one website fails, it works in a private window, and no extension was the cause.

Some sites sign stream addresses with a token that expires. An old copy of the page or old site data can hold such an address. An outdated browser can also miss fixes in the way it handles media requests.

Clear the cached files, and the cookies of the site if needed. Step by step for Chrome, Edge and Firefox: Clear the browser cache and cookies

1. Chrome: open More > Help > About Google Chrome, let it check for updates and select Relaunch.
2. Edge: open Settings and more > Help and feedback > About Microsoft Edge and restart when asked.
3. Firefox: open the menu, then Help > About Firefox, and select Restart to update Firefox when the download ends.
4. Open the video page again and press Play.

Fix 7. For site owners: measure and fix the manifest response

15 minutesNo riskYou run a website with JW Player and visitors report error 232001.

232001 is raised when the manifest request does not finish in time. The fix is on the server side: the .m3u8 address must answer quickly from your visitors' networks, also when caches are cold and traffic peaks.

1. Copy the exact .m3u8 address the player requests: from the player setup (file or sources) or from the DevTools Network panel as in Fix 4.
2. From a Windows PC, run the curl.exe command below a few times. Use curl.exe, because in Windows PowerShell 5.1 curl alone is another command.
3. Read the numbers: a slow first byte time means the origin or CDN is slow to build or serve the manifest. A slow connect time points to the network or the CDN edge.
4. Run the same command from another network or a cloud server to rule out your own office connection.
5. Check the CDN: is the manifest cached for VOD, and for live is it served from the edge with a short cache time that matches the segment length?
6. Check the origin under load: live packagers and signed-URL services often slow down first when many viewers start at the same time.
7. After a change, play the stream in the browsers your visitors use and watch the .m3u8 timing in DevTools.

Time a manifest request from Command Prompt or PowerShell (replace the address)

curl.exe -s -o NUL -w "dns %{time_namelookup}s  connect %{time_connect}s  first byte %{time_starttransfer}s  total %{time_total}s  http %{http_code}\n" "https://cdn.example.com/stream/master.m3u8"

Fix 8. For site owners: log the player's error code and source error

20 minutesLow riskYou run JW Player on your site and need data on who gets 232001 and why.

JW Player reports every error as an object with code, message, type and sourceError, the lower-level error the player caught. Logging it shows which streams, browsers and regions time out, instead of guessing from single reports.

1. Add an error listener and a setupError listener to the player in your page code, as in the example below.
2. Send the code, the message, the stream address, the browser and the time to your logging or analytics tool.
3. Group the reports by code: 232001 is a manifest timeout, 233001 a segment timeout, 2324xx an HTTP error on the manifest.
4. Compare the times of the 232001 reports with your CDN and origin logs and with traffic peaks.
5. Test a fix on a staging page before you change the live player.

Log JW Player errors (JavaScript, web player)

const player = jwplayer("player");
function report(e) {
  console.warn("JW Player", e.type, e.code, e.message, e.sourceError);
  // send e.code, e.message and the stream address to your own logging here
}
player.on("error", report);
player.on("setupError", report);

JW Player's errors reference describes the sourceError object as the lower-level error or event the player caught. For HLS errors it usually holds the hls.js details, which name the failing request. We could not confirm its exact fields for every player version, so log it as a whole.

Still getting error 232001? What to send the website

If the video fails on every network, in a private window and after a wait, the cause is not on your PC. Only the website can fix its stream. A good report gets an answer faster:

• The page address of the video and the exact text: This video file cannot be played. (Error Code: 232001).
• The date, the time and your time zone, and whether it was a live stream or a recorded video.
• Your browser and version (from the About page), and that it also failed on another network.
• The HAR file or chrome://net-export log from Fix 4, if the support team asks for one. Use the sanitized option.

If the code changes while you test, follow the new code. 232011 and 233011 point to cross-domain permission on the server, 230001 to a live stream that stalled, 233001 to a video piece that timed out, and 246xxx to DRM licences.

How to avoid error 232001 next time

A timeout cannot be fully prevented on the viewer's side, because the server's load is outside your control. What you can do is keep your own path short and clean, so that when the error appears you know quickly whether it is the site.

Frequently asked questions

What does error code 232001 mean?

It means the video player on the website asked for the stream's playlist file, the HLS manifest that ends in .m3u8, and the request timed out. The code comes from JW Player. Its errors reference gives the reason "An HLS manifest request timed out" and shows the viewer the text "This video file cannot be played". The video file itself was never reached, so the message does not mean the file is damaged. The cause is a slow or unreachable video server, or a slow path to it from your network.

Is error 232001 a Windows problem?

No. The code comes from a video player that runs inside a web page, so it is the same in Chrome, Edge and Firefox, on Windows 11, Windows 10 and other systems. Windows only matters when its network settings slow the request down, such as a proxy, a stale DNS cache or a weak Wi-Fi link. That is why this guide's Windows steps are limited to the proxy settings and the DNS cache, and why system file checks or driver updates do not help.

Why does it say "This video file cannot be played" when the file is fine?

JW Player uses a few short, general messages for many technical codes. "This video file cannot be played" is shown for 232001 and also for codes like 233001, 232600 and 224003, which have very different causes. The number in brackets is the useful part. For 232001 the player never got the stream's playlist, so it could not even start loading the file. The file can be perfectly fine on the server.

Can a VPN cause error code 232001?

Yes, it can. A VPN routes the request through its own server, which adds distance and a point where traffic can be slow or blocked. Some video services also slow down or refuse traffic from VPN addresses. Users on VPN forums report 232011 and 232001 together with VPN use. Test once with the VPN off or on mobile data, as in Fix 2. If the video then plays, pick a VPN server closer to you or pause the VPN for that site.

Will turning off hardware acceleration or updating the graphics driver fix 232001?

Usually not. Graphics acceleration and drivers matter when the browser decodes the picture, and that starts only after the manifest and the first video pieces have arrived. 232001 happens before that step. Decode problems show other JW Player codes, such as 224002. In Chrome 155 the switch is now called Use graphics acceleration when available under Settings > System, if you want to test it for a different problem.

I get error 232001 on YouTube. Is this the same error?

The code 232001 belongs to JW Player, and we found no YouTube documentation that uses it. YouTube has its own player and its own messages. If you see this exact text and code, check the page you are on: the video may be embedded from another site, or the page may be a copy of a YouTube video played through JW Player. The fixes in this guide still apply to that player.

What about error codes 232011, 230001, 233001, 232500 and 2324?

They are neighbours in the same JW Player family. Code 232011 means the manifest request lacked cross-domain permission, and 233011 the same for a video piece. Code 230001 means a live stream stalled for more than 30 seconds. Code 233001 means a video piece timed out. The 2324xx and 2325xx codes carry an HTTP status, so 232500 is a server error 500 and 232404 a missing file. "Error code 2324" as written is not a JW Player code; it is most likely the start of a 2324xx code.

What is código de error 232001, code erreur 232001 or kode kesalahan 232001?

It is the same error in another language. JW Player can translate its messages, so a Spanish, French or Indonesian site shows the text in that language, but the number stays 232001. The meaning does not change: the stream's playlist request timed out. All the fixes on this page apply, and the menu names in your browser will simply appear in your language.

How long does it take for the website to fix error 232001?

There is no fixed time, because it depends on what failed. A short overload during a live event often clears within minutes. A broken CDN setting or a failed origin server can take hours until the site's team notices and fixes it. That is why a clear report, with the page address, the time and the code, helps. Meanwhile nothing on your PC will make the stream load if the server does not answer.