[Help wanted] "Failed to build TLS acceptor: received fatal alert: CertificateUnknown" #224
Replies: 4 comments 4 replies
-
|
It seems to be a certificate failure. Please check its format and validity. Also, if you use self-signed certificate, check if you use an appropriate binary built for native certificates. If you do mTLS, please check the format of your client CA certificate as well. |
Beta Was this translation helpful? Give feedback.
-
|
Also please check the configuration of Bitwarden android. Especially the domain name in the url since it is the most important to find the matched certificate and verify its validity with the common name (domain name) specified in the certificate. I am hosting vaultwarden behind rpxy too, which can be connected from Bitwarden android flawlessly. So I believe it is from some problems in your configuration. |
Beta Was this translation helpful? Give feedback.
-
Hmmm i'll see then because i know it can't be the domain, but maybe the cert? I used it with acme.sh but needed to convert it using this |
Beta Was this translation helpful? Give feedback.
-
|
Does both key & cert need to be converted to this? |
Beta Was this translation helpful? Give feedback.
-
|
I'll try tonight to tell acme.sh to convert it directly to Pkcs8 i think it just need this |
Beta Was this translation helpful? Give feedback.
-
|
I just moved this to QA in discussion |
Beta Was this translation helpful? Give feedback.
-
|
Solved it was a certificate issue all work well now ^^! |
Beta Was this translation helpful? Give feedback.
-
|
Good to hear that:-) |
Beta Was this translation helpful? Give feedback.
-
So i was trying to setup rust-rpxy all worked great until i was trying to connect bitwarden on android to the vaultwarden instance behind rust-rpxy, everything works fine but idk what to do here...
Maybe X-Real-IP header is missing? And if so how can i add it to rust-rpxy?
Beta Was this translation helpful? Give feedback.
All reactions