-
Notifications
You must be signed in to change notification settings - Fork 13
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
handle_https_peer failed error="TLS handshake failed: unexpected error: no server certificate chain resolved" #775
Comments
PS: With a Test CA which signs a cert it works. But the it's horrible slow compared to guacamole and even more compared to pure RDP. Test setup: |
Hi! Thank you for reporting this issue.
Did you generate the self signed using the installer? I’m currently unable to reproduce the issue using the installer. If you did not use the installer to generate the self-signed certificate, could you describe the procedure you used? (openssl commands, etc) Can you confirm me which version of the Devolutions Gateway you installed? (The current latest is 2024.1.3.0.) If you don’t mind sending us the self signed certificate and private key you used, this could help us investigating this issue. (This is assuming you don’t intend to use it anymore in the future of course.)
Maybe something is off for it to perform poorer than Guacamole, it’s not supposed to be the case. Unfortunately, it’s hard to say what happened just with this description. However, it will always be slower than the native client, we can’t achieve the same speed when running in the web browser how matter how hard we try. |
local_machine_my_2_Veeam Backup Server Certificate.zip It's a self signed cert created from Veeam "Standard" self signed cert works: ` Any idea regarding the speed? PS: Huge fan of the gateway |
Are you using the cert store for the gateway or do you have the cert in a file? |
Hi,
if I try to test the gatway standalone and use a self signed cert I'll only get:
handle_https_peer failed error="TLS handshake failed: unexpected error: no server certificate chain resolved"
greetings
Carsten
The text was updated successfully, but these errors were encountered: