-
Notifications
You must be signed in to change notification settings - Fork 448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
最新版报错服务器502 #170
Comments
估计 mongodb 的版本有关系 |
原来使用的是mongo:3.6,改成mongo最新版后,重新部署,仍然这样 |
新版本应该使用mongodb的哪个版本? |
5.x 试试看,,我是 docker 部署的 所以直接就是 docker lastest 了 |
旧版本都是用这个docker compose部署的,今天试2.13.2就出现这个问题了 |
又仔细看了下最初的报错,第一个 f12 看下是什么错误 打开首页,看是哪个接口错误,然后 再提供一下 docker log 日志,我发现你最初的报错日志只是Warning 并不是 error 所以肯定是别的报错,找下 error 的报错看看 |
docker日志的话,只有下面这样的
Server is running on port 3002 |
那你浏览器f12 打开首页看看呢,,这个看不出啥 |
我将原来的image: kerwin1202/chatgpt-web:v2.13.2
改了其中的主机端口就好了,改成了-3011:3002 ,就好了,但是就很好奇这个问题 感谢大佬了 |
那你怕是这个端口占用了,所以导致没启动起来 可以 |
没有,我又改回原来的3010,但是换了个二级域名去解析就好了,我再研究研究哪的问题 |
嗯,我刚试了换edge浏览器就正常了,只要是以前打开过的浏览器都会出现这个页面,电脑谷歌浏览器,手机的小米浏览器和谷歌浏览器都还是会出现,还试了wifi和流量,也是会出现,目前结论就是,打开过旧版本的浏览器都会出现这个现象 |
server: cloudflare 估计是套了cf 缓存了 重定向的 302 之类的 ctrl + f5 刷新下就可以了 |
非常感谢 |
最新版,使用docker compose,报错如图;
我使用的上个版本是旧版2.12.9,没有这样的问题
报错,日志如下
Server is running on port 3002
(node:36) [MONGODB DRIVER] Warning: cursor.count is deprecated and will be removed in the next major version, please use
collection.estimatedDocumentCount
orcollection.countDocuments
instead(Use
node --trace-warnings ...
to show where the warning was created)ELIFECYCLE Command failed with exit code 143.
Server is running on port 3002
(node:36) [MONGODB DRIVER] Warning: cursor.count is deprecated and will be removed in the next major version, please use
collection.estimatedDocumentCount
orcollection.countDocuments
instead(Use
node --trace-warnings ...
to show where the warning was created)ELIFECYCLE Command failed with exit code 143.
Server is running on port 3002
(node:37) [MONGODB DRIVER] Warning: cursor.count is deprecated and will be removed in the next major version, please use
collection.estimatedDocumentCount
orcollection.countDocuments
instead(Use
node --trace-warnings ...
to show where the warning was created)The text was updated successfully, but these errors were encountered: