Flowplayer, a Flash-based online video streaming program, allows users to watch video directly on a Web page. In some browsers, however, the player may experience errors. One such problem is error 301, which happens when a plugin clashes with Flowplayer. Plugins are small application add-ons, and fixes may involve removing the offending plugin or reinstalling Flowplayer.
When an error happens inside the player itself, it's called an onError, according to Flowplayer. The onError known as a 301 error pops up with the message "Unable to load plugin." This usually results in the player stalling or crashing entirely. Refreshing the page may temporarily make Flowplayer work again, though the error may still appear in future.
In most cases, the internal 301 errors arise when you build plugins inside Flowplayer itself, which means compiling them into the Flowplayer SWF file. In theory, this simplifies the player for use on web pages. However, as the plugin options are wired into your player, any load problems may cause the whole thing to stall or shut down.
Removing plugins one by one from your Flowplayer configuration allows you to isolate which version is causing the problem. This requires some knowledge of Flowplayer's SWF files. Once you find the problem plugin, check the code against that listed in the Flowplayer documentation online. Any characters or commands entered incorrectly can result in error 301.