Describe the bug
Scrypted is working fine. I have a reverse proxy in front of it for external access (Cloudflare tunnel or integration isn't sufficient for my needs). If I use regular OIDC authentication to authenticate the user, and then pass them through to Scrypted, it works fine.
If I enforce mTLS and access the public url from a web browser, the browser prompts to select a certificate, and then it proceeds as usual. Great.
However, the Android app doesn't prompt for a certificate, nor does it redirect to a web browser to support either mTLS or any third-party https authentication. It only works with the built-in authentication.
To Reproduce
Steps to reproduce the behavior:
- Install Scrypted
- In the Cloud plugin, enable custom domain
- Configure a reverse proxy properly, using OIDC authentication (or none), forwarding to the port noted in the Cloud plugin
- Verify that everything works as it should, from a desktop web browser, mobile browser and the Android app
- Alter the reverse proxy to validate the client via mTLS, and properly deploy certificates to the client devices
- Observe that Scrypted can be accessed from a desktop web browser, a mobile browser (in both cases, prompting for certificates as needed), but not the Android app, where it just says "TypeError: Failed to fetch"
Server (please complete the following information):
- OS: macOS 26
- Installation Method: Desktop App
Hardware Model (please complete the following information):
N/A
Client (please complete the following information, if applicable):
- Desktop browsers (chrome, firefox)
- mobile browser (firefox)
- Scrypted Android app
Additional context
Would be nice to either provide a way to upload the certificate into the mobile app, or have the app use the normal OS flows for TLS that display the Android system-level certificate popup.
Login theManagement Consolefor errors or warnings that may help identify and resolve the issue myself.Describe the bug
Scrypted is working fine. I have a reverse proxy in front of it for external access (Cloudflare tunnel or integration isn't sufficient for my needs). If I use regular OIDC authentication to authenticate the user, and then pass them through to Scrypted, it works fine.
If I enforce mTLS and access the public url from a web browser, the browser prompts to select a certificate, and then it proceeds as usual. Great.
However, the Android app doesn't prompt for a certificate, nor does it redirect to a web browser to support either mTLS or any third-party https authentication. It only works with the built-in authentication.
To Reproduce
Steps to reproduce the behavior:
Server (please complete the following information):
Hardware Model (please complete the following information):
N/A
Client (please complete the following information, if applicable):
Additional context
Would be nice to either provide a way to upload the certificate into the mobile app, or have the app use the normal OS flows for TLS that display the Android system-level certificate popup.