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 d...
Updated May 26, 2023
Version 2.0
developer
get started
tips and tricks
mbedsys's avatar
mbedsys
Copper Contributor
Sep 22, 2024

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