Skip to content

Privacy-first password manager with built-in email aliasing. Fully encrypted and self-hostable.

Update self-hosted docs mobile app SSL certificate note

Leendert de Borst9b85cdd9abf0
diff --git a/docs/installation/docker-compose/index.md b/docs/installation/docker-compose/index.md
index ca1f2ea0a..2d01e7dac 100644
--- a/docs/installation/docker-compose/index.md
+++ b/docs/installation/docker-compose/index.md
@@ -82,10 +82,12 @@ services:
## 2. SSL/TLS configuration
To use AliasVault securely, HTTPS is required in the following situations:
- When accessing the web app from any address other than `localhost` (due to browser security restrictions)
-- When using the mobile apps, which require the API URL to have a valid TLS certificate; otherwise, the app will not connect
+- When using the mobile apps, which require the API URL to be served with a **publicly trusted** TLS certificate; otherwise, the app will not connect
You must set up and configure your own TLS/SSL infrastructure (such as Traefik, Nginx, HAProxy, or Cloudflare Tunnel) to make the AliasVault container accessible over HTTPS with a valid SSL/TLS certificate. For example: `https://aliasvault.yourdomain.com`.
+**Note:** the mobile apps enforce SSL certificate validation at the OS level with no "Proceed anyway" option. If the web app and browser extension work but the mobile app does not: check the validity of your SSL cert: it must be issued by a publicly recognized CA (e.g. Let's Encrypt). Self-signed certificates, internal CAs, or ones manually added to the device keystore will not work.
+
---
## 3. Email Server Setup
diff --git a/docs/installation/docker-compose/troubleshooting.md b/docs/installation/docker-compose/troubleshooting.md
index a9986215d..220749d0b 100644
--- a/docs/installation/docker-compose/troubleshooting.md
+++ b/docs/installation/docker-compose/troubleshooting.md
@@ -160,6 +160,10 @@ docker compose restart
4. You can now log in to the admin panel (`/admin`) with the new password.
+### 5. Mobile app cannot connect, but web app and browser extension work
+
+The mobile apps enforce certificate trust at the OS level and reject certificates that browsers would accept with a warning. The certificate served by your reverse proxy must be issued by a publicly recognized CA: self-signed certificates, internal CAs, or ones manually added to the device keystore will not work.
+
---
## Other Issues
diff --git a/docs/installation/script/index.md b/docs/installation/script/index.md
index b0373d2da..b32fa0d4c 100644
--- a/docs/installation/script/index.md
+++ b/docs/installation/script/index.md
@@ -55,7 +55,9 @@ chmod +x install.sh
---
## 2. TLS/SSL configuration
-The default installation will create a self-signed TLS/SSL certificate and configure Nginx to use it. This is sufficient for local deployments using only the web-app, however the mobile apps (iOS and Android) require a valid (external) SSL certificate to be able to connect.
+The default installation will create a self-signed TLS/SSL certificate and configure Nginx to use it. This is sufficient for local deployments using only the web app, however the mobile apps (iOS and Android) require a **publicly trusted** SSL certificate to be able to connect.
+
+**Note:** mobile apps enforce SSL certificate validation at the OS level with no "Proceed anyway" option, so the certificate must be issued by a publicly recognized CA (e.g. Let's Encrypt): self-signed certificates or ones manually added to the device keystore will not work. If the web app and browser extension connect but the mobile app does not, check the validity of your SSL cert first.
To generate a valid external TLS/SSL certificate for AliasVault, you can use Let's Encrypt via a built-in helper tool. In order to make this work you will need the following:
diff --git a/docs/installation/script/troubleshooting.md b/docs/installation/script/troubleshooting.md
index b022b2d95..e9eeb1a46 100644
--- a/docs/installation/script/troubleshooting.md
+++ b/docs/installation/script/troubleshooting.md
@@ -94,7 +94,11 @@ docker compose logs reverse-proxy
./install.sh restart
```
-### 3. No emails being received
+### 3. Mobile app cannot connect, but web app and browser extension work
+
+The mobile apps enforce certificate trust at the OS level and reject certificates that browsers would accept with a warning. The certificate must be issued by a publicly recognized CA: self-signed certificates or ones manually added to the device keystore will not work.
+
+### 4. No emails being received
If you are not receiving emails on your aliases, check the following:
- Verify DNS records are correctly configured
- Ensure ports 25 and 587 are accessible