Blog Post

Microsoft Developer Community Blog
2 MIN READ

Announcing the public preview of the devtunnel CLI

carolinauribe's avatar
carolinauribe
Icon for Microsoft rankMicrosoft
May 23, 2023

Dev tunnels are a powerful tool to securely open your localhost to the internet and control who has access, so you can easily test and debug your web apps and webhooks from virtually anywhere. With dev tunnels, you can also share your local work in-progress with colleagues or clients to get feedback asynchronously without the hassle of deploying. Previously, the only way you could use dev tunnels was through Visual Studio 2022.

 

Today, we are thrilled to announce the public preview of the devtunnel CLI! To create, host, and connect to your first dev tunnel in seconds, please follow the documentation on Microsoft Learn.

 

 

Use cases

Here are some of the scenarios that dev tunnels enable with the devtunnel CLI or dev tunnels in Visual Studio 2022.

Benefits

  • Secure by default – Each dev tunnel you create is only accessible to you using your Microsoft, Microsoft Azure Active Directory or GitHub account.
  • Persistent URLs - Retain the same tunnel URL for extended periods of time.
  • Support for multiple simultaneous ports - Host multiple ports on a single tunnel at the same time.
  • Global service availability - The dev tunnels service is available globally. Tunnels are automatically created in the closest available region to ensure optimal performance.
  • Tunnel inspection - Inspect tunnel traffic in a familiar interface, browser DevTools, to monitor and manage your web apps or webhooks.

To improve the devtunnel CLI, we encourage you to connect with us through GitHub issues to request a feature or submit a bug. We look forward to hearing your feedback!

 

 

Updated May 26, 2023
Version 2.0
  • JGrote's avatar
    JGrote
    Iron Contributor

    It doesn't support http/2, so grpc won't work unless you use a "raw" TCP socket tunnel

  • mbedsys's avatar
    mbedsys
    Copper Contributor

    Hi,

     

    gRPC works normally when I run it on the intranet.

    DevTunnel Cli also works normally when I connect the Client to the Server, with the following message:
    Connected to tunnel: f98126e4-0a7a-d7d7-a41d-b9b143a4ece0
    SSH: Forwarding from 127.0.0.1:10444 to host port 10443.
    SSH: Forwarding from [::1]:10444 to host port 10444.
    SSH: PortForwardingService listening on 127.0.0.1:10444.
    SSH: PortForwardingService also listening on ::1:10444.

     

    Problem:

    I use DevTunnel Cli so that gRPC on the Server side can be accessed by the Client from the Internet.

    When I run gRPC on the Server side, everything runs normally without any errors.

    Then I access gRPC from the Client Side (via the internet), I failed to get data from gRPC via the internet.
    Even though DevTunnel Cli status is connected.


    Then I tried to replace gRPC with CoreWCF, it also didn't work.

    I protect both gRPC and CoreWCF with certificates and there are no problems with the certificates.


    Is it true that DevTunnel Cli does not support gRPC and CoreWCF?

     

    Thanks

    Mbeds