In most cases if you’re trying to connect to Whisperings PureStream and nothing at all happens… or if you receive a MEDIA SOURCE ERROR, it’s an indication that something is blocking your access to our file server. It could be a firewall blocking the access, enhanced network security or a browser plug-in (or old data) interferring with the connection. We have seen instances where users have adjusted their browser security settings to make them more stringent on what gets through… and that has caused the player to generate this message.
The FIRST easy thing to try: If you haven’t done so recently, restart your system. Doing that will free up system resources… then log in again and see if you get the same message.
The SECOND easy thing to try: if you have a different browser installed on your system, try launching that alternative browser and try tuning in from that one… see if you get the same error message. If it works, you’ll know whatever is causing the problem is specific to your original browser and is not a firewall or network security issue. To fix it (in the original browser), try clearing your browser cache. If you’re using the Chrome browser, for example, click on the Menu in the upper right (the three little dots), then More Tools, then “Clear Browsing Data…” Select “All Time” as the time range and then check the box for “Cached images and files” and then hit the Clear Browsing Data button. That process could take a few minutes if you haven’t ever done it before. If you’re using a browser other than Chrome, just google “How to clear the cache in (whatever your browser is)” and you’ll find instructions on how to do that. You just want to clear the temporary files and images for whichever browser you are using. Once you’ve cleared the cache, restart the system, relaunch the browser, return to our web site, relaunch the player and see if you still get the error.
If changing browsers makes no difference and the exact same thing happens, a firewall or tight network security is likely blocking access to our stream. This most commonly occurs in corporate or college network environments. In those cases, we recommend you contact your Network Admins to have them look at the problem.
FINALLY… here’s possible work-around to this issue: Before you log into the player, UNCHECK the “Customized” box (if the player logs you in automatically because you have the “Save Login” box checked, just log out, UNCHECK the “Customized” box, then Log back in.) That will put you in our basic player which may work around the issue as our basic stream is connecting to a live feed and not a file server. Do that, then tune in, and see if you can connect without receiving the error.