Sadly we cannot log into our account because it uses https which means people also cannot listen to feeds because they use https also.
Side note....what are these call sites you speak of?
My system uploads to both Broadcastify & OpenMHZ.com and it is still working.is there a good alternative to broadcastify when it goes down
[2022-02-25 23:38:21.409139] (error) [albp16] TG: 26128 Freq: 8.574375e+08 Broadcastify Metadata Upload Error:
[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
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.A calendar notification is good for these kind of things.