# カテゴリ通知状態の重複値によりユーザーがサインアップできない

**URL:** https://meta.discourse.org/t/user-cannot-signup-due-to-duplicate-values-in-category-notification-states/127444
**Category:** Self-hosting
**Created:** [2019 年 9 月 2 日午後 10:22 UTC](https://meta.discourse.org/t/user-cannot-signup-due-to-duplicate-values-in-category-notification-states/127444 "2019-09-02T22:22:16Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2019 年 9 月 2 日午後 10:24 UTC](https://meta.discourse.org/t/user-cannot-signup-due-to-duplicate-values-in-category-notification-states/127444/2 "2019-09-02T22:24:30Z")

</div>

これに関連する別の報告があります：

> [@Discourse DB Error When Creating New Users via SSO Login](https://meta.discourse.org/t/discourse-db-error-when-creating-new-users-via-sso-login/127442):
>
> Summary Discourse DB constraint error because of duplicate key values generated when users without an account attempt to log in via SSO. Causes internal server error (500) to be seen via external proxy. Discussion On August 28th or 29th, I updated Discourse to the latest beta (v2.4.0.beta2) along with all the installed Discourse plug-ins. Around the same time, I also updated [SeAT](https://github.com/eveseat/seat), and reconfigured Discourse to use a UNIX socket, which the external Apache can proxy/reverse proxy to. Prior to tha…

@sam さん、何かお手伝いできることはありますか？

---

_[View the full topic](https://meta.discourse.org/t/user-cannot-signup-due-to-duplicate-values-in-category-notification-states/127444)._