# Failure on bitwarden mobile with custom certificates

**URL:** <https://vaultwarden.discourse.group/t/failure-on-bitwarden-mobile-with-custom-certificates/3582>\
**Category:** Third Party Help\
**Created:** [April 25, 2024, 7:33am UTC](https://vaultwarden.discourse.group/t/failure-on-bitwarden-mobile-with-custom-certificates/3582 "2024-04-25T07:33:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![DrR0x](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/drr0x/32/1432_2.png) [@DrR0x](https://vaultwarden.discourse.group/u/DrR0x)\
**Post date:** [April 25, 2024, 7:33am UTC](https://vaultwarden.discourse.group/t/failure-on-bitwarden-mobile-with-custom-certificates/3582/1 "2024-04-25T07:33:02Z")

</div>

I am using truenas scale, truecharts with ingress running locally. I have enabled traefik with https using the truenas certs that are not valid but do sign the connection. On PC the extension and local url work fine through https, however the mobile app will not connect.

Is there a way to make Bitwarden mobile “less strict” about it’s certificates.