# 管理员登出用户后出现内部服务器错误

**URL:** <https://meta.discourse.org/t/internal-server-error-after-user-is-logged-out-by-admin/79686>\
**Category:** Bug\
**Created:** [2018年二月3日 00:15 UTC](https://meta.discourse.org/t/internal-server-error-after-user-is-logged-out-by-admin/79686 "2018-02-03T00:15:24Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2018年二月3日 00:58 UTC](https://meta.discourse.org/t/internal-server-error-after-user-is-logged-out-by-admin/79686/6 "2018-02-03T00:58:15Z")

</div>

My flooding fix is definitely in 1.9 stable, have not seen notifications flood anywhere on our hosted sites recently.

That said the correct fix for the various oddities is:

> [@Better detection of "cookies deleted" in the application](https://meta.discourse.org/t/better-detection-of-cookies-deleted-in-the-application/78800):
>
> Occasionally users may delete all cookies or in self hosted situations (which do not have auth token set via env) junk redis. When this happens behaviour is kind of odd. It looks like you are logged in: If you are browsing a secure topic, you only see placeholders: Depending on the site you are on (requires login or not) you will start seeing lots of 302s or 403s Instead: If we detect a user is somehow no longer logged in, we should open a modal saying “looks like you w…

This will happen for 2.0, probably in the next month.

---

_[View the full topic](https://meta.discourse.org/t/internal-server-error-after-user-is-logged-out-by-admin/79686)._