-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect: StatusCode: 500, Protocol "http:" not supported. Expected "https:" #458
Comments
Did you find a solution for this? I've been running into the same issue, and I suspect it's because of this change in the Sentry JavaScript SDK (which you appear to be using as well). It seems this SDK doesn't explicitly set a protocol, and therefore Sentry falls back to I've tried removing the Sentry wrapper from my API handler, and also passing along an explicit |
I'm running into the same issue after adding Sentry. Any updates here? I don't think downgrading Sentry is a good option |
Same here! And we don't really want to downgrade sentry because of this |
Still the same here too. At this point I've update Sentry and just disabled it on the server for now, but I also opened up a new issue for this. |
OS: Sangoma Linux 7 (Core) / CentOS 7
Environment: Node.js v14
SDK: "microsoft-cognitiveservices-speech-sdk": "1.19.0"
I am running into the following connection issue once I run my client code on my server. The code works perfectly on my workstation. I turned off my firewall on the server and everything is whitelisted, so I have the suspicion that it could be related to the operating system.
Any help or pointers into the right direction are greatly appreciated.
Error:
ErrorDetails=Unable to contact server. StatusCode: 500, undefined Reason: TypeError [ERR_INVALID_PROTOCOL]: Protocol "http:" not supported. Expected "https:"
Code:
The text was updated successfully, but these errors were encountered: