Thanks. Also note discourse-health-check v1.0.4 is now updated:
Two fixes:
-
Discourse replaced Unicorn with Pitchfork (default in 2026.2, Unicorn removed entirely
in 2026.4), so the web server check now detects both. Thanks @RGJ for flagging this
back in June. -
The service probes were matching their own command line.
pgrep -f <name>so pgrep matched itself and the check passed whether or not the service was actually up. Sidekiq had been reporting “running” unconditionally since 1.0.0. It could have been dead and you’d still get a green check and exit code 0 from cron. Same root cause as the Puma false
positive in 1.0.1, which turned out to have been renamed rather than fixed.
Oh, and now reports your PostgreSQL major version and flags anything below 15.
One more thing to carry through the upgrade, if you embed YouTube:
Discourse sends Referrer-Policy: same-origin by default, and YouTube rejects embed configuration requests that arrive without a referrer. You get Error 153 and videos won’t play. I hit this back in November and fixed it with a Cloudflare Transform Rule setting Referrer-Policy: strict-origin-when-cross-origin:
I checked the changelog while writing this post. There are no commits touching Referrer-Policy anywhere between 2026.1.5 and 2026.7.0, so this still isn’t fixed in core. If you have a workaround in place for it, don’t clean it up during the upgrade.
For anyone not on Cloudflare, a theme head entry does the same job:
<meta name="referrer" content="strict-origin-when-cross-origin">
Not able to edit that topic, it’s closed. So not it should be “set static” not add:
