Topic: NOAA WEATHER RADIO

[gwwilk]

I abandoned Chrome for the Chrome-based Brave browser last Fall.  Brave allows a granular approach to unblocking sites that is essential for accessing/displaying some or portions of some web sites.  I'm not interested in their 'Rewards', but the browser has served me very well.

[saratogaWX]

I can confirm there is an issue with Chrome. I loaded my WxRadio page on Chrome on my desktop just now and it worked fine. That was with version 79.0.3945.130. I then updated Chrome to 80.0.3987.116 and now I get 'Failed to Load Audio Stream'.

Steve

I think the latest Chrome 80.0.3987.116 now militantly blocks http content (radio streams) from an https page.  Firefox allows it.
Because wxradio.dyndns.org (the Icecast server running most of the streams) and most privately-offered streams are http only, this is going to be a problem with Chrome unless someone finds a way around it .. switching to a browser that works (or switching noaaweatherradio.org to not redirect to https) is another possible solution short-term.

[n2jtx]

Because wxradio.dyndns.org (the Icecast server running most of the streams) and most privately-offered streams are http only, this is going to be a problem with Chrome unless someone finds a way around it .. switching to a browser that works (or switching noaaweatherradio.org to not redirect to https) is another possible solution short-term.

An option for SSL is to go with the free Let's Encrypt service (https://letsencrypt.org/). There are instructions on setting it up at https://mediarealm.com.au/articles/icecast-https-ssl-setup-lets-encrypt/. I use it myself but not with Icecast. The only downside is the certificate needs to be renewed every 90 days. There is an automated routine (certbot) to do it but it requires some configuration work.

[92merc]

Unfortunately, it's a bit more complicated than just getting a cert when it comes to Icecast.

If the Icecast server wasn't built with OpenSSL pre-compiled into the installer, Crushed Box Software would need to re-install it.  So that means either downtime.  Or they'd have to bring up a new server with that already done.  Plus they'd have the work of re-doing the cert every three months.  So more work than they are doing now.

There are other possibilities like using a reverse proxy to serve up the stream.  Not sure if they are interested in doing that.  At least with that option, you can then use Certbot to automatically re-new the cert.  Certbox can work with Icecast from what I've read.  But again, not an easy task.

[Cutty Sark Sailor]

Enough is enough.... cut the hassle with NWR SSL Streams
Knowing Chrome, Goiogle, et.al. plan even more drastic 'restrictions' on mixed content, A couple of moths ago, Took this action.  Do as you will.

NO Hassle, no other charges, 32KB, stats, etc, and most importantly, SSL https://getstreamhosting.com/ssl-radio

Mike

   

[saratogaWX]

Ok.. I submitted change requests to swap my direct streams to the two SSL endpoints at getstreamhosting.  $10 is a small price to pay.  Thanks for the nudge, Cutty!

[ed2kayak]

NO Hassle, no other charges, 32KB, stats, etc, and most importantly, SSL https://getstreamhosting.com/ssl-radio

Mike

Cutty, it says works with encoder - Icecast2 or Shoutcast v1.

I use BroadWave, will it work with that?

Thanks

Ed

[Cutty Sark Sailor]

NO Hassle, no other charges, 32KB, stats, etc, and most importantly, SSL https://getstreamhosting.com/ssl-radio

Mike

Cutty, it says works with encoder - Icecast2 or Shoutcast v1.

I use BroadWave, will it work with that?

Thanks

Ed

No... Broadwave is't just an encoder, it is the server.
You'll want to use the IceCaset option on the GetStream,, it's the freebie. 
An encoder simply codes the audio to mp3, and connects it to the server.
You cana leave broadwave as it is, as an alternate, and:download BUTT, for example, and also install it, take the same audio in souyrcee Broadwave uses, and set up the stream.. You can run both at same time. One advantage to sending mp3 to the icecast:  It does all the heavy lifting.  Broadwave uses more network and computer resources if multiple folks connect to the stream
Folks hitting the Icecast keep the load there, not on your network.

See:  https://noaaweatherradio.org/howto.html for encodes we have on site download,... there are others available...most want some money, however...heh
there are some 'quickly' produced setup hints, e.g. BUTT also e.g. https://noaaweatherradio.org/Encoders/BUTT/QuickSetButt-wxradio.dyndns.org.pdf

[mikev]

Mike... I've had an HTTPS version of my stream (KHB36 alternate) available and in the list for a while. If you want to remove the HTTP version, that's fine. I'll submit the form to get my QRA report going on the HTTPS stream.

[Bunty]

