Build 21301 fails to connect to SSL MQTT
See original GitHub issueI was part of the beta of OwnTracks on the Play Store. After the update of yesterday, my OwnTracks client ceased working immediate. It simply wouldn’t connect to my MQTT server anymore. It only showed “error” in the app, but unfortunately didn’t show any details
After exporting the config, leaving the beta, uninstalling, reinstalling the stable version and importing the config it works again as it did before.
With the new version (build 21301) my MQTT server reports issues with SSL:
1551816331: New connection from X.X.X.X on port 8883.
1551816331: OpenSSL Error: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
1551816331: Socket error on client <unknown>, disconnecting.
1551816341: New connection from X.X.X.X on port 8883.
1551816341: OpenSSL Error: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
1551816341: Socket error on client <unknown>, disconnecting.
1551816412: New connection from X.X.X.X on port 8883.
1551816412: OpenSSL Error: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown
1551816412: OpenSSL Error: error:140940E5:SSL routines:ssl3_read_bytes:ssl handshake failure
1551816412: Socket error on client <unknown>, disconnecting.
This works just fine with the previous build, 21201.
As MQTT server I’m using Mosquitto 1.4.8 on Ubuntu 16.04 LTS.
- App build number: 21301
- Android version: 9
- Device: OnePlus 6T
Issue Analytics
- State:
- Created 5 years ago
- Comments:8
Top Results From Across the Web
can't connect to mqtt broker via ssl
The hostname you use to connect needs to match the CN or SAN entries in the certificate presented by the broker or else...
Read more >[solved] MQTT with SSL/TLS not working with Home Assistant
I'm trying to setup MQTT with Home assistant, but it doesn't want to work. I'm running Mosquitto broker (not add-on) with configured SSL/TLS ......
Read more >LG Smart ThinQ - Bindings - openHAB Community
I'm trying to use @mgw 's Thinq-MQTT-Proxy with an LG dryer… The connection works, I see the initial message in MQTT Explorer, but...
Read more >Connecting to an MQTT Broker over SSL does not work - GitLab
Hey, Expliot gets stuck, when trying to connect to an MQTT Broker which does support SSL only (8883/tcp open ssl/mosquitto version 1.5.7).
Read more >Readme file for IBM Workload Scheduler Version 9.5 Fix ...
Running the CURL command from an Unix machine causes a "CURL: FAILED INITIALIZATION" error. IJ14140, In case of SSL connection issues, the ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Try to change ‘Common Name’ to proper one or try LetsEncrypt cert for mosquitto. One of these would be solution i guess. I bet the last one. I can confirm, i had also issues with the newer version of the app, but after putting my LE cert into mosquitto and restarting the container its ok now. (i just need to reconfigure android client also, because new cert, previously i had self signed and had ca cret installed on android).
I was surprised by the number of testers myself. Glad it is working as expected now.
Thanks for uncovering that change in behavior. I’ll add a warning to the release notes of the public version.
Issue will be closed as everything is working as intended.