# Discourse Admin not accessible (3.3.0beta4)
**URL:** https://meta.discourse.org/t/discourse-admin-not-accessible-3-3-0beta4/318888
**Category:** Self-hosting
**Created:** [July 28, 2024, 6:40pm UTC](https://meta.discourse.org/t/discourse-admin-not-accessible-3-3-0beta4/318888 "2024-07-28T18:40:41Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@bkuntz](https://meta.discourse.org/u/bkuntz)
#### Post date: [July 28, 2024, 6:40pm UTC](https://meta.discourse.org/t/discourse-admin-not-accessible-3-3-0beta4/318888/1 "2024-07-28T18:40:41Z")
Dear all,
Similar to this old post, I’m not able to access any admin function anymore.
> [@Discourse Admin function not accessible, suddenly](https://meta.discourse.org/t/discourse-admin-function-not-accessible-suddenly/139197):
>
> Just today, I am unable to click on the sandwich menu in the top-right corner of our discourse forum page, where you typically access the admin functions. I click it and nothing happens. When I try to enter the admin area via /admin, I get this: I’ve always been able to access this area fine, up until today. I’ve tried it in two different browsers. My first response would be to see if I need an update…but I can’t get there! Any help is appreciated.
Yesterday evening I did a rebuild to upgrade from 3.2.0 to 3.3.0beta4, everything went fine. After the rebuild everything was alright also on /admin.
Suddenly today neither me nor another admin can access it.
Section /about, is OK and all other moderating tools are available for us.
I did a new rebuild, no error either but still not working.
Logs are also not showing anything wrong.
```plaintext
./launcher logs app
x86_64 arch detected.
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 41
ok: run: redis: (pid 52) 0s
ok: run: postgres: (pid 50) 0s
supervisor pid: 54 unicorn pid: 82
```
If someone has an idea I would be very gladful
Thanks
---
### Author:  [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [July 28, 2024, 6:41pm UTC](https://meta.discourse.org/t/discourse-admin-not-accessible-3-3-0beta4/318888/2 "2024-07-28T18:41:41Z")
> [@Resolving "SyntaxError: Unexpected identifier #..." caused by Cloudflare Auto Minify](https://meta.discourse.org/t/resolving-syntaxerror-unexpected-identifier-caused-by-cloudflare-auto-minify/311390):
>
> Cloudflare’s [‘Auto Minify’](https://developers.cloudflare.com/speed/optimization/content/auto-minify/) feature will break recent versions of Discourse. In the browser console, you will see an error like: Uncaught SyntaxError: Unexpected identifier '#...' Cloudflare are aware of the issue, and have added this message to their dashboard: Note: Please note that this feature may not be fully compatible with certain newer CSS and JS language features, which could potentially affect the functionality of the site Unfortunately, despite this critical issue, the feature wi…
---
### Author:  [@bkuntz](https://meta.discourse.org/u/bkuntz)
#### Post date: [July 28, 2024, 6:46pm UTC](https://meta.discourse.org/t/discourse-admin-not-accessible-3-3-0beta4/318888/3 "2024-07-28T18:46:02Z")
Thanks a lot
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [August 27, 2024, 6:46pm UTC](https://meta.discourse.org/t/discourse-admin-not-accessible-3-3-0beta4/318888/4 "2024-08-27T18:46:34Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.