Summary In our Discourse instance, new posts and replies in topics are not appearing automatically. Users must manually refresh the page to see later posts, despite being actively viewing the topic. This appears to be a regression in real-time updates (MessageBus/WebSocket/polling), as no themes, plugins, or custom components are installed. Environment • Discourse version: 2026.4.0-latest (9776b417b8) • Hosting: self-hosted • Custom theme: default Steps to Reproduce 1. Open a topic in one browser/session 2. Open the same topic in another session/user account 3. Post a new reply in the topic 4. Observe the original session Expected Behavior New posts should appear in real-time without requiring a manual page refresh (via MessageBus updates / live topic updates). Actual Behavior New posts do not appear in the open topic view. They only appear after: • Manual browser refresh (F5 / reload), or • Navigating away and back to the topic Notes / Observations • No custom plugins or themes that could interfere • Appears consistent across users/sessions • Issue affects visibility of later posts in a topic thread specifically • Suggests possible regression or failure in: • `MessageBus` subscription handling • `/message-bus/ long polling / websocket` fallback • topic update stream (`topic:reload`, `post:created`) propagation Impact • Breaks real-time discussion flow • Causes users to miss new replies unless they refresh • Creates confusion about whether posting succeeded or not Request Could you please confirm whether there is a known regression affecting real-time topic updates in recent builds, or advise on what subsystem to inspect (MessageBus, polling fallback, etc.)?

Are you behind a proxy such as cloudflare etc?

No - there is no proxy or CDN in front of the instance (no Cloudflare or similar). This is a direct self-hosted setup with standard networking, so nothing external should be interfering with MessageBus/WebSocket or long-polling behaviour. Given that, it seems less likely to be caused by intermediary caching or connection buffering, and more likely something internal to the real-time update mechanism itself (e.g. MessageBus subscription, polling fallback, or client-side handling in this build). Happy to provide any logs (e.g. /logs , browser console, or /message-bus/ requests) if that would help narrow it down.

i confirm this is now working on v2026.4.0-latest +289 so the GitHub compare between this and when the bug was reported is [изображение] Comparing 9776b417b8...866ae39d4642f667eb75a663e672d0eaf32db595 ·... A platform for community discussion. Free, open, simple. - Comparing 9776b417b8...866ae39d4642f667eb75a663e672d0eaf32db595 · discourse/discourse that shows the likely commit that fixed this bug https://github.com/discourse/discourse/commit/ccdb162ccefec3586cef5b69f63f503d71e8985b

Новые сообщения/ответы не отображаются в реальном времени; требуется ручное обновление

Поддержка продукта

sam (Sam Saffron) 16.Апрель.2026 00:03:13 2

Вы находитесь за прокси-сервером, например Cloudflare и т.д.?

Тема		Ответов	Просм.
Topic list doesn’t refresh after posting Product Support	9	461	22.12.2023
"1 new or updated topic" on user's topic list page after straight after replying Bug	10	1737	29.07.2022
Topic doesn't show new posts on the fly anymore Product Support	3	611	24.03.2020
Does discourse have a feature to advise you that a new post has been added while you're working on a reply to a post Feature	1	415	26.05.2023
Own posts triggering updated topic notification Bug	0	590	19.09.2020

Новые сообщения/ответы не отображаются в реальном времени; требуется ручное обновление

Связанные темы