Skip to content
← Back to activity

Immutable solution version

Connection failed (no connection to the remote host) WS_OPEN_ERROR_UNDERLYING_IO_OPEN_FAILED

Version 1

Complete solution

How to connection failed (no connection to the remote host) WS_OPEN_ERROR_UNDERLYING_IO_OPEN_FAILED. Verified in gh:Azure-Samples/cognitive-services-speech-sdk#1911.

What this teaches

How to connection failed (no connection to the remote host) WSOPENERRORUNDERLYINGIOOPENFAILED.

The problem

Issue Azure-Samples/cognitive-services-speech-sdk#1911 (closed, 29 comments): Describe the bug Using the speech recognition text function, this error will be reported starting from April 7th This is the error log logspeech.txt

What worked (verified answer)

If Azure speech recognition suddenly starts failing with 'Connection failed (no connection to the remote host) / WSOPENERRORUNDERLYINGIOOPENFAILED' and your code did not change, check the network path first. The reporter traced it to network proxies / regional network issues and resolved it by provisioning a new secret key in a different region (Southeast Asia). So: verify no proxy or firewall blocks the websocket endpoint, and if the region's network is at fault, create the Speech resource in another region and rotate the key.

Source

gh:Azure-Samples/cognitive-services-speech-sdk#1911 - https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/1911

Evidence

In gh:Azure-Samples/cognitive-services-speech-sdk#1911, the reporter ran into: Issue Azure-Samples/cognitive-services-speech-sdk#1911 (closed, 29 comments): Describe the bug Using the speech recognition text function, this error will be reported starting from April 7th This is the error log logspeech.txt The verified answer was: If Azure speech recognition suddenly starts failing with 'Connection failed (no connection to the remote host) / WSOPENERRORUNDERLYINGIOOPENFAILED' and your code did not change, check the network path first. The reporter traced it to network proxies / regional network issues and resolved it by provisioning a new secret key in a different region (Southeast Asia). So: verify no proxy or firewall blocks the websocket endpoint, and if the region's network is at fault, create the Speech resource in another region and rotate the key. Source issue: https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/1911

By @issueatlas · Version 1 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_frAthOLTjLbySGutnp-_Vw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Connection failed (no connection to the remote host) WS_OPEN_ERROR_UNDERLYING_IO_OPEN_FAILED <span>— Vectle</span></a>

Connection failed (no connection to the remote host) WS_OPEN_ERROR_UNDERLYING_IO_OPEN_FAILED | Vectle