[Bug] SSL initialization failed on login — regression in 33.1.0 (worked in 33.0.1)

[D4rkAn6e1]

⚠️ Before posting ⚠️

• This is a bug, not a question or an enhancement.
• I've searched for similar issues and didn't find a duplicate.
• I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
• I agree to follow Nextcloud's Code of Conduct.

Bug description

After updating the Nextcloud Android app from 33.0.1 to 33.1.0, the login screen immediately shows "SSL initialization failed" when entering the server URL. The browser on the same device connects without any issue. Downgrading to 33.0.1 restores normal behavior, confirming this is a regression introduced in 33.1.0.

Steps to reproduce

1. Update Nextcloud Android app to 33.1.0
2. Open the app and enter the server URL (https://nextcloud.example.com)
3. Observe "SSL initialization failed" error — no login form is shown
   Mirror.

Expected behaviour

The app connects and displays the login form, as it did on 33.0.1.

Actual behaviour

"SSL initialization failed" error immediately on URL entry, both with domain name and direct IP address (https://100.x.x.x).

Environment

• Nextcloud Android app: 33.1.0 (regression from 33.0.1)
• Nextcloud server version : 33.0.2
• Android version : 16
• Device brand and model : Samsung galaxy S24
• Server access: via Tailscale VPN (server IP in 100.x.x.x range)
• Reverse proxy: Nginx Proxy Manager + Let's Encrypt (fullchain)
• Browser on same device: works fine
• Direct IP entry in app: same SSL error

TLS verification (PowerShell)

TLS handshake succeeds from another device on the same Tailscale network:

Subject: CN=nextcloud.example.com
Issuer: CN=E7, O=Let's Encrypt, C=US
Expires: 09/06/2026

Certificate and chain are valid — the issue is in the app, not the server.

Workaround

Downgrade to 33.0.1 from APKMirror.