升级到 discourse 3 后..只能通过安全模式访问管理员

[albjeremias (Albatroz Jeremias)]

当前行为：
当我点击右上角的汉堡菜单时，我期望看到一个菜单，但什么也没有出现。并且我在控制台中看到这个：

预期行为：
我期望点击汉堡菜单，然后看到访问管理面板的菜单。

解决方法：
使用安全模式，如以下链接所述：

Using Safe Mode to troubleshoot issues with themes and plugins

This guide explains how to use Discourse’s Safe Mode to troubleshoot issues with themes and plugins. Required user level: All users Discourse offers a “JavaScript Safe Mode” that allows any user to isolate the root cause of JavaScript issues caused by plugins, themes, or theme components. This feature is particularly useful for troubleshooting problems on your Discourse site. Accessing Safe Mode To access Safe Mode, follow these steps: Open a new browse…

可能相关的问题：

Admin Plugin page is blank - Error: There is no route named adminPlugins.index

The fix worked for me, as well! Thanks @vinothkannans !

[albjeremias (Albatroz Jeremias)]

我的插件列表，我将禁用它们所有

[albjeremias (Albatroz Jeremias)]

是否有办法禁用所有插件和主题？我是指作为系统管理员手动禁用。

[Falco]

从 app.yml 中移除插件并重新构建。

[pfaffman (Jay Pfaffman)]

乍一看，我会删除反驳，但我怀疑您的问题出在主题上。只需使用安全模式并在一个浏览器中禁用所有主题组件，然后在另一个浏览器中重新添加它们。

[albjeremias (Albatroz Jeremias)]

这可能与之相关.. How-to disable or tune rate limiting by ip address?
另外，我该如何查看日志？

./launcher logs app

是这个吗？

[albjeremias (Albatroz Jeremias)]

我禁用了所有插件……但仍然看到很多这样的屏幕：

How-to disable or tune rate limiting by ip address?

I have multiple users sharing the same ip address using my discourse instance, how do I tune the rate limiting on the new discourse 3? i dont think this has very good default values, they seem to low. i didn’t get this problem with the previous version [image] [image] [image]

b25f381c69c708

2:~/discourse_docker_active$ ./launcher logs app

x86_64 arch detected.

WARNING: containers/app.yml file is world-readable. You can secure this file by running: chmo

d o-rwx containers/app.yml

run-parts: executing /etc/runit/1.d/00-ensure-links

run-parts: executing /etc/runit/1.d/00-fix-var-logs

run-parts: executing /etc/runit/1.d/01-cleanup-web-pids

run-parts: executing /etc/runit/1.d/anacron

run-parts: executing /etc/runit/1.d/cleanup-pids

Cleaning stale PID files

run-parts: executing /etc/runit/1.d/copy-env

Started runsvdir, PID is 40

warning: redis: unable to open supervise/ok: file does not exist

ok: run: redis: (pid 54) 1s

ok: run: postgres: (pid 56) 1s

supervisor pid: 78 unicorn pid: 82

[Stephen]

您可能会遇到很多导致速率限制问题的原因。

最主要的原因是使用了类似 Cloudflare 的服务，但没有使用 Cloudflare 模板。这样做会导致您的服务器认为您的所有用户都来自一两个 IP 地址。

请告诉我们您的设置，我们可以帮助您排查问题——对他人有效的方法可能不适用于您的特定配置。

[albjeremias (Albatroz Jeremias)]

好吧，我确定这与这次升级有关。现在我全新安装了 3.0 并使用了备份。现在看起来好多了。

你可以提出更具体的问题，但不要问我的网关、负载均衡器之类的东西。我使用 docker-compose 来运行大量的开源项目，而 discourse 总是很痛苦，因为你们重新发明了轮子。谢谢你。

顺便说一句……我该如何查看日志文件？拜托。

[Stephen]

如果您不想讨论可能导致问题的环境方面，并且没有使用受支持的跟踪来安装 Discourse，我将将其标记为 unsupported-install 并保留在那里。

[albjeremias (Albatroz Jeremias)]

随你便。你是仁慈的独裁者。但你能指导我如何查看日志文件吗？谢谢。

[albjeremias (Albatroz Jeremias)]

抱歉，我有点神经多样性。我无意冒犯。

[Stephen]

这里有一个很好的主题，解释了在哪里可以找到大部分内容：

Where does Discourse store and show logs?

When troubleshooting issues or errors with Discourse it is important you look at your logs. Here’s a listing of where they are and what’s in there. Your site domain Administration logs shown in the UI The Discourse admin panel contains several forms of logging: Emails that are sent, skipped, bounced, received and rejected are logged at https://=DOMAIN=/admin/email/sent and the neighboring tabs. Staff actions are logged at https://=DOMAIN=/admin/logs/staff_action_logs Email addresses and …

[albjeremias (Albatroz Jeremias)]

此指南可以指导我们吗？

2023/02/23 17:10:30 [error] 60#60: *310 limiting requests, excess: 12.448 by zone "flood", client: 172.17.0.1, server: _, request: "POST /mini-profiler-resources/results HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/"
2023/02/23 17:10:30 [error] 60#60: *311 limiting requests, excess: 12.448 by zone "flood", client: 172.17.0.1, server: _, request: "POST /mini-profiler-resources/results HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/"
2023/02/23 17:10:30 [error] 60#60: *312 limiting requests, excess: 12.436 by zone "flood", client: 172.17.0.1, server: _, request: "POST /mini-profiler-resources/results HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/"
2023/02/23 17:10:30 [error] 61#61: *309 limiting requests, excess: 12.460 by zone "flood", client: 172.17.0.1, server: _, request: "POST /mini-profiler-resources/results HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/"
2023/02/23 17:10:35 [error] 60#60: *344 limiting requests, excess: 12.352 by zone "flood", client: 172.17.0.1, server: _, request: "POST /mini-profiler-resources/results HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/"
2023/02/23 17:10:35 [error] 60#60: *346 limiting requests, excess: 12.340 by zone "flood", client: 172.17.0.1, server: _, request: "POST /mini-profiler-resources/results HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/"
2023/02/23 17:10:35 [error] 60#60: *348 limiting requests, excess: 12.340 by zone "flood", client: 172.17.0.1, server: _, request: "POST /mini-profiler-resources/results HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/"
2023/02/23 17:10:35 [error] 61#61: *342 limiting requests, excess: 12.340 by zone "flood", client: 172.17.0.1, server: _, request: "POST /mini-profiler-resources/results HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/"
2023/02/23 17:13:18 [error] 60#60: *466 limiting requests, excess: 12.904 by zone "flood", client: 172.17.0.1, server: _, request: "GET /brotli_asset/browser-update-331e86c77ddeff594308c27802669aeffae5f4ffddf9565a44e67d119278ae51.js HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/admin/site_settings/category/all_results?filter=allow_restore"
2023/02/23 17:13:18 [error] 60#60: *468 limiting requests, excess: 12.904 by zone "flood", client: 172.17.0.1, server: _, request: "GET /brotli_asset/plugins/discourse-details-4cc313dcbef7c2a43d82c8d9cd301ad2bedc79dcb8f31645e1dd0a8b626ba7f3.js HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/admin/site_settings/category/all_results?filter=allow_restore"
2023/02/23 17:13:24 [error] 61#61: *531 limiting requests, excess: 12.388 by zone "flood", client: 172.17.0.1, server: _, request: "POST /mini-profiler-resources/results HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/admin/site_settings/category/all_results?filter=allow_restore"
2023/02/23 17:13:24 [error] 61#61: *533 limiting requests, excess: 12.376 by zone "flood", client: 172.17.0.1, server: _, request: "POST /mini-profiler-resources/results HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/admin/site_settings/category/all_results?filter=allow_restore"
2023/02/23 17:13:24 [error] 61#61: *534 limiting requests, excess: 12.376 by zone "flood", client: 172.17.0.1, server: _, request: "POST /mini-profiler-resources/results HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/admin/site_settings/category/all_results?filter=allow_restore"
2023/02/23 17:13:24 [error] 60#60: *523 limiting requests, excess: 12.364 by zone "flood", client: 172.17.0.1, server: _, request: "POST /mini-profiler-resources/results HTTP/1.1", host: "forum.DOMAINNAME", referrer: "https://forum.DOMAINNAME/admin/site_settings/category/all_results?filter=allow_restore"

[Stephen]

在 discourse 中，您和您的用户似乎来自哪个 IP 地址？请通过 /admin 查看几位用户。

[albjeremias (Albatroz Jeremias)]

这个时段没有任何活动，只有我一个人。人们的使用非常随意，大部分在一天结束时使用。

[Stephen]

用户帐户上的最后一个 IP 地址即使没有当前活动也可以显示。

[Stephen]

通过 /admin/users 打开几个用户，并比较“上次 IP 地址”。

[albjeremias (Albatroz Jeremias)]

您知道 XY 问题吗？XY problem - Wikipedia
我不明白您想要什么或需要什么。我需要了解 discourse 为什么会进行速率限制，我已经给了您日志文件……接下来我该怎么办？是什么代码触发了它？

[albjeremias (Albatroz Jeremias)]

不知怎么地，问题好像解决了……我猜可能是上次升级不彻底留下的问题吧？我也不知道。现在一切看起来都正常了。

全新安装，然后在恢复模式下加载那个 zip 文件就好了。

感谢你们的支持和耐心。
也感谢这个很棒的软件