I have a real issue with many of my users. The users can be seen in admin panel like this: [Screenshot from 2019-12-12 20-00-31] But when I try to reveal their email address, It wont show anything to me. And also their public profile gives a 404 error. As far as I see, all of these users are alm…

Another thing I notice: If I inactivate, and then activate them, they get fixed!

If a user is inactive for a certain length of time (730 days by default) they are automatically inactivated. The setting is in your dashboard under Settings/Users and scroll almost down to the bottom. That is where you’ll see that. But, it’s not necessary to make any changes for the sake of making a…

No. My problem is not this. The dashboard says the users are activated.

Seems similar to the issue I’m having . Could you check if the affected names have duplicates or ‘very near matches’ in your database? For example user.user and useruser.

Yes affected users are among those usernames that are very popular. so discourse suggest a near match username. I signup users with api. so I get a username from user. then I check it against discourse api and if its already taken, I would automatically use whatever discourse suggest.

btw with help of @RGJ we nailed the problem down to this two condisions: [이미지] On another topic there are two different problems: users that cannot be found by username but can be found by id (like mojtaba11) users that cannot be found by username_lower but can be found by username (like alire…

To add to that, the issue @hosna is having is clearly an issue on the database level. It seems like there is some corruption in the users table. Copying the contents to a new table solves these issues. That said, I did see two occurrences of @bartv ’s issue in @hosna ’s database (those were the two d…

Sounds like a corrupt database index. REINDEX TABLE users should solve the problem.

What about the duplicate usernames? I have many same usernames being used for 2 distinct users. The issue is acknowledged here: [이미지] Critical Error: changed username, user got broken Support That’s an interesting observation! Usernames are effectively …

That’s probably a side effect of a corrupt index. You might need to clean that up manually before the reindexing works.

손상된 데이터베이스로 인해 많은 사용자의 계정이 손상되었습니다

지원

hosna (hosna) 12월 14, 2019, 2:39오후 10

What about the duplicate usernames? I have many same usernames being used for 2 distinct users.

The issue is acknowledged here:

글		댓글	조회수
Critical Error: changed username, user got broken Support	18	1913	3월 15, 2020
Upgrade issue with duplicate username in DB Self-hosting	2	525	1월 29, 2021
2.7.0.beta2 upgrade failed with ERROR: duplicate key Self-hosting	24	2444	1월 26, 2021
Duplicate 'Names' Support	10	825	3월 8, 2020
Username already exist error Self-hosting	3	1195	12월 11, 2019

손상된 데이터베이스로 인해 많은 사용자의 계정이 손상되었습니다

Related topics