HeyPuter/puter · error · HttpError
upstream_bad_request
upstream_bad_request
Error message
Speechify TTS did not return audio data
What it means
Error "Speechify TTS did not return audio data" thrown in HeyPuter/puter.
Source
Thrown at src/backend/drivers/ai-tts/providers/speechify/SpeechifyTTSProvider.ts:228
: 400;
throw new HttpError(
exposedStatus,
errText ||
`Speechify TTS request failed (status ${response.status})`,
{
legacyCode,
fields: {
provider: 'speechify',
upstreamStatus: response.status,
},
},
);
}
// eslint-disable-next-line @typescript-eslint/no-explicit-any
const data: any = await response.json();
if (!data?.audio_data) {
throw new HttpError(
400,
'Speechify TTS did not return audio data',
{
legacyCode: 'upstream_bad_request',
fields: { provider: 'speechify' },
},
);
}
const buffer = Buffer.from(data.audio_data, 'base64');
const stream = Readable.from(buffer);
const contentType =
CONTENT_TYPES[data.audio_format ?? format] || 'audio/mpeg';
this.meteringService.incrementUsage(
actor,
usageType,
text.length,View on GitHub (pinned to 908ec23eda)
Solutions
- Retry the request; if it persists, verify the model and parameters are supported by Speechify.
- Check the Speechify response payload handling for changes in the API format.
When it happens
Trigger: Thrown at src/backend/drivers/ai-tts/providers/speechify/SpeechifyTTSProvider.ts:228 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of HeyPuter/puter@908ec23eda (2026-08-12).
Data as JSON: /api/errors/0bb4be0ee3d19dfe.
Report an issue: GitHub.