Trojan server and Caddy integration with Docker compose。
Trojan server listens port 443. For https requests from normal sources, Trojan server will forward them to Caddy server for processing and return to the Web page while requests from Trojan client will be proxied by Trojan server which like V2ray+Websocket+TLS avoid GFW detection by disguising requests.
Git clone this repo then change directory to this project.
-
Modify
./caddy/Caddyfile
:www.yourdomain.com:80 { root * /usr/src/trojan log { output file /usr/src/caddy.log } file_server } www.yourdomain.com:443 { root * /usr/src/trojan log { output file /usr/src/caddy.log } file_server }
Replace
www.yourdomain.com
with your own domain name. -
Modify
./trojan/config/config.json
:Change
your_password
to your own password onconfig:json:8
, this is your trojan password just safekeeping.Change
your_domain_name
to your own domain name onconfig:json:12-13
, this is your domain ssl certification path, Caddy server generate certs automatically on the path/ssl/your_domain_name/your_domain_name.crt
-
Run
docker-compose up
ordocker-compose up -d
with Daemon mode -
When each container is successfully built, it means that your Trojan and Caddy servers are working well. If Trojan container crashes temporarily, please wait until it restart later due to certication registering.
If you encounter any problems during the deployment process, you can raise them in' issue' considering various unknown situations.