-
Notifications
You must be signed in to change notification settings - Fork 187
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 execute dev tunnel operation 'create'. Tunnel service returned status code: 403 Forbidden #11275
Comments
@ashlytom
|
@XiaofuHuang |
No @XiaofuHuang. |
@ashlytom We've used the dev tunnel instead of ngrok in Teams Toolkit V5. Given that the dev tunnel CLI isn't functioning in your environment, it's likely the root cause lies within the dev tunnel. |
@XiaofuHuang Thank you. It was an issue caused due to the firewall on the system i was working with. Once the API within devtunnel host was whitelisted, it started working again. |
Describe the bug
I am unable to run the debug operation in Teams toolkit. I have create a testing account for running debug code. The account has custom app upload capability. But im getting this error constantly. It has only started recently, I had tried the same a month back and it was working fine.
Summary:
(×) Error: Unable to execute dev tunnel operation 'create'. Tunnel service returned status code: 403 Forbidden
Visit https://aka.ms/teamsfx-local-tunnel-task to learn more about 'Start local tunnel' task.
[2024-04-03T06:38:17.984Z] [Error] - code:Ext.DevTunnelOperationError, message: Unable to execute dev tunnel operation 'create'. Tunnel service returned status code: 403 Forbidden
Help link: https://aka.ms/teamsfx-local-tunnel-task
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Tunnel should be automatically relates and Dev Teams should open up browser
Screenshots
VS Code Extension Information (please complete the following information):
CLI Information (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: