starred/rustdesk-rustdesk

Fork 0

mirror of https://github.com/rustdesk/rustdesk.git synced 2026-03-02 19:26:56 -05:00

CERTIFICATE_VERIFY_FAILED #2338

New issue

Closed

opened 2026-02-21 00:19:32 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 00:19:32 -05:00

Owner

Originally created by @ferocknew on GitHub (Dec 6, 2023).

Bug Description

windows7 客户端
version ： 1.2.3

Unknown Error:HandshakeException:Handshake error in client (OS Error: CERTIFICATE_VERIFY_FAILED:unable to get local issuer certificate(././
third_party/boringssl/src/ssl/handshake.cc:393))

How to Reproduce

windows7sp1 客户端
version ： 1.2.3

Unknown Error:HandshakeException:Handshake error in client (OS Error: CERTIFICATE_VERIFY_FAILED:unable to get local issuer certificate(././
third_party/boringssl/src/ssl/handshake.cc:393))

Expected Behavior

windows 客户端
version ： 1.2.3

Unknown Error:HandshakeException:Handshake error in client (OS Error: CERTIFICATE_VERIFY_FAILED:unable to get local issuer certificate(././
third_party/boringssl/src/ssl/handshake.cc:393))

Operating system(s) on local side and remote side

windows 7sp1

RustDesk Version(s) on local side and remote side

1.2.3

Screenshots

Additional Context

No response

Originally created by @ferocknew on GitHub (Dec 6, 2023). ### Bug Description windows7 客户端 version ： 1.2.3 Unknown Error:HandshakeException:Handshake error in client (OS Error: CERTIFICATE_VERIFY_FAILED:unable to get local issuer certificate(././ third_party/boringssl/src/ssl/handshake.cc:393)) <img width="462" alt="image" src="https://github.com/rustdesk/rustdesk/assets/2178683/1a110b23-9e1b-4c81-8cc7-5bce68e13ec7"> ### How to Reproduce windows7sp1 客户端 version ： 1.2.3 Unknown Error:HandshakeException:Handshake error in client (OS Error: CERTIFICATE_VERIFY_FAILED:unable to get local issuer certificate(././ third_party/boringssl/src/ssl/handshake.cc:393)) <img width="462" alt="image" src="https://github.com/rustdesk/rustdesk/assets/2178683/1a110b23-9e1b-4c81-8cc7-5bce68e13ec7"> ### Expected Behavior windows 客户端 version ： 1.2.3 Unknown Error:HandshakeException:Handshake error in client (OS Error: CERTIFICATE_VERIFY_FAILED:unable to get local issuer certificate(././ third_party/boringssl/src/ssl/handshake.cc:393)) <img width="462" alt="image" src="https://github.com/rustdesk/rustdesk/assets/2178683/1a110b23-9e1b-4c81-8cc7-5bce68e13ec7"> ### Operating system(s) on local side and remote side windows 7sp1 ### RustDesk Version(s) on local side and remote side 1.2.3 ### Screenshots <img width="462" alt="image" src="https://github.com/rustdesk/rustdesk/assets/2178683/1a110b23-9e1b-4c81-8cc7-5bce68e13ec7"> ### Additional Context _No response_

deekerman

2026-02-21 00:19:32 -05:00

closed this issue
added the
bug
label

deekerman commented

2026-02-21 00:19:36 -05:00

Author

Owner

@rustdesk commented on GitHub (Dec 7, 2023):

#763

@rustdesk commented on GitHub (Dec 7, 2023): #763

deekerman commented

2026-02-21 00:19:37 -05:00

Author

Owner

@alex7875 commented on GitHub (Oct 14, 2024):

I have the similar error after updating to 1.3.1 client and 1.4.4 sever
My server client versions
1.4.4 server - Pro version
1.3.1 client
The steps I did when the problem occurs.
I was running 1.4.3 server (with 1.4.4 update available displayed in my webpage when logging in to the admin console of my selfhosted pro version of RustDesk. And installing (new install) 1.3.1 client version, I think the correct server information was input. And this error emerged. I have done so to update the server to 1.4.4 and update Rustdesk client to the latest 1.3.1 on other computers to reproduce the error. For those upgraded, it remains connecting the to server. However, as soon as I log off and log back in, the same error is produced.

I've also done refreshing the cert by removing the id_ed25519 and id_ed25519.pub (this resulting in change of the key string). Because after I ran the update script (to 1.4.4) and reload the service or reboot the server, my new login to the RustDesk admin portal still show current version as 1.4.3 and 1.4.4 is still available for upgrade. I've also ran upgrade script again or the convert to pro version script to initialized the SSL cert creation, this worked for a few time until now it is not able to complete the SSL certbot installation/initialization. It prompted 443/80 port error or Domain Name /DNS not being forwarded correctly. I really exhausted of options within in my knowledge. Anyone help? Thank you.

@alex7875 commented on GitHub (Oct 14, 2024): ![image](https://github.com/user-attachments/assets/cd85698b-16b6-476f-9cf7-eda85caf5e4d) I have the similar error after updating to 1.3.1 client and 1.4.4 sever My server client versions 1.4.4 server - Pro version 1.3.1 client The steps I did when the problem occurs. I was running 1.4.3 server (with 1.4.4 update available displayed in my webpage when logging in to the admin console of my selfhosted pro version of RustDesk. And installing (new install) 1.3.1 client version, I think the correct server information was input. And this error emerged. I have done so to update the server to 1.4.4 and update Rustdesk client to the latest 1.3.1 on other computers to reproduce the error. For those upgraded, it remains connecting the to server. However, as soon as I log off and log back in, the same error is produced. I've also done refreshing the cert by removing the id_ed25519 and id_ed25519.pub (this resulting in change of the key string). Because after I ran the update script (to 1.4.4) and reload the service or reboot the server, my new login to the RustDesk admin portal still show current version as 1.4.3 and 1.4.4 is still available for upgrade. I've also ran upgrade script again or the convert to pro version script to initialized the SSL cert creation, this worked for a few time until now it is not able to complete the SSL certbot installation/initialization. It prompted 443/80 port error or Domain Name /DNS not being forwarded correctly. I really exhausted of options within in my knowledge. Anyone help? Thank you. ![image](https://github.com/user-attachments/assets/afe440ed-8a97-4421-b423-0b945da97b38) ![image](https://github.com/user-attachments/assets/ad9f2999-1e65-4a7b-b155-de4b1938a833) ![image](https://github.com/user-attachments/assets/02ce03bf-b03b-48cc-8a86-fa69393bf27c)

deekerman commented

2026-02-21 00:19:37 -05:00

Author

Owner

@rustdesk commented on GitHub (Oct 14, 2024):

I would suggest you install with docker, and set up certbot manually,

https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/installscript/docker/#docker-compose

https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/#setup-https-for-web-console

please backup old data files. https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/#migrate-to-new-host-and-backup--restore

The script install looks simpler, but it is hard to figure problem once it fails.

@rustdesk commented on GitHub (Oct 14, 2024): I would suggest you install with docker, and set up certbot manually, https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/installscript/docker/#docker-compose https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/#setup-https-for-web-console please backup old data files. https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/#migrate-to-new-host-and-backup--restore The script install looks simpler, but it is hard to figure problem once it fails.