STT Invalid URL?

[awickham10]

What happened?

When using OpenAI for SST, I am getting an Invalid URL when trying to use it. TTS works fine.

I have tried with, and without the URL being specified in the config. Both produce the same result.

Steps to Reproduce

1. Set config yaml to this:

speech:
  speechTab:
    conversationMode: true
    advancedMode: true
    speechToText:
      engineSTT: "external"
      languageSTT: "English (US)"
      autoTranscribeAudio: true
      decibelValue: -45
      autoSendText: 0
    textToSpeech:
      engineTTS: "external"
      voice: "alloy"
      languageTTS: "en"
      automaticPlayback: true
      playbackRate: 1.0
      cacheTTS: true
  stt:
    openai:
      url: 'https://api.openai.com/v1/audio/transcriptions'
      apiKey: '${STT_API_KEY}'
      model: 'whisper-1'
  tts:
    openai:
      apiKey: '${TTS_API_KEY}'
      model: 'tts-1'
      voices: ['alloy', 'echo', 'fable', 'onyx', 'nova', 'shimmer']

3. Create a new chat
4. Hit the microphone button
5. Observe an in the UI saying an error occurred maybe the audio is too short.

What browsers are you seeing the problem on?

No response

Relevant log output

error: STT request failed for provider openai: Invalid URL
error: An error occurred while processing the audio: Invalid URL

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[solomonrosemite]

any update on this? i'm currently running into the same problem

[Spp595]

I have exactly the same problem, I tried both with and without the link. Local whisper doesn't work either
#8035

[jcbartle]

@awickham10 / @solomonrosemite / @Spp595 - in case anyone else runs into this issue, I thought I'd throw out what my problem was.

I was getting this exact same error when trying to run the project locally (though deployed to Azure worked just fine).

You can't trust this error message. It seems that axios just sends back the "Invalid URL" error no matter what error actually occurred. In my instance, I was actually getting a 401 unauthorized.

Setting up Fiddler, I was able to see that the api-key header value was getting sent over as ${STT_API_KEY} instead of my API key. The issue in this situation was that I had forgotten to set the STT_API_KEY environment variable in my local .env file.