Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

handle_https_peer failed error="TLS handshake failed: unexpected error: no server certificate chain resolved"

Open
#775 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust

Research direction

Start by reproducing the standalone gateway test with a self-signed certificate and inspect the TLS handshake path that reports "no server certificate chain resolved." Done means the self-signed certificate chain is resolved and the handshake no longer fails with this error.

Written by the indexing model from the issue text.

Description

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

Dominant language
Rust
Stars
161
Forks
30
Avg merge
2d 10m
Merged PRs (30d)
22

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Devolutions/devolutions-gateway

All issues in Devolutions/devolutions-gateway

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.