Sadly we cannot log into our account because it uses https which means people also cannot listen to feeds because they use https also.
TLS Cert expired/Broadcastify Issues
- Thread starter Saint
- Start date
- Status
Real world? Or joke?
My system uploads to both Broadcastify & OpenMHZ.com and it is still working.
I'm a feed provider using Broadcastify. My feed and as far as I can tell all other local feeds here in the Texas area are not working. Seems to be a Broadcastify issue. Looks like we'll have to wait it out until they fix it.
My feed just went offline as well. I opened a ticket #38820 with broadcastify.
jpryor
Member
Broadcastify calls API uploads also impacted.
I got the notification my feed went offline around 1600 PST today. I checked my radio and it was functioning properly but I was busy with family and not at home. I tried to login to Broadcastify and got the SSL error. I hope this is rectified soon.
I got my node back up and running at least. I use SDRTRUNK. I switched to http instead of https
Even with HTTP I am seeing intermittent connection errors like this:
Code:
[2022-02-25 23:38:21.409139] (error) [albp16] TG: 26128 Freq: 8.574375e+08 Broadcastify Metadata Upload Error:
Code:
[2022-02-25 23:38:37.665495] (error) [albp16] TG: 35280 Freq: 8.577375e+08 Broadcastify Metadata Upload Error: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD><BODY>
<H1>502 ERROR</H1>
<H2>The request could not be satisfied.</H2>
<HR noshade size="1px">
CloudFront wasn't able to connect to the origin.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
<BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
<BR clear="all">
<HR noshade size="1px">
<PRE>
Generated by cloudfront (CloudFront)
Request ID: l2HISyt2uyncJHpAtbjmNuK-090S8DaHkpPX7u_pTkkw4IAMh-4qvQ==
</PRE>
<ADDRESS>
</ADDRESS>
</BODY></HTML>
[2022-02-25 23:38:37.665597] (error) Plugin Manager: call_end - broadcastify_uploader failed
There is a known workaround, change the date on your computer or your phone to 01/23/2022. This is a known work around until, broadcastify fixes the certificate issues.
Already being discussed here...
forums.radioreference.com
forums.radioreference.com
calls platform offline
Looks like the wildcard SSL cert for broadcastify expired today.... my trunk-recorder instances cannot upload... anyone know if it's being worked on or if there is an alternative upload path? https://api.broadcastify.com/call-upload @blantonl UPDATE... I switched my config to use HTTP and...
TLS Cert expired/Broadcastify Issues
When I click on Live Audio I get this popup and can not listen
I guess I'll wait until Broadcastify fixes it. Can listen to the G-4
Yep. Just came here to see if it was a system issue. I can’t get the app to work on my phone but my feed still plays on 5-0 Radio.
There is also something wrong with the front (landing) page of Broadcastify. It only loads halfway & has broken links. I hope they didn't get hacked.
rclegion
Member
I tested an android app "Scanner Radio" and my feeds are working from the app . But getting the 502 error on website like everyone else .
Meaning that when a new cert is added, set a calendar notification for a few days before its expiration date as a warning that it needs to be renewed or replaced.
- Status
Similar threads
