microsoft / microsoft/dev-tunnels

Anonymous Websocket not working, timeout

Open
#523 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
508
Forks
52
Avg merge
20h 6m
Merged PRs (30d)
7

Description

I'm trying to use devtunnels for testing from an Android device to a test server being developed on a cloud based dev machine I can't directly connect to that is running a web socket / signalR based service.

From my mobile device or a desktop machine, i just get a timeout trying to use an anonymous connection or connection with a tunnel auth header.
On the desktop machine i can get it to work if I use devtunnel connect and create a local persistent port to connect to, but there are no devtunnel commandline tools I can run on my android device to do the same thing

Is there another way to do this?
I hoped I could use devtunnel connect with a machine on my local network, and connect to it but the ports that devtunnels creates seem to only be accessible from the local host even if I try to open the port on my firewall.

side note: ngrok works without doing anything special all I did was run ngrok tcp and was able to use it from mobile or desktop

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the timeout from Android and desktop with an anonymous connection or tunnel auth header, then compare it with the working devtunnel connect setup and the ngrok tcp behavior described here. The issue names no source files or tests, and completion is not defined beyond finding a supported way for the WebSocket or SignalR connection to work remotely.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.