Skip to content
This repository has been archived by the owner on Mar 20, 2024. It is now read-only.

selenium error: panic, need to create a new session and refresh #33

Closed
hncboy opened this issue Apr 17, 2023 · 15 comments
Closed

selenium error: panic, need to create a new session and refresh #33

hncboy opened this issue Apr 17, 2023 · 15 comments

Comments

@hncboy
Copy link

hncboy commented Apr 17, 2023

railway 部署
image

@sam-hieken
Copy link

遇到同样的问题 I have the same problem

@linweiyuan
Copy link
Owner

go-chatgpt-apichatgpt-proxy-server 缺一不可,两个都要部署并保证都在运行

proxyapi,有依赖

没用过 railway,可以把 compose.yamlChatGPT 转成 docker 命令


不保证稳定运行,不行的话,重启 api

@chijiao
Copy link

chijiao commented Apr 18, 2023

同样的问题

@Haibersut
Copy link

看看issue #22

@linweiyuan
Copy link
Owner

需要贴下启动配置看有没有错,另外网络要正常访问 ChatGPT 或者 Cloudflare

@linweiyuan linweiyuan added the question Further information is requested label Apr 19, 2023
@HasakyZoro
Copy link

本地docker部署同样问题,proxy-server正常运行

@linweiyuan
Copy link
Owner

"selenium error: panic, need to create a new session and refresh"

还有这个错误提示?需要拉下镜像

@HasakyZoro
Copy link

"selenium error: panic, need to create a new session and refresh"

还有这个错误提示?需要拉下镜像

删除重拉了还是这个报错

@linweiyuan
Copy link
Owner

拉了个假镜像,我把这个日志都删除了

@linweiyuan
Copy link
Owner

看看你删除和拉新镜像的命令

@linweiyuan
Copy link
Owner

chatgpt-proxy-server 这个也可以拉下,我加了日志

@HasakyZoro
Copy link

err
我设备是NAS,在docker界面操作删除后,用dockerhub界面的命令重新拉的,现在还是这个报错

@linweiyuan
Copy link
Owner

chatgpt-proxy-server 和 go-chatgpt-api 如果是最新的话,看下 chatgpt-proxy-server 的日志

先启动 proxy,再启动 api

或者可以的话找个时间可以给我远程看下,比如 todesk,不会收费的

@HasakyZoro
Copy link

chatgpt-proxy-server的日志是正常的
proxy-server-log

@linweiyuan
Copy link
Owner

确定是最新的镜像吗,chatgpt-proxy-server,昨晚我修改了下启动命令开启了啰嗦模式重新打了个包推了上去,启动应该有很多输出才对,不会这样一句话不说

第六感是打开方式不对

@linweiyuan linweiyuan removed the question Further information is requested label Apr 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants