Open J-Roberts1 opened 9 months ago
Hi, @J-Roberts1, thanks for your feedback, from the error message, seems this error is related to the local dev tunnel. Please check your network, and disable proxy and try again. If it doesn't work, you can follow below steps to setup local dev tunnel manually:
devtunnel user login
.devtunnel host -p 3978 --protocol http --allow-anonymous
.env/.env.local
file, fill in the values for BOT_DOMAIN
and BOT_ENDPOINT
with your dev tunnel URL.
BOT_DOMAIN=sample-id-3978.devtunnels.ms
BOT_ENDPOINT=https://sample-id-3978.devtunnels.ms/
"Start local tunnel"
task in tasks.json
@SLdragon Thanks for your reply. I tried disabling t proxy and that didn't resolve the issue. I moved on to the steps you outlined but I encountered a new error in the CLI.
PS C:\Users\myuser> .\devtunnel host -p 3978 --protocol http --allow-anonymous
The SSL connection could not be established, see inner exception.
I think this error message indicates that there is an underlying issue with one of the SSL certificates. Does that seem like an accurate assumption to you?
I got a similar issue while working with Teams Toolkit. I figured that it could be because I was on different internet connection that the one I was connecting on before. Upon resuming to my usual internet connection the issue resolved. @J-Roberts1 could you try a different internet connection and see?
Here is the error I was getting: [2024-02-14T13:19:09.982Z] [Error] - code:Ext.DevTunnelOperationError, message: Unable to execute dev tunnel operation 'create'. self signed certificate in certificate chain Help link: https://aka.ms/teamsfx-local-tunnel-task
@J-Roberts1
I suspect that the user might have a configured proxy server, and the SSL certificate errors are likely being triggered by the proxy server’s SSL certificate. It's possible that the proxy server is injecting its own HTTPS certificate. Normally, in such a scenario, the proxy server's certificate would be added to the Windows certificate store as a trusted root certificate.
Unfortunately, the support for proxy in VS Code extension is still not fully developed. This is being monitored under issue https://github.com/microsoft/vscode/issues/12588, although there haven't been significant updates for some time.
There are a couple of potential workarounds to enable VS Code extensions to connect through a proxy that replaces HTTPS certificates:
NODE_EXTRA_CA_CERTS=<your-proxy-root-ca.crt>
--ignore-certificate-errors
command.
Describe the bug I am replicating the "Teams AI Library Quick Start Guide'. I am able to successfully follow all the steps up until step 17. Upon debugging I get the following error: "The preLaunch Task 'Start Teams Locally' terminated with exit code 1.". In terminal the error reads "Executing task: Start local tunnel Starting local tunnel service Dev tunnel tag: TeamsToolkitCreatedTag. Failed to start local tunnel service. Unable to execute dev tunnel operation 'create'. Hostname/IP does not match certificate's altnames: Host: global.rel.tunnels.api.visualstudio.com. is not in the cert's altnames: "
To Reproduce Steps to reproduce the behavior:
Expected behavior A browser tab should open a Teams web client requesting to add the bot to my tenant.
Screenshots
VS Code Extension Information (please complete the following information):