What are you trying to achieve? I am trying to configure the Envoy mobile app to use my self-hosted StartOS block explorer as a Custom Block Explorer over my local network.
What steps are you taking to try and achieve this? I navigated to Envoy’s Privacy settings > Block Explorer > Custom. I have tried pointing Envoy to my StartOS node using several URL formats, appending /tx/ not appending /tx/ to the end of each.
I’ve tried:
* Local IP (HTTPS): https://:/
* Local IP (HTTP): http://:/
* StartOS mDNS: https://.local:/
I have also ensured that the StartOS Root CA is fully installed and trusted on my mobile device.
What are you seeing or experiencing to suggest that something is wrong? When I try to setup the explorer connection in Envoy, the connection fails to load. However, if I paste those exact same addresses into my mobile browser, or configure them in Sparrow Wallet on my desktop, they load perfectly.
Because the links work everywhere else, it appears Envoy’s in-app web engine is either aggressively rejecting the .local StartOS self-signed certificate (ignoring the Root CA installed on the OS level), or Envoy is blocking the local network routing entirely.
What version of Envoy are you using? [2.3.1]
Does your query relate to the mobile wallet or a Passport account? Mobile wallet.
Thanks for the detailed report. I have now reproduced this using Envoy 2.3.1 and a StartOS-hosted Mempool block explorer over a local HTTPS address.
I initially received the same error because the StartOS Root CA profile was installed but had not been given Full Trust for SSL/TLS. After enabling Full Trust, Envoy connected successfully.
I appreciate that you already confirmed your Root CA is fully installed and trusted, so I do not want to assume you missed that step. There is another setting that may explain what you are seeing.
When Improved Privacy is enabled, Envoy currently routes its block-explorer validation request through Tor. Tor cannot reach a private IP or .local hostname. Could you please try the following:
In Envoy, select Better Performance so that Tor is turned off.
Enter only the explorer’s base address, with no trailing slash and no /tx/, for example:
https://192.168.x.x:port
Confirm the StartOS Root CA is enabled under Settings > General > About > Certificate Trust Settings, rather than only being installed under VPN & Device Management.
Open the following URL in Safari and confirm that it loads without a privacy warning and without manually bypassing one:
If those checks pass but Envoy still cannot connect, please send your Envoy logs from Settings > Advanced > View Envoy Logs, along with your phone model and OS version. The logs should tell us whether Envoy is encountering a certificate, local-network permission, DNS or connection error.
Thanks, that log confirms the likely cause. Envoy is reaching your StartOS server, but its native HTTP client is rejecting the self-signed certificate chain. Your browser trusts the CA you installed as a user certificate, but Envoy does not seem to inherit Android’s user-added CA trust.
So this is an Envoy compatibility gap, rather than a problem with your StartOS configuration. We will raise it with engineering.