Calls platform; connection broken

[KC3AWP]

I noticed my calls node was deleted the other day due to inactivity. Odd because nothing was touched int the year or so it was running. Resubmitted for a new node and reset up everything how it was and no activity is being uploaded. I looked into the logs and found this multiple times:

2024-12-24 14:31:17,452 - DEBUG - Starting new HTTPS connection (2): api.broadcastify.com:443
2024-12-24 14:31:17,517 - DEBUG - Incremented Retry for (url='/call-upload'): Retry(total=1, connect=None, read=None, redirect=None, status=None)
2024-12-24 14:31:17,517 - WARNING - Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1091)'))': /call-upload
2024-12-24 14:31:17,517 - DEBUG - Starting new HTTPS connection (3): api.broadcastify.com:443
2024-12-24 14:31:17,587 - DEBUG - Incremented Retry for (url='/call-upload'): Retry(total=0, connect=None, read=None, redirect=None, status=None)
2024-12-24 14:31:17,587 - WARNING - Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1091)'))': /call-upload

Literally nothing has changed since ive started this node. I can ping api.broacastify.com with no issues. Ive deleted VoxCall and started fresh but still the same error. Any help? Ive quadruple checked my API key as well.

 

[KC3AWP]

Anyone?

 

[RaleighGuy]

Anyone?

These things take time to be noticed by people who know about them, you need to remember it is still the Christmas holiday and many members aren't active this week.

 

[KC3AWP]

These things take time to be noticed by people who know about them, you need to remember it is still the Christmas holiday and many members aren't active this week.

Yeah, I realized that i posted Christmas eve after the fact. I don't expect an official answer immediately. The "Anyone?" was for for the almost 100 viewers. Being as there's over 600 other call nodes up and running, its probably something on my end. Just wasn't sure if anyone already ran into this before and its something simple I'm overlooking.

 

[blantonl]

VoxCall is broken running on Windows.

Switch to GitHub - BobAProScan/VOX-Recorder: VOX Recorder is an application specifically designed for the Broadcastify Calls platform. Connect a receiver tuned to a specific conventional frequency.

 

[mikewren]

Root cause is likely related to this: *.broadcastify.com ssl cert expiration?

Looks like it's been resolved (until January 2026 )

 

[blantonl]

That issue has nothing to do with the VoxCall issue

 

[KC3AWP]

VoxCall is broken running on Windows.

Switch to GitHub - BobAProScan/VOX-Recorder: VOX Recorder is an application specifically designed for the Broadcastify Calls platform. Connect a receiver tuned to a specific conventional frequency.

Thank you sir! I will swap tonight!

 

[KC3AWP]

@blantonl same error with Vox Recorder. Need a new API key possibly?

 

[blantonl]

View attachment 175337

@blantonl same error with Vox Recorder. Need a new API key possibly?

No, I think these guys compiled against an older windows SSL version. Let me have a further look

 

[KC3AWP]

Just for info, the computer running the feed is a Windows 7 pro SP1. Im working to see if i can get SP2 on it.

 

[blantonl]

That's probably the problem. Windows 7 was released 16 years ago, and probably doesn't support TLS1.2 which we're required to support for a number of government agencies that use Broadcastify Calls for various reasons.

You might check out this document for more details on how to enable TLS 1.2 for Windows 7

https://vfa.aacc.nche.edu/Documents/Enable%20TLS%201.2%20On%20Windows%207.pdf