Chained Proxy and Intranet Penetration are the two advanced features of Go-Proxy and are configured as follows:
Chained Proxy Configuration
- Edit config.yaml and add a new line in the
upstream_proxiesSection Add:- protocol: socks5 address: proxy1.example.com:1080 credential: user:pass - Support for nested multiple upstream agents
- start using
failover: trueEnables automatic failover
Intranet Penetration Configuration
- running on the penetrated intranet machine:
./go-proxy -mode tunnel -server 公网代理IP - Configuration on the public proxy side:
tunnels: web_app: local_addr: 192.168.1.100:80 subdomain: app - pass (a bill or inspection etc)
app.yourdomain.comAccess to intranet services
Key considerations: 1) Chained proxies will increase latency by 30-50ms, no more than 3 hops are recommended; 2) Ensure that the NAT type is Full Cone for intranet penetration; 3) Always enable TLS encrypted tunnels for production environments. Complex network topology is recommended to combinenetwork_policyConfigure fine-grained access rules.
This answer comes from the articleGo-Proxy: A High Performance Reverse Proxy Server for Docker IntegrationThe
May not be reproduced without permission:AI productivity tools " How to configure Go-Proxy for chaining proxy and intranet penetration?
