Anybody had a problem accessing certain station streams on Tunein? I can get my station using Firefox but Chrome no longer works . But some other stations do work on Tunein with Chrome.
One possibility, since many streams on TuneIn are just Shoutcast streams under the hood:
Years back, several browsers, one at a time, made the same security change to their respective code bases, preventing them from making non-SSL connections to HTTP/0.9 servers on any TCP ports except 80. As it so happens, Shoutcast version 1 servers, a version many stations still stream with despite its incredible age, don't support SSL and also look like HTTP 0.9 to web clients (due to their actually using a protocol called ICY for streaming which
looks like HTTP/0.9 to web clients). Consequently, many users find that some but not all of their browsers fail to connect to certain servers and are unable to readily see why.
Here's WRMI's "Legends" oldies stream, which is an example of a still-operational Shoutcast V1 server that's not on port 80. It should fail to work in modern versions of the aforementioned browsers, but should still work in old versions, or in Winamp/VLC/WMP/etc.
http://64.235.54.14:8020/;
Anyway, I believe this security change first appeared in Chromium, meaning that all the browsers internally built from Chromium's codebase were initially affected (Google Chrome, Microsoft Edge, Opera, Brave, Amazon Silk, Vivaldi, SRWare Iron, etc). But later, Safari implemented the same change, bringing the problem to most Apple users. Firefox, if memory serves, was one of the last hold-outs. But a couple years ago, I saw evidence that at least some of its builds were implementing the change as well. (I haven't looked any further into the matter since.)
The solution, for stations, is updating their Shoutcast V1 servers to Shoutcast V2, which doesn't look like HTTP/0.9 to web clients (and which, as of the most recent Shoutcast V2 versions, also supports SSL natively). If stations can't upgrade to V2 because other softwares they're interfacing to Shoutcast itself require V1, they can alternatively pay for or install a Shoutcast SSL proxy so their Shoutcast V1 installations can be reached via SSL anyway. See below.
Try getting the direct stream URLs for the stations you're having trouble with by monitoring your browser's web console's [Network] traffic inspection tab while visiting their TuneIn pages. If those links don't work in those browsers but do work in VLC or older browser versions, it's most likely a Shoutcast V1 issue.
More information:
https://radio.co/blog/shoutcast-v1-not-working-heres-fix
https://codecanyon.net/item/kast-ex...io-player-for-jquery-material-design/14396614
https://bugs.chromium.org/p/chromium/issues/detail?id=669800
https://www.internet-radio.com/comm...55-breaks-shoutcast-v1-x-html5-players.27560/
https://stackoverflow.com/questions/2682932/shoutcast-over-ssl
Examples of Shoutcast SSL proxying (possible from paid services or DIY style):
https://shoutcastsolutions.com/store/ssl-proxy
https://www.svnlabs.com/blogs/radio-icecast-shoutcast-php-proxy-to-re-stream-radio-stream-on-https/
