When I’m typing a reply to someone else’s message I get this notice while I’m composing my reply. It doesn’t happen every time I make a post but when it does it will pop up multiple times while I’m composing my reply.
When it shows up I’m not editing anything in another window. Clicking on “Ignore” opens up the page for further typing but the notice soon shows up again.
I’ve had the same happen a few times recently.
I agree with this annoyance.
Me too. 
Plus 20
Same here, multiple times.
Me too. 12345
This could be a bug introduced with the latest update. I’ll update again as soon as I get a chance.
Thanks,
Gunnar
It happened to me several months ago as well, It went away so I didn’t bother reporting it.
Also today I started getting “529 Too Many Requests” notices and the unsmilie “cannot reach that page”
notices. Not getting them now as I type this and also not getting the editing notice. Maybe they are all related.
I’ve updated the forum software again. Let’s see if that helps.
Thanks,
Gunnar
I got the same “couldn’t load topic” message a couple of times today. I’ve noticed that if I get that error and try again I’ll often get the topic back, but it will be displayed from the first post rather than the first “new” post that I haven’t read.
Same here.
I had a look on the Discourse developer forum, and found this article from 2022 that seems relevant. I’m not sure if the explanation there applies to us, though.
They also suggest looking at the logs, which I have, without finding anything. I’ve also never had this error happen to me.
The next time it happens, could you please post a link to the message you were trying to access? Just so I can see if I’m able to reproduce the error.
Thanks,
Gunnar
FWIW, I’ve had that happen to me once or twice in the last year, but no more often than that.
I saw that one today as well (note: it’s 429, not 529), “Too many requests.”
Apparently, this is caused by problems in the site code, but unfortunately (or luckily), that’s out of my control. What I can do, is make sure that this issue isn’t caused by the “front end” Nginx reverse proxy that sits between the client and Discourse.
I’ve made some tweaks to the configuration of Nginx now, let’s see if it helps.
I got the “editting in another window” issue again earlier today for the first time for a while. This may be a clue: it occured while I was creating a reply and hit some unknown key, or clicked an unknown icon, and the entire reply vanished, though the reply window remained open. When I tried to re-compose my reply the “editting in another window” popped up with my first keyboard entry. I cleared it, and all was well from then on.
Hi David,
I did also update Discourse earlier today, so it’s possible you were editing your message just as Discourse was being updated and restarted.
