Documentation · Help

Troubleshooting common issues

Fixes for self-signed SSL certificates, private HTTP restrictions, SSH host key changes, Gemini quotas, and Drive restore errors.

Quick solutions for the most common issues when setting up Portainer, SSH, hybrid AI, or Google Drive backups.

SSL or TLS certificate error in Portainer

Symptom: SSL Certificate error. Enable "Allow Insecure".

Causes & fix:

  • If your Portainer instance uses HTTPS with a self-signed certificate (for example port 9443), edit the server profile and toggle Allow self-signed certificates.
  • If you sit behind a reverse proxy (Caddy, Traefik, Nginx) with a public certificate, verify the URL hostname matches the certificate and your device date/time are accurate.

Plain HTTP blocked for a host

Symptom: STALMAS refuses an http:// address outside your private LAN.

Why it happens: CleartextGuard blocks cleartext HTTP toward public hosts to keep API keys and passwords encrypted in transit. Plain HTTP is allowed only for localhost, .local, and RFC 1918 private ranges (10.x.x.x, 172.16.x.x–172.31.x.x, 192.168.x.x). Use https:// or connect over a private VPN (WireGuard / Tailscale).

SSH refuses connection due to changed host key

Symptom: Stored TOFU fingerprint differs from the server’s current key.

Checklist:

  1. If you reinstalled the OS or regenerated /etc/ssh/ssh_host_*, inspect the new fingerprint directly on your server with ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub.
  2. Accept the updated fingerprint only after confirming the change was yours. If nothing changed on the host, pause and investigate your network path before connecting.

Gemini BYOK quota reached or busy

Symptom: Your Gemini key has no quota left for this model... or The cloud AI is busy right now.

  • Use Check my key inside Settings → AI Integration to estimate whether your API key is on the free or paid tier.
  • If a specific model hits rate limits, switch to another model in the selector or switch to an on-device Gemma 4 model (Pro).

Google Drive backup fails to decrypt

Symptom: Wrong password or PIN for this backup / Wrong password or corrupted backup.

  • appDataFolder snapshots are encrypted locally with AES-256 using the exact master password entered when creating them. Double-check casing or an earlier PIN. There is no server-side recovery for forgotten encryption passwords.

How to report a technical problem from the app

If you run into a bug or crash:

  1. Open Settings → Report a problem inside STALMAS.
  2. Briefly describe what happened and choose whether to include recent app error diagnostics (and, if you use local AI, technical metadata about the active model and accelerator).
  3. Tap Preview report to inspect the full text: STALMAS automatically redacts IP addresses, private domains, passwords, and tokens before building the draft.
  4. Tap Send to open a pre-filled email draft to report@stalmas.app (or copy the report to your clipboard if no email app is configured). You can also visit our Support & contact page.