Skip to content
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

Opening handshake failed. QUIC_TLS_CERTIFICATE_UNKNOWN #3

Closed
wanjohiryan opened this issue Dec 23, 2022 · 1 comment
Closed

Opening handshake failed. QUIC_TLS_CERTIFICATE_UNKNOWN #3

wanjohiryan opened this issue Dec 23, 2022 · 1 comment

Comments

@wanjohiryan
Copy link
Contributor

Error:

I keep getting 'Opening handshake failed' in brave v1.46.144 (running on chromium v108.0.5359.128) and chrome canary v111.0.5494.0

I have tried searching all over the internet but nothing seems to solve this.

This includes:

  1. Generating new certificates,
  2. allowing insecureOrigins in tls.Config
  3. Using a different machine

Probable cause

Chrome /Chromium seems to have dropped support for the flag --ignore-certificate-errors-spki-list

Expected behaviour

Run warp in the browser without TLS_CERTIFICATE error

Screenshot

2022-12-23 21_22_58-WARP - Brave

@wanjohiryan
Copy link
Contributor Author

After a lot of tinkering, a found a working solution:

chrome --origin-to-force-quic-on=localhost:4443 localhost:4444

Works like a charm.

Also, a simpler way to create self signed certificates would be with mkcert

mkcert -install
mkcert localhost

The fingerprint is not required after they dropped support for the flag --ignore-certificate-errors-spki-list

Closing this issue.

kixelated pushed a commit that referenced this issue Jul 21, 2024
Commit to fix build warnings ( cargo clippy ,cargo fmt run and obi1kenobi/cargo-semver-checks ) in PR : #2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant