게시글 이동 시 500 오류 발생

Moving a single or multiple posts of a thread into another thread located in another category results in http 500 error. I tested with both a moderator and admin account and with both a single post or multiple selected posts. Permission matrix of the categories:

Category Group Permissions
Source anybody see
Source group01 see reply create
Target group01 see reply create

Note that we have we have a separate permission group for mods and admins and I assume that the root cause is some tricky permissions issue. Ideas how to debug this are welcome :smiling_face_with_sunglasses:

Update: The source catogory in federated (ActivityPub), maybe this plugin code plays a role too… I removed the separate permission groups for mods and admins and tested again with two accounts which have “standard” mod (Moderator = Yes) or admin (Admin = Yes) permissions. Same results: The error 500 appears for any use case: new topic, existing topic, new message.

:white_exclamation_mark: Note: This bug was already reported a few times earlier and there were already some code fixes. I see it again in our instance with the current release 2026.3.0-latest

1개의 좋아요

Anything in the console?

Does any of the post contains a solution?

I couldnt find a solution from older posts yet. Here is the screenshot

The console shows that the 500 appears directly after a POST request for

https://forum.netzwissen.de/t/1431/move-posts
[HTTP/2 500  60ms]

which should be equivalent to clicking on the blue button. Any ideas how to debug that a bit deeper?

Is there something more helpful in the network tab of your browser console? That helped me in January with an error while moving posts.

1개의 좋아요

… unfortunately not, at least I don’t see anything useful in the response in this (compressed) har file (see response following the line 165).

forum.netzwissen.de_t_1431_move-posts_Archive [26-03-05 22-14-18].har.zip (2.8 KB)

I did some deeper debugging. Even the nginx log inside the container shows no useful information about whats going on

root@docker5-web-only:/var/log/nginx# tail -f access.log | grep 500
[06/Mar/2026:08:51:45 +0000] "``forum.netzwissen.de``" 10.10.10.21 "POST /t/1431/move-posts HTTP/1.0" "Mozilla/5.0 (X11; Linux x86
_64; rv:148.0) Gecko/20100101 Firefox/148.0" "topics/move_posts" 500 432 "``https://forum.netzwissen.de/t/begehung-quartierszent
rum-mettingen/1431/3" 0.053 0.052 "mainmod" "-" "-" "-" "-" "-" "-"

I would guess that the root cause lies somewhere behind, e.g. in the database request from postgres (we use separate containers and a dedicated postgres server)

불행히도 이 문제는 아직 해결되지 않았고, 특정 논리나 전제 조건 없이 간헐적으로 발생하고 있습니다. 따라서 재현하기가 어렵습니다.

다시 웹 애플리케이션의 nginx 로그를 확인해 보았지만, 컨테이너 서버 측에서 HTTP 500 에러에 대한 어떤 표시도 찾을 수 없었습니다.

@here 이 문제가 해결될 확률이 55%입니다 :sweat_smile:

3개의 좋아요

완벽합니다, 감사합니다. 이 코드는 ActivityPub 플러그인 코드 일부인 것 같습니다. 이 플러그인이 이미 메인 코드에 번들링되어 있는지 기억이 나지 않네요 (참고: Bundling more popular plugins with Discourse core ). 어쨌든, 다음 빌드/컨테이너 업데이트와 함께 배포될 것이라 이해하면 되나요?

플러그인이 "메인 코드에 포함된다"는 것은 https://github.com/discourse/discourse/tree/main/plugins 아래에 있다는 뜻입니다. 해당 경우, discourse-activity-pub는 메인 코드에 포함되어 있지 않습니다 :slight_smile:

Matty Matheson Says Correct

이 주제는 4일 후 자동으로 닫혔습니다. 더 이상 새 답변을 작성할 수 없습니다.