Skip to content

[BUG] [Android] SSL Certificate Error with OS-trusted custom CA - Regression in v1.2.0 #468

Description

@HerkimerDev

Title

Android app v1.2.0 does not trust user-installed CA certificates, despite being trusted at the OS level. This was previously fixed in v1.1.0 (see #212) and appears to have regressed.

Platform

App - Android

Server Installation Method

Docker (behind Traefik reverse proxy)

Version

1.2.0

Troubleshooting

  • I have examined logs and tried to find the issue
  • I have reviewed opened and closed issues
  • I have tried restarting the application

The Problem

The Android app (v1.2.0) fails to connect with the error:

SSL Certificate Error
Unable to verify the server's SSL certificate. Please ensure:

  1. Your self-signed certificate's root CA is installed in Android Settings > Security > Encryption & Credentials > Install a certificate
  2. The certificate is installed as a 'CA certificate'
  3. You've rebuilt the app after installing the certificate

Error: SSL error: The certificate authority is not trusted

The root CA is installed as a CA certificate in Android. Chrome and Edge on the same device connect to the same URL over HTTPS without any certificate warnings. This is the same behavior reported in #212, which was fixed in v1.1.0.

This was working earlier today on the same app version and stopped unexpectedly.

How to Reproduce

  1. Set up Termix behind a reverse proxy (Traefik) with a certificate signed by a private root CA
  2. Install the root CA as a CA certificate in Android settings
  3. Verify HTTPS works in Chrome on Android (shows as trusted)
  4. Open the Termix Android app (v1.2.0) and attempt to connect
  5. App shows SSL Certificate Error despite the CA being trusted at the OS level

Certificate Details

  • Wildcard cert with proper SANs
  • Issued by a custom root CA installed in Android as a CA certificate
  • Certificate is valid (not expired)
  • openssl verify confirms the chain is valid
  • Chrome on the same Android device trusts the certificate without issues

Additional Context

This appears to be a regression of #212, which was resolved in v1.1.0. The app may not be reading from the Android user trust store correctly in v1.2.0.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingsecurity

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions