However, depending on the browser that you’re using, the exact steps of doing so will be different.

Keep in mind that there are several different problems that might occur due to corrupted temporary data left behind by the JW player and the Error code 23011 is one of them.įortunately, affected users have discovered that the problem can be fixed swiftly by accessing your browser settings and clearing the cache and the cookies. Method 1: Clearing your browser Cache and CookiesĪs it turns out, one of the most common causes that might end up causing this problem is some type of corruption located inside the cache or cookie folder of the browser that you’re actively using. You can eliminate the majority of inconsistencies by switching to a Chromium-based browser.

Browser incompatibility – Internet Explorer and Edge are two browsers that are still experiencing incompatibilities in relation to JW Player.

In this case, you can either try talking with the network administrator to remove the roadblock or you can connect to a different network.

Restricted network type – Corporate, school, and hotel networks might be specifically blocking Content Delivery Networks (CDN) such as the one that the platform behind JW Player uses.

In this case, you can resolve the conflict with the JW player by disabling the problematic extension or add-on.

Problematic extension – According to some affected users, this particular error code can also be caused by extensions and add-ons like Privacy Badger, Malwarebytes, or Avast Online Security.

If this scenario is applicable, you should be able to fix the problem by disabling the built-in proxy server or by installing the system-level proxy or VPN client.

Proxy or VPN-cause interruption – It’s a well-known fact that JW Player is not that good with managing end-user connections that are being funneled through a VPN or a Proxy server.

If this scenario is applicable, you should be able to fix the problem entirely by clearing both the cache and the cookie.

Corrupted cache or cookie data – Corrupted temporary data or a badly saved cookie can also be responsible for this particular error code.

About jw player 5.8.2011