Connection failed (no connection to the remote host). Internal error: 1. Error details: Failed with error: WS_OPEN_ERROR_UNDERLYING_IO_OPEN_FAILED wss://francecentral.stt.speech.microsoft.com/stt/speech/universal/v2?language=en-US

[khursheed33]

I am using Docker container for transcription.

Below is the log from the container:

[INFO] SpeechConfig created successfully
[INFO] SpeechConfig set: Language=en-US, Diarization enabled
[INFO] PushStream created successfully
[INFO] AudioConfig created successfully
[INFO] Successfully read WAV file: /app/demo/harvard.wav, size=3249880 bytes
[INFO] Starting transcription
[INFO] Setting up transcriber
[INFO] Transcriber setup completed
[INFO] Transcription started successfully
[INFO] TranscribeFromRawData: dataSize=3249880
[INFO] Resampling audio: inputSize=3249880, inputSampleRate=32000, outputSampleRate=16000
cp: target '/root/.config/pulse/' is not a directory
W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
mkdir: cannot create directory '/root/.config': File exists
[INFO] Resampling completed: outputFrames=812470
[INFO] Resampled audio size=1624940
[INFO] Pushing audio data: size=1624940
[INFO] Audio data pushed successfully
[INFO] Running main loop for 30 seconds to process transcription...
[ERROR] CANCELED: Reason=1, ErrorCode=5, Details=Connection failed (no connection to the remote host). Internal error: 1. Error details: Failed with error: WS_OPEN_ERROR_UNDERLYING_IO_OPEN_FAILED
wss://francecentral.stt.speech.microsoft.com/stt/speech/universal/v2?language=en-US
X-ConnectionId: 30beceb456274245a10f3fc561125357 SessionId: 30beceb456274245a10f3fc561125357
[INFO] SESSION STOPPED

Related Issue: #1911

Please help ASAP.

[BrianMouncer]

@khursheed33

What programming language are you using?
Can you reproduce the issue with one of our speech sdk samples?
How are you creating your SpeechConfig object?

Is this a recent problem?

Thanks.

[Daniel19821128]

I’ve encountered the same issue. I’m using the code from the Speech SDK samples (cognitive-services-speech-sdk-master/quickstart/java/android/from-microphone). Both the subscription key and region are correct, as they work fine when tested with the CLI on Windows. However, the code fails on the Android platform.

[Kanchan-Microsoft]

Hi @BrianMouncer, I've encountered the same issue.

• Region: UK South
• Tested WebSocket connection: Successful
• Actual Error:
  Connection failed (no connection to the remote host). Internal error: 1.
  Error details: Failed with error: WS_OPEN_ERROR_UNDERLYING_IO_OPEN_FAILED
  wss://uksouth.stt.speech.microsoft.com/stt/speech/universal/v2?language=en-US

Despite the WebSocket connection being successful in network tests, the API still fails with the above error.
Could you please provide an update on this or let us know if there’s a workaround?

Thanks in advance!

[Kanchan-Microsoft]

Hi @BrianMouncer, just following up on this.
I’m still encountering the same issue in the UK South region.
Any updates or workarounds would be really helpful.

Thanks again!

[Kanchan-Microsoft]

Hi @BrianMouncer,
This is a quick follow-up — I'm still encountering this issue in the UK South region.
Any update or acknowledgment would really help me plan accordingly.

Thanks!

[Kanchan-Microsoft]

Hi @BrianMouncer,
Just checking in again on the issue. We're still experiencing the same problem despite successful WebSocket tests.
We’d really appreciate any updates, workarounds, or even confirmation that the issue is being investigated.

Thanks!

[Kanchan-Microsoft]

Hi @BrianMouncer,
Just checking in on this issue. We're still encountering the same problem. Is there any update, known workaround, or confirmation that the issue is being looked into?
We’d really appreciate any insights or direction you could provide.

Thanks in advance!

[Kanchan-Microsoft]

Hi @BrianMouncer,
Just following up again to check if there are any updates regarding this issue. We’re still facing the same problem. Any confirmation, or workaround would be greatly appreciated.

Thanks again for your time and support!

[Kanchan-Microsoft]

Hi @BrianMouncer,
Just checking in again on the issue. We're still experiencing the same problem.
Any updates or workarounds would be really helpful.

Thanks!

[Kanchan-Microsoft]

Hi @BrianMouncer ,
Just following up again — I'm still encountering this issue.
Any update or acknowledgment would really help me.

Thanks!

[Yamini-Microsoft]

Hi @BrianMouncer
Just following up on this issue we encountered.
Could you please advise:

1. If this is a known issue on the Microsoft side (e.g., service or regional outage)?
2. If any network or firewall configurations need to be reviewed on our end?
3. Any workaround or alternate region we should try meanwhile?

Looking forward to your inputs so we can proceed further.

[Yamini-Microsoft]

Hi @BrianMouncer
Just checking in again on this issue.
Could you please let us know:

• Whether this might be a known issue on Microsoft's end (e.g., a service or regional outage)?
• If there are any network or firewall settings we should revisit on our side?
• Whether there's a suggested workaround or alternate region we could try in the meantime?

Appreciate your input so we can move ahead accordingly.

[Kanchan-Microsoft]

Hi @BrianMouncer,
Just following up again. We're still experiencing the same problem.
We’d really appreciate any updates, workarounds, or even confirmation that the issue is being investigated.

Thank you!