One-click deployment of the ChatGPT private proxy, power by Next.js, support SSE!
English | 简体中文
This project is based on Next.js, use Rewriter to complete proxy function, only 2 lines of core code, combining Zeabur or Vercel can easily host your private proxy service
Before you start, you'd better check the How to use section to determine whether this project is applicable to you
ps: The SSE part of the code from chatgptProxyAPI
You must have a server and make sure your server can access ChatGPT
You need some knowledge about Docker
- Fork this repository for your own repository
-
Switch to the your forked project directory and run
docker build -t chatgpt-proxy .
-
then run
docker run --name chatgpt-proxy -d -p 8000:3000 chatgpt-proxy
-
open
http://127.0.0.1:8000
on your browser
If you don't use Docker, you can also manually deploy it
Steps for manually deploy
Your nodejs version needs to be greater than or equal to 14
$ git pull https://github.com/imyuanx/chatgpt-proxy
$ cd chatgpt-proxy
$ pnpm install
$ pnpm build
$ pnpm start
❗️
⚠️ ❗️Warning: This project may violate theNever Fair Use - Proxies and VPNs
entries under the Zeabur Terms of Use. Zeabur hosting this project is strongly not recommended!❗️
⚠️ ❗️Warning: If your account is punished due to the deployment of this project to Zeabur, please bear the consequences
Steps for deployment
❗️
⚠️ ❗️Assuming that you have completely read the warning information and understand the possible risks and consequences, you can still continue to complete the deployment
Specific operations are as follows
- Fork this repository for your own repository
![fork](https://raw.githubusercontent.com/chensihai/chatgpt-proxy/main/public/frok.png)
- Add a new service on Zeabur console
![step 1](https://raw.githubusercontent.com/chensihai/chatgpt-proxy/main/public/zeabur.png)
- Add service and deploy from source code
![step 2](https://raw.githubusercontent.com/chensihai/chatgpt-proxy/main/public/zeabur-1.png)
![step 2-1](https://raw.githubusercontent.com/chensihai/chatgpt-proxy/main/public/zeabur-1-1.png)
- Select your forked repo
![step 3](https://raw.githubusercontent.com/chensihai/chatgpt-proxy/main/public/zeabur-2.png)
- Select main and deploy
![step 4](https://raw.githubusercontent.com/chensihai/chatgpt-proxy/main/public/zeabur-3.png)
- After the deployment is successful, Generate the domain name.
![step 5](https://raw.githubusercontent.com/chensihai/chatgpt-proxy/main/public/zeabur-4.png)
- Finally get your service
![step 6](https://raw.githubusercontent.com/chensihai/chatgpt-proxy/main/public/zeabur-5.png)
❗️
⚠️ ❗️Warning: This project may violate the Never Fair Use - Proxies and VPNs entries under the Vercel Terms of Use. Vercel hosting this project is strongly not recommended!❗️
⚠️ ❗️Warning: If your account is punished due to the deployment of this project to Vercel, please bear the consequences
Steps for deployment
❗️
⚠️ ❗️Assuming that you have completely read the warning information and understand the possible risks and consequences, you can still continue to complete the deployment
If you use Vercel deploy services, you must custom domain name, beacuse the custom domain name is not affected by the GFW, Specific operations are as follows
- Click the deploy button at the top
![One-click deploy](https://raw.githubusercontent.com/chensihai/chatgpt-proxy/main/public/vercel.png)
- After deployment, the repository will be forked automatically for you, entering a custom repository name in the input field
![Deploy](https://raw.githubusercontent.com/chensihai/chatgpt-proxy/main/public/vercel-deploy.png)
- After successful deployment, get your service
![Alt text](https://raw.githubusercontent.com/chensihai/chatgpt-proxy/main/public/vercel-success.png)
- You must add a custom domain name for your service, otherwise you will not be able to access your service in the country
![Domain](https://raw.githubusercontent.com/chensihai/chatgpt-proxy/main/public/vercel-domain.png)
Whether you use Zeabur or Vercel, you will get the following proxy service after deployment
The resulting two addresses will be fully forwarded to https://api.openai.com
and both will be domestically accessible, where .../proxy-sse
supports SSE
You can use the proxy service in applications that support custom apis to invoke the "openai" interface domestically
Fro example, openai-translator: