server-trojan

Yet another unofficial Trojan server container with x86 and arm/arm64 (Raspberry Pi) support.

[Optional] How to build server-trojan docker image

$ git clone https://github.com/samuelhbne/server-trojan.git
$ cd server-trojan
$ docker build -t samuelhbne/server-trojan:amd64 -f Dockerfile.amd64 .
...

NOTE1

• Please replace "amd64" with the arch match the current box accordingly. For example: "arm64" for AWS ARM64 platform like A1 and t4g instance or 64bit Ubuntu on Raspberry Pi. "arm" for 32bit Raspbian.

How to start server-trojan container

$ docker run --rm -it samuelhbne/server-trojan:amd64
server-trojan -d|--domain <domain-name> -w|--password <password> [-p|--port <port-num>] [-f|--fake <fake-domain>] [-k|--hook <hook-url>]
    -d|--domain <domain-name> Trojan server domain name
    -w|--password <password>  Password for Trojan service access
    -p|--port <port-num>      [Optional] Port number for incoming Trojan connection, default 443
    -f|--fake <fake-domain>   [Optional] Fake domain name when access Trojan without correct password
    -k|--hook <hook-url>      [Optional] URL to be hit before server execution, for DDNS update or notification
$ docker run --name server-trojan -p 80:80 -p 8443:443 -d samuelhbne/server-trojan:amd64 -d my-domain.com -w my-secret
...
$

NOTE2

• Please replace "amd64" with the arch match the current box accordingly. For example: "arm64" for AWS ARM64 platform like A1 and t4g instance or 64bit Ubuntu on Raspberry Pi. "arm" for 32bit Raspbian.
• Please ensure TCP port 80 of the current server is reachable, or TLS cert acquisition will fail otherwise.
• Please replace 8443 with the TCP port number you want to listen for Trojan service.
• Please replace "my-domain.com" and "my-secret" above with your FULL domain-name and Trojan service access password accordingly.
• You can optionally assign a HOOK-URL to update the DDNS domain-name pointing to the current server public IP address.
• Alternatively, server-trojan assumes you've ALREADY set the domain-name pointed to the current server public IP address. server-trojan may fail as unable to obtian Letsencrypt cert for the domain-name you set otherwise .
• You may reach the limitation of 10 times renewal a day applied by Letsencrypt soon if you remove and restart server-trojan container too frequent.

How to verify if server-trojan is running properly

Try to connect the server from trojan compatible mobile app like Igniter for Android or Shadowrocket for iOS with the domain-name and password set above. Or verify it from Ubuntu / Debian / Raspbian client host follow the instructions below.

Please run the following instructions from Ubuntu / Debian / Raspbian client host for verifying

$ docker run --rm -it samuelhbne/proxy-trojan:amd64
proxy-trojan -d|--domain <trojan-domain> -w|--password <password> [-p|--port <port-number>]
    -d|--domain <trojan-domain>   Trojan server domain name
    -w|--password <password>      Password for Trojan server access
    -p|--port <port-num>          [Optional] Port number for Trojan server connection, default 443
$ docker run --name proxy-trojan -p 1080:1080 -p 65353:53/udp -p 8123:8123 -d samuelhbne/proxy-trojan:amd64 -d my-domain.com -p 8443 -w my-secret
...

$ curl -sSx socks5h://127.0.0.1:1080 http://ifconfig.co
12.34.56.78

NOTE4

• First we ran proxy-trojan as SOCKS5 proxy that tunneling traffic through your trojan server.
• Then launching curl with client-IP address query through the proxy.
• This query was sent through your server with server-trojan running.
• You should get the public IP address of your server with server-trojan running if all good.
• Please have a look over the sibling project proxy-trojan for more details.

How to stop and remove the running container

$ docker stop server-trojan;
...
$ docker rm server-trojan
...
$