mirror of
https://github.com/masterking32/MasterHttpRelayVPN.git
synced 2026-05-17 21:24:37 +03:00
Refactor setup instructions in GETTING_STARTED.md for clarity and update LAN_SHARING.md with additional details on proxy addresses and CA certificate installation
This commit is contained in:
@@ -13,20 +13,18 @@ This guide keeps only the setup path most users need. Follow it once, then come
|
|||||||
|
|
||||||
Choose whichever option works on your network.
|
Choose whichever option works on your network.
|
||||||
|
|
||||||
**Option A: Git**
|
**Option A: ZIP**
|
||||||
|
|
||||||
|
[Click to Download](https://github.com/masterking32/MasterHttpRelayVPN/archive/refs/heads/python_testing.zip)
|
||||||
|
|
||||||
|
|
||||||
|
**Option B: Git**
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
git clone https://github.com/masterking32/MasterHttpRelayVPN.git
|
git clone https://github.com/masterking32/MasterHttpRelayVPN.git
|
||||||
cd MasterHttpRelayVPN
|
cd MasterHttpRelayVPN
|
||||||
```
|
```
|
||||||
|
|
||||||
**Option B: ZIP**
|
|
||||||
|
|
||||||
1. Open [the GitHub repository](https://github.com/masterking32/MasterHttpRelayVPN).
|
|
||||||
2. Click **Code** -> **Download ZIP**.
|
|
||||||
3. Extract the ZIP file.
|
|
||||||
4. Open a terminal inside the extracted `MasterHttpRelayVPN` folder.
|
|
||||||
|
|
||||||
## 2. Deploy The Google Relay
|
## 2. Deploy The Google Relay
|
||||||
|
|
||||||
The relay is the small Apps Script program that fetches websites for you.
|
The relay is the small Apps Script program that fetches websites for you.
|
||||||
@@ -97,7 +95,7 @@ Chrome and Edge use the system proxy on Windows. You can also use extensions suc
|
|||||||
|
|
||||||
HTTPS browsing needs the local CA certificate generated by the proxy. The file is created at `ca/ca.crt` after first run.
|
HTTPS browsing needs the local CA certificate generated by the proxy. The file is created at `ca/ca.crt` after first run.
|
||||||
|
|
||||||
The app tries to install it automatically. If it cannot, install it manually:
|
**The app tries to install it automatically. If it cannot, install it manually:**
|
||||||
|
|
||||||
**Windows**
|
**Windows**
|
||||||
|
|
||||||
|
|||||||
+6
-3
@@ -18,7 +18,10 @@ Set this in `config.json`:
|
|||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
Restart the proxy. The startup log prints LAN addresses other devices can use.
|
Restart the proxy. The startup log prints LAN addresses other devices can use. it would be something like `192.168.x.x` or `10.x.x.x`.
|
||||||
|
|
||||||
|
in terminal you would see a message like `CA certificate download : http://192.168.xxxxxx/ca.crt` in a green color, on the other devide open this URL in browser to download the CA certificate and install it there as well.
|
||||||
|
|
||||||
|
|
||||||
## Configure Other Devices
|
## Configure Other Devices
|
||||||
|
|
||||||
@@ -30,12 +33,12 @@ On the other device, set the HTTP proxy to:
|
|||||||
| Port | `8085` |
|
| Port | `8085` |
|
||||||
| Type | HTTP |
|
| Type | HTTP |
|
||||||
|
|
||||||
If the other device browses HTTPS websites, it also needs to trust the CA certificate from `ca/ca.crt`.
|
Or you can create V2ray connection as HTTP or Socks5 protocol.
|
||||||
|
|
||||||
## Safety Checklist
|
## Safety Checklist
|
||||||
|
|
||||||
- Use this only on networks you trust.
|
- Use this only on networks you trust.
|
||||||
- Turn it off when you do not need it.
|
- Turn it off when you do not need it.
|
||||||
- Keep `auth_key` private.
|
- Keep `auth_key` private.
|
||||||
- Never share the `ca/` folder.
|
- Never share the `ca/` folder with random users.
|
||||||
- Prefer `127.0.0.1` for normal single-computer use.
|
- Prefer `127.0.0.1` for normal single-computer use.
|
||||||
|
|||||||
Reference in New Issue
Block a user