# 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:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![bkuntz](https://avatars.discourse-cdn.com/v4/letter/b/d78d45/32.png) [@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")

</div>

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

---

_[View the full topic](https://meta.discourse.org/t/discourse-admin-not-accessible-3-3-0beta4/318888)._