Mobile app won't connect to instance running on LAN with HTTPS

[J-Carder]

Describe the issue you are experiencing
A clear and concise description of your issue:
I'm running a local instance of xBrowserSync on a Ubuntu Server 22.04 installation. I have it using HTTPS and served under "tcserver.lan" with my Pi-Hole DNS. It has been working fine on my desktop browsers but on mobile (Google Pixel 4a) it doesn't connect. I've tried directly accessing the website via browser (https://tcserver.lan) and that works fine after a brief warning about the certificate that must be accepted.
In addition I've tried pre-release builds but I get the same issue, on v1.7.0 I also tried but it wouldn't run the app (error on starting app). So the latest version I've tried on has been v1.6.0-beta.62.
My guess is that it's because it can't trust the certificate? I'm not sure though, and if this is the case I'm not sure how to get around it.

How can the issue be reproduced?
Steps to reproduce the behavior:

1. Open mobile app
2. Try to scan the sync code via QR code (alternatively in later beta releases enter the sync provider and sync code manually)
3. Attempt to connect to instance

Screenshots
If applicable, add screenshots to help explain your problem:

Desktop browser
Please complete the following information for all affected desktop browsers:

N/A

Mobile device
Please complete the following information for all affected mobile devices:

• Device: Google Pixel 4a
• OS: Graphene OS 13
• Version: v1.5.2, v1.6.0-beta.62, v1.7.0-beta.47

Application log
Please include the logs from the affected clients:

2023-02-05 05:00:56.123	[trace]	Installed v1.5.2
2023-02-05 05:00:56.151	[trace]	Starting up
2023-02-05 05:00:56.161	[trace]	{"checkForAppUpdates":true,"appVersion":"1.5.2","displayHelp":true,"platform":{"name":"Android","device":"Google Pixel 4a"}}
2023-02-05 05:01:10.783	[trace]	Scanned: be8434087b3545c3837750efebc1dd04|$$|https://tcserver.lan
2023-02-05 05:01:11.801	[trace]	Service url changed to: https://tcserver.lan
2023-02-05 05:01:11.953	[error]		Error: [10001] HttpRequestFailed at file:///android_asset/www/js/app.min.js:2461:38 at file:///android_asset/www/js/app.min.js:140:44 at m.$digest (file:///android_asset/www/js/app.min.js:151:185) at m.$apply (file:///android_asset/www/js/app.min.js:155:35) at k (file:///android_asset/www/js/app.min.js:106:129) at v (file:///android_asset/www/js/app.min.js:111:206) at y.onabort (file:///android_asset/www/js/app.min.js:112:301)
2023-02-05 05:01:12.067	[error]		Error: [10001] HttpRequestFailed at file:///android_asset/www/js/app.min.js:2461:38 at file:///android_asset/www/js/app.min.js:140:44 at m.$digest (file:///android_asset/www/js/app.min.js:151:185) at m.$apply (file:///android_asset/www/js/app.min.js:155:35) at k (file:///android_asset/www/js/app.min.js:106:129) at v (file:///android_asset/www/js/app.min.js:111:206) at y.onabort (file:///android_asset/www/js/app.min.js:112:301)
2023-02-05 05:01:20.229	[error]		Error: [10001] HttpRequestFailed at file:///android_asset/www/js/app.min.js:2461:38 at file:///android_asset/www/js/app.min.js:140:44 at m.$digest (file:///android_asset/www/js/app.min.js:151:185) at m.$apply (file:///android_asset/www/js/app.min.js:155:35) at k (file:///android_asset/www/js/app.min.js:106:129) at v (file:///android_asset/www/js/app.min.js:111:206) at y.onabort (file:///android_asset/www/js/app.min.js:112:301)