更新 Discourse 后如何解决 502 Bad Gateway 问题？
[英]How to troubleshoot 502 Bad Gateway after updating Discourse?
问题描述
I just updated Discourse by running the following after the server being at sleep for a few months.
我刚刚通过在服务器休眠几个月后运行以下命令来更新 Discourse。
cd /var/discourse
git pull
./launcher rebuild app
Now, when I open my Discourse URL, I get a Nginx 502 Bad Gateway error.现在，当我打开我的 Discourse URL 时，我收到 Nginx 502 Bad Gateway 错误。
I know very little about Docker.我对 Docker 知之甚少。 How can I figure out what isn't working?我怎样才能弄清楚什么不起作用？
Thanks!谢谢！
1 个解决方案
解决方案1
0 已采纳 2020-07-06 14:24:49
Running ./launcher rebuild app again fixed the issue.再次运行./launcher rebuild app解决了这个问题。
声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.
相关问题
如何对 ECS Fargate 容器进行故障排除？ | “502 错误的 inte.net 网关” - How to troubleshoot ECS Fargate container? | "502 bad internet gateway"
一定时间后 traefik 502 坏网关 - traefik 502 bad gateway after a certain time
如何修复 nginx 中的 502 Bad Gateway 错误？ - How to fix 502 Bad Gateway error in nginx?
Traefik - 502 错误网关 - Traefik - 502 Bad Gateway
Nginx：在kubernetes集群中部署Redmine后出现502 Bad Gateway错误 - Nginx: 502 Bad Gateway error after deploying redmine in kubernetes cluster
初始加载后的 AWS Fargate 502 Bad Gateway - AWS Fargate 502 Bad Gateway after initial load
502错误的网关Docker + Laravel - 502 Bad Gateway Docker + Laravel
502 坏网关，header 大小 - 502 bad gateway, header size
Ngnix Django 502 网关坏 - Ngnix Django 502 Bad Gateway
Nginx 容器502坏网关 - Nginx container 502 Bad Gateway
相关标签