-
-
Notifications
You must be signed in to change notification settings - Fork 11k
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
"connect: No error" error with remote ADB server #1939
Comments
This call fails: Line 36 in 25aff00
(and What happens if you forward a port manually: adb -s 10.1.0.12:5555 forward tcp:1234 tcp:1234 Then connect to it, for example via
Does it return immediately, or does it print an error message? |
I don't have netcat on Windows. I've tried a new setup as follows:
But .\scrcpy.exe -V debug
INFO: scrcpy 1.17 <https://github.com/Genymobile/scrcpy>
DEBUG: Using server (portable): C:\scrcpy-win64-v1.17\scrcpy-server
C:\scrcpy-win64-v1.17\scrcpy-server: 1 file pushed, 0 skipped. 46.8 MB/s (34930 bytes in 0.001s)
DEBUG: Screensaver enabled
[server] INFO: Device: samsung SM-T819 (Android 7.0)
[server] DEBUG: Controller stopped
[server] DEBUG: Using encoder: 'OMX.qcom.video.encoder.avc'
[server] DEBUG: Screen streaming stopped
[server] DEBUG: Device message sender stopped
DEBUG: Server terminated In the remote ADB server logs:
I have ad this comment already. But I was hoping being on a VPN - so basically the same network - would avoid using the SSH tunnel. |
Actually, the problem is a bit different if I use the SSH tunnel: ssh -CN -L5037:localhost:5037 -R27183:localhost:27183 my.remote.vpn.host.com .\scrcpy -V debug
.\scrcpy.exe -V debug
INFO: scrcpy 1.17 <https://github.com/Genymobile/scrcpy>
DEBUG: Using server (portable): C:\scrcpy-win64-v1.17\scrcpy-server
C:\scrcpy-win64-v1.17\scrcpy-server: 1 file pushed, 0 skipped. 55.3 MB/s (34930 bytes in 0.001s)
DEBUG: Screensaver enabled
[server] INFO: Device: samsung SM-T819 (Android 7.0)
[server] DEBUG: Using encoder: 'OMX.qcom.video.encoder.avc' The device screen does light up. Then the terminal hangs there. Then after a few seconds:
And the terminal hangs again. The ADB server logs show nothing at all. The ADB client works as expected: .\adb.exe devices -l
List of devices attached
386c9358 device usb:3-11 product:gts210veltexx model:SM_T819 device:gts210velte transport_id:3 Killing the SSH tunel does stop
which would indicate the SSH tunnel is indeed used. |
The following works:
But I'm still surprised I need to use an SSH tunnel when:
|
The following also works:
|
So my conclusion is that the Yet I don't see any actual ADB reverse/forward from the ADB client:
Wouldn't it be possible to specify another host? |
I guess the work being done here would match that requirement: |
After further investigation, hen running
Which means So it would seem it is an |
Actually, this line of code: Line 316 in c5c5fc1
suggests that So in the case of a device on the same VPN as the machine running |
Environment
I want to access the Android device via scrcpy via a Wireguard VPN.
Here is a the setup:
10.1.0.12
on the VPN10.1.0.6
adb nodaemon server
scrcpy -s 10.1.0.12:5555
works as expected$env:ADB_SERVER_SOCKET=tcp:10.1.0.6:5037
then runningscrcpy -s 10.1.0.12:5555
also works as expected10.1.0.2
$env:ADB_SERVER_SOCKET=tcp:10.1.0.6:5037
then running.\adb.exe -H 10.1.0.6 devices -l
returns the device listbut setting
$env:ADB_SERVER_SOCKET=tcp:10.1.0.6:5037
then runningscrcpy -s 10.1.0.12:5555
does not works as expected:the
connect: No error
line repeats endlessly.the
connect: No such file or directory
line repeats endlessly.Yet
.\adb.exe -a -H 10.1.0.6 -s 10.1.0.12:5555 shell
works as expected. So I suspect the remote adb server is working and available.Please advise.
The text was updated successfully, but these errors were encountered: