Initial commit: combine nas_tool, nas_webdav, sync-utils
This commit is contained in:
@@ -0,0 +1,139 @@
|
||||
# Clash Proxy Server Configuration
|
||||
|
||||
## Server Details
|
||||
- **Server:** server2 (oracle-tokyo)
|
||||
- **Tailscale IP:** 100.70.115.1
|
||||
- **Status:** ✅ Running
|
||||
|
||||
## Proxy Endpoints
|
||||
|
||||
### HTTP Proxy
|
||||
- **Type:** HTTP
|
||||
- **Server:** 100.70.115.1
|
||||
- **Port:** 7890
|
||||
|
||||
### SOCKS5 Proxy
|
||||
- **Type:** SOCKS5
|
||||
- **Server:** 100.70.115.1
|
||||
- **Port:** 7891
|
||||
|
||||
### Mixed Port (Recommended)
|
||||
- **Type:** HTTP/SOCKS5 (auto-detected)
|
||||
- **Server:** 100.70.115.1
|
||||
- **Port:** 7892
|
||||
|
||||
### Web Dashboard
|
||||
- **URL:** http://100.70.115.1:9090/ui
|
||||
- Use this to monitor traffic and manage settings
|
||||
|
||||
## Client Configuration
|
||||
|
||||
### For Clash Clients (Clash for Windows, ClashX, Clash Verge, etc.)
|
||||
|
||||
#### Option 1: Direct Proxy Configuration
|
||||
In your Clash client settings, add a proxy:
|
||||
|
||||
```yaml
|
||||
proxies:
|
||||
- name: "server2-proxy"
|
||||
type: http
|
||||
server: 100.70.115.1
|
||||
port: 7890
|
||||
# Or use mixed port:
|
||||
# port: 7892
|
||||
```
|
||||
|
||||
#### Option 2: Use as Upstream Proxy
|
||||
If you want to route through server2:
|
||||
|
||||
```yaml
|
||||
proxies:
|
||||
- name: "server2"
|
||||
type: http
|
||||
server: 100.70.115.1
|
||||
port: 7892
|
||||
```
|
||||
|
||||
Then add it to your proxy groups:
|
||||
```yaml
|
||||
proxy-groups:
|
||||
- name: "Proxy"
|
||||
type: select
|
||||
proxies:
|
||||
- server2
|
||||
- DIRECT
|
||||
```
|
||||
|
||||
### For System-Wide Proxy (macOS/Windows)
|
||||
|
||||
#### macOS:
|
||||
1. System Settings → Network → Advanced → Proxies
|
||||
2. Check "Web Proxy (HTTP)" and "Secure Web Proxy (HTTPS)"
|
||||
3. Server: 100.70.115.1
|
||||
4. Port: 7890 (or 7892 for mixed)
|
||||
|
||||
#### Windows:
|
||||
1. Settings → Network & Internet → Proxy
|
||||
2. Manual proxy setup
|
||||
3. Address: 100.70.115.1
|
||||
4. Port: 7890
|
||||
|
||||
### For Mobile Apps (iOS/Android)
|
||||
|
||||
Most apps support HTTP/SOCKS5 proxy:
|
||||
- **Type:** HTTP or SOCKS5
|
||||
- **Host:** 100.70.115.1
|
||||
- **Port:** 7890 (HTTP) or 7891 (SOCKS5) or 7892 (Mixed)
|
||||
|
||||
## Testing the Connection
|
||||
|
||||
### Test HTTP Proxy:
|
||||
```bash
|
||||
curl -x http://100.70.115.1:7890 https://api.ipify.org
|
||||
```
|
||||
|
||||
### Test SOCKS5 Proxy:
|
||||
```bash
|
||||
curl --socks5 100.70.115.1:7891 https://api.ipify.org
|
||||
```
|
||||
|
||||
### Check if proxy is working:
|
||||
Visit http://100.70.115.1:9090/ui in your browser to see the Clash dashboard.
|
||||
|
||||
## Management Commands
|
||||
|
||||
### Check Status:
|
||||
```bash
|
||||
ssh server2 'sudo systemctl status clash-meta'
|
||||
```
|
||||
|
||||
### View Logs:
|
||||
```bash
|
||||
ssh server2 'sudo journalctl -u clash-meta -f'
|
||||
```
|
||||
|
||||
### Restart Service:
|
||||
```bash
|
||||
ssh server2 'sudo systemctl restart clash-meta'
|
||||
```
|
||||
|
||||
### Stop Service:
|
||||
```bash
|
||||
ssh server2 'sudo systemctl stop clash-meta'
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- All traffic routed through server2 will use server2's internet connection
|
||||
- The proxy is accessible only via Tailscale network (secure)
|
||||
- No authentication required (protected by Tailscale)
|
||||
- The proxy uses "direct" mode - all traffic goes directly through server2's connection
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user