Unable to connect to HTTP endpoint using TLS about android HOT 11 OPEN

Have you read "Breaking Changes" in our Changelog ?

from android.

Hi @jpmens , thanks for responding

I'm using a certificate from Let's Encrypt, so it should be trusted by the Android trust store. I can connect to the same URI using curl or chrome.

from android.

Do I see a TLS v1 connection attempt there? Our Changelog says:

TLSv1 and TLSv1.1 are deprecated. Supported TLS versions are 1.2 and 1.3.

from android.

I think it's a v1 request with a v1.3 response.

Without seeing both the app log and status message, it's going to be hard to figure out what's going on here.

from android.

@ilanco are you able to send both, unobfuscated please, to [email protected] so that @growse can take a look?

from android.

If you also want to email us your endpoint, I can try and recreate the connection here.

from android.

I've sent both the app log and status message and the endpoint to [email protected]. Thanks!

from android.

Thanks - I seem to be able to send messages from my test device to your endpoint. I see you're using HTTP auth, are you including those credentials in the URL itself, or setting them with the credentials part on the connection screen?

from android.

Hi Growse, thank you for testing the endpoint from your side. I believe I set the credentials in the dedicated settings. However, I tested without HTTP auth as well and could not connect using https, only http.

Did you use the beta version installed from Google Play or from the GitHub releases?

from android.

Hi guys, I've performed another test using owntracks-release-oss-420500002.apk loaded from the GitHub releases page. Using this version I was able to connect using https.

from android.

Ok, that's weird.

Could you confirm that the oss APK (from the GH release) works, but the gms one doesn't?

from android.