Description When fetching active users with the API some pages of `/admin/users/list/active.json` return a HTTP 500. Workaround If the problematic pages are skipped the other pages can be fetched without problem. Error The server error that caused the HTTP 500: ```ruby NoMethodError: undefined method ‘[]’ for nil (NoMethodError) main_user_record\[:silenced_till\] ^^^^^^^^^^^^^^^^ from app/models/user.rb:1335:in `silenced_till’ from active_record/attribute_methods/query.rb:48:in `public_send’ from active_record/attribute_methods/query.rb:48:in `query_attribute’ from active_model/attribute_methods.rb:273:in `silenced_till?’ from app/serializers/admin_user_list_serializer.rb:51:in `include_silenced_till?’ from active_model/serializer.rb:375:in `include?’ … ``` Our system logs indicate we started getting these errors after we upgraded from Discourse v3.5.1 to v3.5.2 in late October 2025. The referenced lines were introduced in FIX: Delegate silenced_till from anonymous user to main user account by Drenmi · Pull Request #32416 · discourse/discourse · GitHub as discussed in Silenced user can circumvent it entering anonymous mode - #12 by pangbo . Solution I’m no Ruby expert myself, but since it looks to me that this happens with the API JSON pages that contain users that hasn’t been active since the changes in v3.5.2 I would guess there is a missing database migration handling some corner case with this change.

Are you running the latest version of Discourse? I believe your issue was fixed a couple months ago in https://github.com/discourse/discourse/commit/137638887a21c617223680b7b45bff59e1cbc828

[图片] torgeirl: Our system logs indicate we started getting these errors after we upgraded from Discourse v3.5.1 to v3.5.2 in late October 2025. The referenced lines were introduced in FIX: Delegate silenced_till from anonymous user to main user account · Pull Request #32416 · discourse/discourse as discussed in Silenced user can circumvent it entering anonymous mode - #12 by pangbo . Solution I’m no Ruby expert myself, but since it looks to me that this happens with the API JSON pages that contain users that hasn’t been active since the changes in v3.5.2 I would guess there is a missing database migration handling some corner case with this change. If you are still running v3.5.2, that’s your issue, because it’s significantly out of date and as mentioned the issue may be fixed in a newer version. Try updating your site to something more modern and try again.

@zogstrip: Yes, we are running 2026.1.3 (latest ESR, released on March 31 2026) and it looks like the fix was included in 2026.2.0 (and not backported) so the current ESR just missed it.

API 调用因 main_user_record 的 silenced_till 字段问题而失败

产品支持

zogstrip (Régis HANOL) 2026 年5 月 12 日 13:38 3

您运行的是最新版本的 Discourse 吗？我相信您的问题已在几个月前通过以下提交修复：

话题		回复	浏览量
Issues with the /get-users ending point Development rest-api	4	231	2024 年7 月 16 日
Please eval short Ruby script to suspend inactive users Development	3	220	2024 年9 月 4 日
The discourse stopped working with error 500 Internal Server Error Bug	1	3164	2017 年3 月 7 日
/admin/users/list/active returns users with active=false Feature	1	562	2019 年1 月 4 日
Sidekiq jobs are failing for 1 of my users Self-hosting	11	2368	2016 年10 月 6 日

API 调用因 main_user_record 的 silenced_till 字段问题而失败

相关话题