You really should set it up on a different server than discourse, at the bare minimum don’t use the docker bridge for uptime kuma or take discourse out of the bridge.

Thank you for this check I’m going to debug the problem on my side and I’ll let you know

FrancescoM: > Maybe something to set on Discourse? No, there is nothing to set up on discourse because problem is with your install of uptime kuma not discourse. I set up your site as a monitor on a fresh uptime kuma and it works.

I tried but it shows me the same error. I also set up a new monitor for a different website inside the same server, and it works perfectly. Maybe something to set on Discourse? Thanks again for your help

Change the monitor type to keyword first.

itsbhanusharma: > change the setup to monitor ok keyword Ok, I removed the SSL check, but how can I set the “ok” keyword? Here?

FrancescoM: > Can I try something else? change the setup to monitor ok keyword, disable ssl check.

Hi, thanks for the advice. The Discourse app has an SSL certificate generated by Traefik using Let’s Encrypt. Right now I’m using the container check using docker socket, but it’s not reliable. Can I try something else? I have only one server with docker. Thanks again

That’s funny, I recently read old topics about how Discourse hijacked the `Ctrl`+`f` feature of the browser. I understand the intent, but in 7+ years of using Discourse, it always annoyed me more than it helped me. I’m happy to see the feature gone, especially since there’s the `\` shortcut to replace it (even though it requires pressing two keys on a French keyboard).

Most likely it is certificate mismatch. And the uptime monitor will not catch issues if the server itself is down, hence it is recommended to have it on a server that’s different than the one with the rest of your application(s)

No way! I’d never have realised. Thanks.

https://meta.discourse.org/search?q=tags%3Aai%2Bsearch does not only return topics tagged with ai and search, which is what I would expect, but also topics tagged with ai and ai-search. The topic filter doesn’t have this problem: https://meta.discourse.org/filter?q=tag%3Aai%2Bsearch

When you are in full page mode, the back button is the back button of your browser

is uptime kuma hosted on the same machine as discourse? EDIT: FrancescoM: > I’m using also a docker network “proxy_network” for Traefik. I believe this is your problem.

Hi @itsbhanusharma and thank you for the quick answer! I set up only the status code, this is my configuration I’m using also a docker network “proxy_network” for Traefik. Thanks again for your help!

riknoll: > I just tried removing that wildcard and replacing it with a single domain (YouTube) but it doesn’t seem to have had any effect on the embed. Did you try rebuilding the post’s HTML after that (Post 3 dots > Admin wrench > Rebuild HTML)?

Could the math tag be added? Thanks.

This is a bit weird, can you share a screenshot of how you configured it? You have to set it up as keyword monitor, looking for keyword “ok” and status code 200

Hi! I tried to use Uptime Kuma pointing `/srv/status` but it tells me “Connection Refused”. I’m using Uptime Kuma in a container, as well as Discourse. Also, for both I’m using traefik for reverse proxy. Uptime Kuma with other website works very well, but I can’t reach the Discourse app. Can you tell me why? Thanks in advice!

Hi team, Is there a plan to eventually combine the standard search bar and Discourse AI into a single AI-driven chat interface? Also, are there any updates on displaying sources/citations from forum topics in a more integrated way, similar to how **NotebookLM** handles document sources? Thanks!

Because https://meta.discourse.org/raw/393640 says the report was made this year

Ethsim2: > Looks like this report just hit an instance that hadn’t updated yet Well, the report was written in 2024. There was no fix back then. Why do you assume they haven’t updated since?

Yep - this was already fixed quite a while ago The MathJax-inside-[details] issue was resolved by MathJax not working inside details sections > FIX: prefers textContent over innerText by jjaffeux · Pull Request #111 · discourse/discourse-math · GitHub That change has been in place for a long time, which is why Sam’s example now renders correctly. Looks like this report just hit an instance that hadn’t updated yet - all good now.

Yup, we were caught up in that. An update has sorted it.

Lead the way Discourse, Thank all you guys