Certificate hostname mismatch error in v1.2.1 (works in v1.2.0)

[Scemp]

Environment:

• App version: 1.2.1
• Previous working version: 1.2.0
• Android version: 16
• Device: OnePlus 15

Steps to reproduce:

1. Install opencloud/android v1.2.1
2. Enter server URL: "https://truenas:30259"
3. Accept/trust the certificate when prompted

Expected behavior:
After trusting the certificate, the app should proceed to authentication (similar to v1.2.0, which redirects to the browser login and works correctly).

Actual behavior:
After trusting the certificate, a new window appears with the error:

the url does not match the hostname in the certificate

Additional context:

• Downgrading to version 1.2.0 resolves the issue.
• In v1.2.0, entering the same URL redirects to the browser for login, and everything works as expected.
• This suggests a regression introduced in v1.2.1 related to certificate or hostname validation.

Notes:

• The setup uses a local hostname ("truenas") with a custom/self-signed certificate.
• Behavior change seems specific to the new version’s handling of certificates or redirect/login flow.

Let me know if logs or additional debugging info would help.

[guruz]

@Scemp Do you think you could bring "truenas" into the Subject Alternative Name (SAN) of the certificate?
What is the CN and SAN in the cert now?

[Scemp]

When hitting DETAILS regarding the error I can encounter:

Issued to:
Common name:
OpenCloud
...
Issued by:
Common name:
OpenCloud
...

but there is no sign on SAN. I am also not sure where the certificate is stored and thus, I cannot access the cert from my phone. If you lead me to the actual location, I could provide additional information.

[guruz]

How did you install your server?
(Especially with regards to SSL/TLS certificate used for web or client access)

[zerox80]

@Scemp Can you test it with my Branch please? Look PR

[guruz]

@Scemp Can you test it with my Branch please? Look PR

I think I can create a teat build (QA app) for @Scemp .. Will ping about it.

I'm still curious though about people having setups where the server does not have a proper SSL setup (e.g. from LetsEncrypt or whatever)

How did you install your server?
(Especially with regards to SSL/TLS certificate used for web or client access)

[zerox80]

I use lets encrypt on my own server and it works fine.

Ah yea, github actions build sounds good!

[Scemp]

@zerox80 I’ve now compiled your PR into an APK and installed it on my phone. Everything works perfectly on my side now. Thanks a lot for your help and the quick turnaround!

@guruz Regarding the certificate setup: I’m using the default TrueNAS configuration and the generated certificate looks like this:

• Common Name (CN): localhost
• SAN: DNS:localhost

Since I was not aware of the certificates in the first place, I might consider using encrypt to create a certificate and use this from now on.

[guruz]

-> http://play.google.com/apps/testing/eu.opencloud.android 1.2.2