# The Git Hang and the Admin/Mod user Accs Oops Error Page Error

**URL:** <https://meta.discourse.org/t/the-git-hang-and-the-admin-mod-user-accs-oops-error-page-error/413475>\
**Category:** Self-hosting\
**Tags:** login, bug\
**Created:** [September 28, 2026, 1:24pm UTC](https://meta.discourse.org/t/the-git-hang-and-the-admin-mod-user-accs-oops-error-page-error/413475 "2026-09-28T13:24:02Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)\
**Post date:** [October 1, 2026, 3:27pm UTC](https://meta.discourse.org/t/the-git-hang-and-the-admin-mod-user-accs-oops-error-page-error/413475/11 "2026-10-01T15:27:21Z")

</div>

Kind of looks like something to do with presenting the upcoming changes - that’s something only admins would see. According to [ask.discourse.com](http://ask.discourse.com)

> The entire feature is controlled by a **hidden** site setting called `enable_upcoming_changes`, set to `false` in a Rails console:
> 
> ```ini
> SiteSetting.enable_upcoming_changes = false
> 
> ```
> 
> However, this requires terminal/server access, so it’s only doable on **self-hosted** installs.

---

_[View the full topic](https://meta.discourse.org/t/the-git-hang-and-the-admin-mod-user-accs-oops-error-page-error/413475)._