When I try to connect to a MySQL Database from my Raspberry Pi, I get this error:
system error: 1 [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:1056)
Other Platforms work fine. Is there any fix? Please tell me if you need more info. Any help is appreciated. Thank You in Advance!
Update: I found the solution. By doing sudo nano /etc/ssl/openssl.cnf and scrolling to the end, I could change the MIN_VERSION value to be version 1.0 instead of 1.2. This fixed it. This is just for the future in case other people have the same problem!
Related
I am new to Kuma and am trying to set up Multi-Zone deployment mode after experimenting with standalone mode. Currently, I have managed to setup the Global Control Plane on an Azure VM and it seems to be working well.
My problem lies in setting up the Zone Control Planes. I have tried setting up on both Docker, WSL and a VirtualBox Ubuntu VM but I am receiving the same error again and again. It should be noted that I am attempting to set this up using Universal mode, as described on Kuma docs, and have tried both versions 1.4.1 and 1.2.3. The error in question is as below:
ERROR kds-zone.kds-mux-client component terminated with an error (“generationID”: 6, “error”: “rpc error; code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: tls: first record does not look like a TLS handshake””}
I have tried googling this problem, but can’t seem to find any similar problems relating to Kuma, and have also tried experimenting in the kuma.conf.yml file but to no avail.
Thank you in advance to anyone who may have any advice on how to solve this.
Regards,
Daniel
I am about to install RabbitMQ image 3.7.17-debian-9-r37 on a Kubernetes cluster 1.15 using Helm charts.
While starting the RabbitMQ container I see the following error:
Failed to get nodes from k8s -
{failed_connect, [{to_address, {"kubernetes.default.svc.cluster.local",443}},{inet,[inet],{tls_alert,{internal_error, "received CLIENT ALERT: Fatal - Internal Error - {unexpected_error...
It looks like something is wrong with TLS, but I am not sure what exactly.
Can anybody help understand the problem?
Thank you.
I have made some research and found this bug which is what you are currently experiencing.
Current fix versions are:
Fix Version/s:
21.3.8.5, 22.0.4
You can find Debian packages with fixed versions available here.
Please let me know if that helped.
I 'm working on esp8266 module these days.
The firmware on this module is nodemcu 0.9.6 and its language is lua.
I use mqtt protocol for my project and it works well.But TLS is necessary.
I don't know how to set tls on this firmware. I 've searched but documents about TLS on nodemcu website is not enough for me.
I know that I should use this instruction at connection time to broker:
m:connect(BROKER, 8883, 1 , function ( connection ) ... end )
and to put the CA file on module i should use something like this:
enter image description here
that 's what i read from nodemcu website --> https://nodemcu.readthedocs.io/en/master/en/modules/net/#netcertverify
but the problem is when i use this on my code the module doesn't understand it and gives error at upload time and runtime.
is this problem because of the version of my firmware? Upgrading will make it? Or I am just doing something wrong on my code?
I haven't seen sample code about putting CA file on module in other project so I guess my work is wrong.
if you have worked on TLS ( on nodemcu firmware ) I would be happy by your helps.
Build a recent firmware with SSL/TLS enabled.
Flash the binary to upgrade. Make sure all flashing parameters are exactly as documented and include the init data binary.
The rest of your code seems fine.
Take a look at this question and read through comments of the answer.
You may have to get esp_init_data_default.bin from latest sdk.
I used esptool.
esptool.py --port <PORT> write_flash -fm dio -fs 32m 0x00000 <BIN_PATH_AND_FILENAME> 0x3fc000 <PATH\>esp_init_data_default.bin
Please do upvote this post if you find it is useful. Thumbs up for #MarcelStör.
I am using Charles 3.7 to debug SSL connections. I was able to view most of the HTTPS connections, however there is 1 or 2 sites that returned "SSLProtocol: handshake alert: unrecognized_name" when I try to debug it, and I was unable to load the website with Charles on. I am able to do so using Fiddler. Any ideas on how to resolve this issue? Thanks.
I came across this when using the latest beta Charles 3.10b9 on 10.10. We fixed by using a similar method to Shade's answer:
I opened info.plist in Xcode and did the following:
Under the JVMOptions (as oppose to VMOptions) key add the string:
-Djsse.enableSNIExtension=false
Looks like this has more to do with a security improvement from Java 1.7 and server configuration than it does Charles. Can you confirm which JRM Charles is using? help -> about java
Here's an article about the same error message but after upgrading to Java 1.7:
http://www.pressingquestion.com/2030237/Ssl-Handshake-Alert-Unrecognized_name-Error-Since-Upgrade-To-Java-170
Do you need to use Charles for those sites throwing the error? You can disable SSL Proxying per site if not.
Add
-Djsse.enableSNIExtension=false to the info.plist in the Contents folder for the Charles application.
In:
<key>VMOptions</key>
<string>-Xmx512m -Djsse.enableSNIExtension=false</string>
Try using command line from project's path:
mvn clean install -Djsse.enableSNIExtension=false
I tried to run example from HornetQ and I got this error:
[java] HornetQServer_0 out: Deployment "JNDIServer" is in error due to: java.rmi.server.ExportException: Port already in use: 1098
Actually this is not the first time I got this kind of error. I can verify that port 1098 is indeed already in use (using Netstat command) but I just don't know which service using it. Is anybody has encountered such problem?
Thanks in advance for any response and help. :)
Could be JBOSS or Remote Admin Tool. Or something else like Outlook or Firefox.