ikechan8370 / node-chatgpt-proxy Goto Github PK

a stable proxy solution of chat.openai.com which can bypass cloudflare with browser

License: Apache License 2.0

JavaScript 97.78% Dockerfile 2.19% Shell 0.03%

node-chatgpt-proxy's Introduction

node-chatgpt-proxy

A simple reverse proxy for chat.openai.com which can bypass cloudflare protection.

This project has been used by chatgpt-plugin for months, and huge improvements in performance and stability have been made to it.

Give me a star if this project helps or you are using any service supported by it.

How to use

with source code

todo

with docker

just run docker run -d -p [PORT]:3000 --name node-chatgpt-proxy --shm-size=1gb geyinchi/node-chatgpt-proxy

Check log: docker exec -it node-chatgpt-proxy tail -100f /var/log/node-chatgpt-proxy.log

Check new version and update: docker pull geyinchi/node-chatgpt-proxy && docker stop node-chatgpt-proxy && docker rm node-chatgpt-proxy && docker run -d -p [PORT ]:3000 --name node-chatgpt-proxy --shm-size=1gb geyinchi/node-chatgpt-proxy

中文

一个简单的chat.openai.com的反代，基于浏览器绕过Cloudflare防护。

本项目目前用于chatgpt-plugin插件，经中等规模用户长期使用，稳定性不错。

如果这个项目对你有帮助或者你就在使用基于这个项目的其他开源项目，请给我一个免费的Star，谢谢！

如何使用

源码部署

TODO

使用docker

直接运行 docker run -d -p [PORT]:3000 --name node-chatgpt-proxy --shm-size=1gb geyinchi/node-chatgpt-proxy

查看日志: docker exec -it node-chatgpt-proxy tail -100f /var/log/node-chatgpt-proxy.log

检查新版本并更新: docker pull geyinchi/node-chatgpt-proxy && docker stop node-chatgpt-proxy && docker rm node-chatgpt-proxy && docker run -d -p [端口号]:3000 --name node-chatgpt-proxy --shm-size=1gb geyinchi/node-chatgpt-proxy

可以参考这篇博客：https://ikechan8370.com/archives/da-jian-chatgpt-guan-fang-fan-xiang-dai-li

node-chatgpt-proxy's People

Contributors

Stargazers

Watchers

Forkers

sixicat expcat angusvencent angusvencentgg utopialee yjw8336 csj8520 super-hong lyhiving csvproject qq821181867 fshebe233 2521245392

node-chatgpt-proxy's Issues

程序无法正常运行起来

通过docker运行你的镜像后，一直反复重启proxy进程，定位了一下，是在this.browser = await puppeteer.launch(this.config)执行后就崩了，catch捕捉不到

> % docker exec -it node-chatgpt-proxy tail -f /var/log/node-chatgpt-proxy.log

init chatgpt browser
node-chatgpt-proxy listening on port 3000
chatgpt puppeteer 启动中...

> [email protected] start
> node src/main.js

init chatgpt browser
node-chatgpt-proxy listening on port 3000
chatgpt puppeteer 启动中...

> [email protected] start
> node src/main.js

init chatgpt browser
node-chatgpt-proxy listening on port 3000
chatgpt puppeteer 启动中...

> [email protected] start
> node src/main.js

init chatgpt browser
node-chatgpt-proxy listening on port 3000
chatgpt puppeteer 启动中...

2023-04-04 14:03:26,438 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2023-04-04 14:03:26,443 INFO supervisord started with pid 1
2023-04-04 14:03:27,472 INFO spawned: 'xvfb' with pid 9
2023-04-04 14:03:27,487 INFO spawned: 'proxy' with pid 11
2023-04-04 14:03:28,497 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-04 14:03:28,498 INFO success: proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-04 14:03:34,252 INFO exited: proxy (exit status 1; not expected)
2023-04-04 14:03:34,252 INFO reaped unknown pid 85 (exit status 0)
2023-04-04 14:03:34,252 INFO reaped unknown pid 90 (exit status 0)
2023-04-04 14:03:34,252 INFO reaped unknown pid 76 (exit status 0)
2023-04-04 14:03:34,253 INFO reaped unknown pid 78 (exit status 0)
2023-04-04 14:03:35,267 INFO spawned: 'proxy' with pid 105
2023-04-04 14:03:36,272 INFO success: proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-04 14:03:41,546 INFO exited: proxy (exit status 1; not expected)
2023-04-04 14:03:41,546 INFO reaped unknown pid 157 (exit status 0)
2023-04-04 14:03:41,546 INFO reaped unknown pid 162 (exit status 0)
2023-04-04 14:03:41,546 INFO reaped unknown pid 148 (exit status 0)
2023-04-04 14:03:41,547 INFO reaped unknown pid 150 (exit status 0)
2023-04-04 14:03:42,561 INFO spawned: 'proxy' with pid 177
2023-04-04 14:03:43,566 INFO success: proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-04 14:03:49,076 INFO exited: proxy (exit status 1; not expected)
2023-04-04 14:03:49,077 INFO reaped unknown pid 229 (exit status 0)
2023-04-04 14:03:49,077 INFO reaped unknown pid 234 (exit status 0)
2023-04-04 14:03:49,077 INFO reaped unknown pid 220 (exit status 0)
2023-04-04 14:03:49,077 INFO reaped unknown pid 222 (exit status 0)
2023-04-04 14:03:50,092 INFO spawned: 'proxy' with pid 249
2023-04-04 14:03:51,097 INFO success: proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-04-04 14:03:56,542 INFO exited: proxy (exit status 1; not expected)