ERROR: Server Connection Failed

[Akslaton]

• [x ] I have read the FAQ.
• [x ] I have searched in existing issues.

Environment

• OS: Windows 10
• scrcpy version: win64-v1.20
• installation method: Windows release
• device model: Pixel 4a (Running GrapheneOS)
• Android version: 12

Describe the bug

Over USB Cable, ADB and SCRCPY sees my phone, pushes the SCRCPY Server file, and then fails to connect to the server.

PS C:\platform-tools> ./scrcpy
INFO: scrcpy 1.20 <https://github.com/Genymobile/scrcpy>
C:\platform-tools\scrcpy-server: 1 file pushed, 0 skipped. 94.2 MB/s (37139 bytes in 0.000s)
[server] INFO: Device: Google Pixel 4a (Android 12)
ERROR: Server connection failed

Thank you

[rom1v]

Is another scrcpy instance running at the same time? (#2779)

Could you run scrcpy -Vdebug?

[Akslaton]

I don't think there are any other Scrcpy instances running.

PS C:\platform-tools> ./scrcpy -Vdebug
INFO: scrcpy 1.20 https://github.com/Genymobile/scrcpy
DEBUG: Using server (portable): C:\platform-tools\scrcpy-server
DEBUG: Screensaver enabled
C:\platform-tools\scrcpy-server: 1 file pu...skipped. 79.9 MB/s (37139 bytes in 0.000s)
[server] INFO: Device: Google Pixel 4a (Android 12)
[server] DEBUG: Controller stopped
[server] DEBUG: Using encoder: 'c2.qti.avc.encoder'
[server] DEBUG: Screen streaming stopped
[server] DEBUG: Device message sender stopped
DEBUG: Interrupting socket
DEBUG: Server disconnected
DEBUG: Server terminated
ERROR: Server connection failed

[rom1v]

Try with another encoder: https://github.com/Genymobile/scrcpy#encoder

[rom1v]

Also, could you test the version from #2783 and see if the console output is different?

[Akslaton]

Yesterday after work, I seem to have gotten SCRCPY working.
I tried closing a few programs that run in the system tray... I closed Discord, Syncthing and I disconnected my ExpressVPN.
Unfortunately I closed them all at once and then tried SCRCPY, so I have no idea which one was causing the server connection fail error.

I've tried turning those programs back on one at a time to see if the issue returned and it has not, which is king of frustrating from a troubleshooting perspective.

[rom1v]

If that happen again, switch to the version from #2783, I'm pretty sure that it is related if you're on Windows.