Please pardon my confusion, but  does switching to getstreamhosting mean I can't continue to be in the NOAA Weather Radio Network?

[92merc]

No, you can be a part of the NOAAWeatherRadio.org site.  You'll just need to submit your new link so they can update their records.

[lddaly]

Enough is enough.... cut the hassle with NWR SSL Streams
Knowing Chrome, Goiogle, et.al. plan even more drastic 'restrictions' on mixed content, A couple of moths ago, Took this action.  Do as you will.

NO Hassle, no other charges, 32KB, stats, etc, and most importantly, SSL https://getstreamhosting.com/ssl-radio

Mike

Thanks, Mike and Ken. I moved over the KEC56 stream last week and everything has been working fine. This was the last remaining non-secure element on my website. The additional stream usage metrics from this service are also nice to have.

[MchWxEnthusiast]

what's with the lock icons on some streams?

[saratogaWX]

Those indicate a HTTPS (SSL) radio stream.  With recent updates to browsers, if you access a site using https:, then all the media (images, streams) must also be https: to be used. 

The padlock (like the padlock shown on your browser) simply shows those streams that can be used with both http and https access and are the only ones that can be used when the page is loaded https.

[Otis]

Just an FYI about this stream.


PUBLIC INFORMATION STATEMENT
NATIONAL WEATHER SERVICE GAYLORD MI
412 AM EDT TUE JUN 30 2020

...NOAA WEATHER RADIO OUTAGE...

DUE TO SCHEDULED MAINTENANCE, NOAA WEATHER RADIO STATION WNG-572,
BROADCASTING FROM NEAR GOOD HART, MICHIGAN, ON A FREQUENCY OF
162.475 MHZ, WILL BE OFF THE AIR INTERMITTENTLY TODAY, JUNE 30TH,
FROM 8 AM TO 8 PM. WE APOLOGIZE FOR THE INCONVENIENCE.

$$

[MchWxEnthusiast]

kinda irrelevant to what you guys are talking about but it would be nice to have streams from the upper peninsula of Michigan and also northern Minnesota.

[Otis]

kinda irrelevant to what you guys are talking about but it would be nice to have streams from the upper peninsula of Michigan and also northern Minnesota.

Just requires somebody to stream them, yes would be nice to have them.

[gwwilk]

The Lincoln, NE WXM20 transmitter has malfunctioned.  The stream from both of my feeds is almost all noise at this point, so it provides no useful information.  I believe that this is the same problem that afflicted the Omaha transmitter recently.  Who should I contact regarding this?

[tmabell]

I'd try the WCM at Omaha.  Email or PM for his contact.

[gwwilk]

I would say that they have their hands full from the looks of this map!  No need to report what they're already aware of...

Perforce, here's the plan:

[NWROrg Team]

Gerry, contact the Omaha/Valley NE WFO (OAX) directly,...    nws.omaha@noaa.gov they're aware of the issue, but may be able to give you an update....

Actually, the quickest way, sometimes, is to contact the 'owning' WFO directly... they may not even be aware of an issue if you've caught it quickly, and many issues can be corrected fairly rapidly.  You can ALWAYS report an outage or issue at
https://www.weather.gov/NWR/nwr_outage_report but it usually takes MUCH longer than checking with local first.

[gwwilk]

Gerry, contact the Omaha/Valley NE WFO (OAX) directly,...    nws.omaha@noaa.gov they're aware of the issue, but may be able to give you an update....

Actually, the quickest way, sometimes, is to contact the 'owning' WFO directly... they may not even be aware of an issue if you've caught it quickly, and many issues can be corrected fairly rapidly.  You can ALWAYS report an outage or issue at
https://www.weather.gov/NWR/nwr_outage_report but it usually takes MUCH longer than checking with local first.

I've been wrestling with Win10 Updates on over 10 affected computers, but I can now see the light at the end of that tunnel.

I appreciate the suggestions, and I have sent a query re estimated WXM20 downtime to the OAX NWS office.  Thanks!

[gwwilk]

This is the reply I received from NWS Omaha:

Hi Jerry.

The issue is due to a Verizon line at the transmitter. They inform us they continue to troubleshoot the Verizon issues. We suggest having multiple ways to receive weather information like weather apps on a smart phone or via internet/TV sources.

Our apologies.

NWS Omaha

I hated being just another burr under their saddle, but the information is useful.

[NWROrg Team]

Watch This Topic...

For important information, and updated service for HTTPS (SSL/TLS) streaming server solution.
Coming Very Soon!

[NWROrg Team]

HEAD'S UP:
https://www.wxforum.net/index.php?topic=40781.msg418428#msg418428

Save A Life!