I’m trying to move ~100 posts to an existing topic. After a delay of about 10 seconds, it says there was an error when moving posts in a green alert area: [image] No new entries in /logs No useful information in console either: [image] What can be wrong and where to look for the error?

Very likely babble, I am guessing it has hooks that fire on post move.

Good to know. Thanks. And props to @featheredtoast for the fix.

My community recently started experiencing the 502 error issue when moving posts, especially between large threads. I had no custom plug-ins installed. Following the advice from another Discourse thread, I increased the unicorn_workers to 10 and db_shared_buffers to 4096MB, but that did not ameliora…

Hi, I encounter the same issue. Can’t split megatopics because of this. Also tried in safe-mode, didn’t change anything. [image] No issue in my development Discourse installation (same version 2.6.0.beta2) though. And nothing in the logs.

I’m getting this 502 errors for an year ;(

I don’t think we’ve asked you: what plugins are you running?

I disable all plugins to check is it plugin related bug. It looks like it repeated stable with long threads.

This most annoying bug is still with us. Could you give me instructions to nail the problem?

Unfortunately we are still running into this issue from time to time. I managed to collect some data about a recent problem where moving 27 posts into an existing topic (2013 posts) failed: Beginning move at 2021-05-25 20:54:57 +0000 create_temp_table 0.000134 0.000027 0.000161 ( 0.002810) …

Maybe we defer the update_statistics work to sidekiq?

Moving posts returns 502 bad gateway

지원 자체 호스팅

글		댓글	조회수
Moving posts to a long topic fails Bug	4	226	1월 28, 2025
Unable to move posts between topics Bug fixed	2	170	12월 10, 2024
Moving shipments causes an error Bug	4	169	12월 18, 2024
500 Error: There was an error moving posts Bug	3	411	10월 25, 2023
"There was an error moving posts" Bug	2	156	12월 12, 2024

Moving posts returns 502 bad gateway

Related topics