Independent • Trojan Protocol • BYO Provider

avoGate
mobile Trojan VPN client

avoGate is a lightweight, privacy-first VPN client for the Trojan protocol. It’s provider-agnostic: import a config from any Trojan service or your own server, then connect in one tap.

Install Size
~37 MB
Accounts
Not required
Protocol
Trojan (TLS)
Platforms
iOS
# Quick peek
# 1) Get a Trojan config 
(from provider or your server)
# 2) Import into avoGate via key
# 3) Tap Connect

trojan://6270d530-289e-4e2b
@95.141.32.52:443?security=tls
&sni=owlycloud.biz&fp=chrome
#avogate.com

Features / what you get

Provider-agnostic

Bring your own Trojan config from any provider or a self-hosted server. No lock-in, no accounts required.

Import made easy

Paste a key trojan://. We parse and validate before saving.

Local-only telemetry

No personal data collection. Connection logs are temporarily stored on your device and log only the traffic of the current session.

Fine-grained controls

Tune SNI, ALPN, and certificate checks.

Screenshots / interface preview

Screenshot avoGate Main Screenshot avoGate Success Screenshot avoGate On Screenshot avoGate Off

Download / iOS

iOS

  • Minimum: iOS 15
  • Architecture: arm64
  • App Store

Getting Started / 1-minute setup

  1. Install avoGate on your device.
  2. Get a Trojan config from any provider or set up your own server.
  3. Import the config via Key.
  4. Tap Connect. You’re online.
Typical connection checklist (if it doesn’t connect)
  • Host reachable on 443 (or your custom port)
  • Valid TLS certificate (hostname matches SNI)
  • Correct password and ALPN (e.g., h2 / http/1.1)
  • Device clock is accurate (TLS depends on time)
  • Try cellular vs Wi-Fi to rule out local filters

Documentation / reference & guides

A) Client configuration

avoGate consumes Trojan URLs and transforms them into saved profiles. A typical URL looks like:

trojan://UUID
@host.example.com:443
security=tls&sni=example.com
&alpn=h2&fp=chrome
#avogate

Parameters (commonly used):

  • UUID — shared secret
  • host:port — server endpoint (default port 443)
  • security — type of encryption tls
  • sni — TLS Server Name (hostname in certificate)
  • alpn — application-layer protocol (e.g., h2, http/1.1)
  • fp — fingerprint, most often Chrome
  • avogate (# fragment) — profile label

Logs

Local connection logs contain minimal information, only about the amount of traffic for the current session. Logs never leave your device and are cleared immediately after reconnecting to the VPN.

B) Self-hosting a Trojan server

You can deploy a minimal Trojan server on any Linux VPS. The snippet below illustrates a quick Docker-based setup.

version: "3"
services:
  trojan:
    image: ghcr.io/example/trojan:latest
    container_name: trojan
    ports:
      - "443:443"
    environment:
      - TROJAN_PASSWORD=change-me
      - TROJAN_SNI=your.domain
      - TROJAN_ALPN=h2
    volumes:
      - ./certs:/certs:ro
    restart: unless-stopped

Certificates: use Let’s Encrypt or an equivalent; ensure the certificate’s CN/SAN matches the SNI you configure in avoGate.

Hardening checklist

  • Use a firewall to allow only required ports
  • Prefer strong ciphers and TLS 1.3 where possible
  • Rotate passwords regularly
  • Monitor for abnormal traffic patterns

C) Integrations

Key should embed a standard trojan:// URL. The app will parse and validate before saving a profile.

D) Troubleshooting

Handshake fails with certificate error

Ensure your SNI matches the certificate hostname, the certificate is valid, and the device clock is correct.

Connects on mobile data but not Wi-Fi

Your local network may filter outbound 443 or TLS traffic. Try a different network or port if your server allows it.

Slow speeds or frequent drops

Test a closer server, verify DNS resolution, and try alternative ALPN settings (h2 vs http/1.1).

E) Security & privacy

  • No accounts: the app works entirely with local profiles you import.
  • No personal data collection: avoGate does not collect user identifiers or traffic logs.
  • Local telemetry only: cleared immediately after reconnecting to the VPN..
  • Permissions: only what’s necessary to create a secure VPN tunnel and import configurations.

Support / help desk

Contact

Email: support@avogate.net
Community: Telegram

avoGate is an autonomous client; there’s no central service dependency required to connect.

About / project

avoGate is a focused mobile client for the Trojan protocol. We prioritize privacy, minimalism, and transparent ergonomics for technically minded users.

Roadmap (high-level)

  • Profile export & secure backup
  • Per-app routing (Android), on-device DNS options
  • Optional widgets / quick tiles