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
waiting for image, then connection reset by peer errors looping indefinitely #1146
Comments
Downloaded current Pop!_Os (22.04 LTS) from website, installed in VM. Downloaded rustdesk-1.1.9.deb, attempt to install (failed with pulseaudio requirement). re-packaged it according to #559 then re-tried the install, which worked. Started it up, entered my id server and key, and successfully connected to the pop!_os client computer. After that, I successfully used it to connect to a windows client. |
Thanks |
RustDesk installed successfully for me in PopOS and I can connect to the client; but it fails to fully establish. Instead, it loops between the 2 "waiting for image", then "connection reset by peer" errors indefinitely. |
Could you please run the following commands in a terminal window and post the result: |
Describe the bug you encountered:
I have this same issue detailed in #499; but am not using the docker container. Client connects, then hangs on "waiting for image" for a second, and then i get the "reset by peer" error. This just keeps looping indefinitely until i stop it. All other clients are working fine except this one. This is a linux client; but other linux clients work fine. This client is running PopOS. So, it's possible the GUI is having an issue with RustDesk.
What did you expect to happen instead?
The connection to establish properly and show the desktop
How did you install
RustDesk
?installed github release 1.1.9 from the rustdesk website's download button
RustDesk version and environment
installed github release 1.1.9 from the rustdesk website's download button to a PopOS linux client. Using a self hosted server (not the docker container). All other windows and linux clients are working properly.
The text was updated successfully, but these errors were encountered: