After upgrading to discourse 3.. can only access to admin using safe-mode

[albjeremias (Albatroz Jeremias)]

Current Behavior:
When i go to the hamburguer menu on the top right, i expect to click and see a menu, instead nothing comes. and i get this on my console

Expected behavior:
I expect to click the hambuger menu, and see the menus to access to the admin panels

Work around:
use safe mode as explained in:

Use Safe Mode to troubleshoot issues with themes and plugins

Discourse has a “JavaScript Safe Mode”, where any user can use to isolate the root cause of a JavaScript issue caused by plugins, themes or theme components. To access safe mode go to: http://your-site-name/safe-mode for example this is the safe mode for our demo site: https://try.discourse.org/safe-mode [safe mode options] [safe mode is enabled] To exit safe mode simply close your browser tab When entering safe mode you can select between: Disable all themes and theme-components …

Issues that might be related:

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)]

my plugin list, ill disable them all

[albjeremias (Albatroz Jeremias)]

is there a way to disable all plugins and themes? manually as sysadmin i mean.

[Falco]

Remove plugins from the app.yml and rebuild.

[pfaffman (Jay Pfaffman)]

From a quick glance, I’d remove retort, but I suspect your problem is with a theme. JUst use safe-mode and disable all of your theme components in one browser and add them back in another.

[albjeremias (Albatroz Jeremias)]

I think this might be related… How-to disable or tune rate limiting by ip address?
anyway how can i see the logs?

./launcher logs app

is it this?

[albjeremias (Albatroz Jeremias)]

I disabled all plugins… and still get a lots of this screens:

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]

There are lots of reasons you might see rate limit issues.

The top culprit is using something like Cloudflare without the Cloudflare template. Doing so means that your server things all of your users originate from one or two IPs.

Tell us about your setup and we can help troubleshoot - what worked for others may not work for your specific configuration.

[albjeremias (Albatroz Jeremias)]

well, im sure it was about this upgrade. Now I installed 3.0 fresh and used a backup. looks better now.

you can make more specific questions, but not about my gateways, load balancer ninja stuff. i use docker-compose for loads of open source projects, and discourse is always painful, cause you guys revinvented the wheel. thank u for that.

btw… how do you see logfiles? please.

[Stephen]

If you don’t want to discuss aspects of your environment which might be contributing to the issue and aren’t using the supported track to install Discourse I’ll flag this as unsupported-install and leave it there.

[albjeremias (Albatroz Jeremias)]

do whatever u want. u are the good dictator. but can you please guide me how to see logfiles? thank u

[albjeremias (Albatroz Jeremias)]

sorry im a bit neurodivergent. i dont mean to be rude.

[Stephen]

There’s a good topic here explaining where you can find most everything:

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)]

can this guide us?

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]

What IP address do you and your users appear to originate from within discourse? Take a look at a few users through /admin

[albjeremias (Albatroz Jeremias)]

there is no activity at this hour, only me. people use it very spontaneously mostly at the end of the day

[Stephen]

There doesn’t need to be current activity for the last IP address on user accounts to be visible.

[Stephen]

Open a couple of users via /admin/users and compare Last IP Address

[albjeremias (Albatroz Jeremias)]

do you known the XY problem? XY problem - Wikipedia
I don’t understand what you want, or need. I need to understand why discourse is rate limitting and I gave you logfiles… where can I go from there? what piece of code is triggerin that?

[albjeremias (Albatroz Jeremias)]

i think it solved magically somehow… i guess maybe it was still an issue from the not clean upgrade? i dunno. now everything seems find.

fresh install and load that zip in recovery worked.

thanks for the support and patience.
and for this cool software