Berry webclient : error -1296 with self-signed certificate #22591
Unanswered
MG695
asked this question in
Support request
Replies: 2 comments 4 replies
-
Can you give access to the endpoint over the internet for testing? |
Beta Was this translation helpful? Give feedback.
3 replies
-
Could you please try with the latest version. I enabled ECDSA for some web sites, it might help. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
Hello. I try to access my PV Enphase Envoy gateway local API using webclient in Berry, with https get request, but get a -1296 error code.
When using curl my request works fine but only if I use -k parameter to accept self-signed certificate (which the Envoy uses).
My understanding is that, when using TLS/https, Tastomata checks certificate against the following two CA's : Let's Encrypt and Amazon root CA
But when a server uses a self-signed certificate, it is not using these CA's.
Therefore, as the -k option with curl is doing (Allow insecure server connections), there should be an option for webclient in Berry to not check CA/allow insecure server connection.
I tried to use fingerprint validation (SetOption132 1) first using real fingerprint of the self-signed certificate (I used tasmota-fingerprint program to get it), then fingerprint auto-learn and finally disable fingerprint but none of them worked. But, as the name of the option/command (mqttfingerprint) suggests, it might apply to MQTT only and is not used by Berry webclient.
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
Steps to reproduce the behavior:
https webclient request against server using self-signed certificate
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
Bypass authentication and have the request working
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
Beta Was this translation helpful? Give feedback.
All reactions