502 Bad Gateway on Calls Ingest

bashtech · Saturday at 7:07 AM

Is anyone seeing a larger number of upload errors when ingesting audio into the Calls platform?

I recently migrated my setup from SDRTrunk to Trunk Recorder so I'm not sure if this is a configuration issue on my part or an error that I just didn't notice with SDRTrunk. I don't seem to be missing any (many?) calls so the upload retry appears to be working and calls upload successfully eventually. Probably 1 in 5 calls fail to upload on the first attempt.

recorder-1 | [2025-07-26 12:02:46.180183] (error) [BerksNorth] 6416C TG: 3001 Freq: 769.293750 MHz Broadcastify Metadata Upload Error: <html>
recorder-1 | <head><title>502 Bad Gateway</title></head>
recorder-1 | <body>
recorder-1 | <center><h1>502 Bad Gateway</h1></center>
recorder-1 | </body>
recorder-1 | </html>
recorder-1 | [2025-07-26 12:02:46.180317] (error) [BerksNorth] 6416C TG: 3001 Freq: 769.293750 MHz Plugin Manager: call_end - Broadcastify failed.

rjdj2000 · 2025-07-28T11:05:12-0500

bashtech said:
Is anyone seeing a larger number of upload errors when ingesting audio into the Calls platform?

I recently migrated my setup from SDRTrunk to Trunk Recorder so I'm not sure if this is a configuration issue on my part or an error that I just didn't notice with SDRTrunk. I don't seem to be missing any (many?) calls so the upload retry appears to be working and calls upload successfully eventually. Probably 1 in 5 calls fail to upload on the first attempt.

I would think possibly configuration error but if you are using SDRTrunk to capture, I'd just send direct from there. No need for another program to be middle man. In the cmannd window that is open for SDRTrunk, you would see errors there or an abundance of calls piling up in the streaming viewer (if turned on) at the bottom of SDRTrunk

bashtech · 2025-07-28T15:26:20-0500

rjdj2000 said:
I would think possibly configuration error but if you are using SDRTrunk to capture, I'd just send direct from there. No need for another program to be middle man. In the cmannd window that is open for SDRTrunk, you would see errors there or an abundance of calls piling up in the streaming viewer (if turned on) at the bottom of SDRTrunk

I am not using SDRTrunk anymore. It entirely Trunk Recorder now. I liked SDRTrunk but the P25 system I am monitoring always had audio distortion that I could never resolve after over a year of on and off tweaking. So far, no signs of issues after moving to TR.

It seems like the errors cleared up today. I don’t see any failed uploads in the logs over the past 8 hours. Maybe just some server issues over the weekend?

502 Bad Gateway on Calls Ingest

bashtech

Newbie

rjdj2000

Gone Cuckoo

bashtech

Newbie

Similar threads