First happened on Chrome on laptop, then same with Microsoft Edge on same laptop. Same with iPhone.
Ping works.
C:\Users\Groot>ping swi-prolog.discourse.group
Pinging swiprolog.hosted-by-discourse.com [2602:fd3f:3:ff01::cb] with 32 bytes of data:
Reply from 2602:fd3f:3:ff01::cb: time=85ms
Reply from 2602:fd3f:3:ff01::cb: time=82ms
Reply from 2602:fd3f:3:ff01::cb: time=80ms
Reply from 2602:fd3f:3:ff01::cb: time=85ms
Ping statistics for 2602:fd3f:3:ff01::cb:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 85ms, Average = 83ms
It works in safe mode, if thatās any comfort. Specifically, it works when I select ādisable official pluginsā so thatās going to be something weāre going to need to look at.
Let me see what I can find out.
Update: Itās looking like an update to the Maths plugin may be the culprit. Someone is looking at it now and we should have a fix in soon. Thanks for the report.
Hi, sorry for squatting this thread, but we have the exact same issue on our hosted site https://brian.discourse.group/ since an hour or so (worked fine earlier during the day). Using safe-mode with āunoffical pluginsā (do we use any?) disabled fixes it as well.
I agree. Knowing itās happening to more than one site can help us narrow down the cause if weāre not able to spot it straight away. Itās genuinely very useful.
Sorry it was my mistake. It should be fixed and deployed. Let me know if you see any other issue with this, itās an old plugin and I cleaned quite a lot.
After the problem I disabled both MathJax and AsciiMath on our site.
After seeing your reply reenabled them and then checked if the site was responding with a page refresh, it was, and if the MathJax plugins were working using our custom test page and they were not.
@EricGT ok I checked, this is correctly working, you must have updated the topic (great idea btw) when the plugin was disabled, I rebuilt the HTML and it seems all good
Thanks for the feedback, learned something new, that updating a topic with a plugin disabled could cause such a problem. While I am not a Ruby-on-Rails developer I take it that rebuilt the HTML means a rebake, please correct me if I am wrong.
Thanks for taking the time to look at this, being a developer myself I know such things happen from time to time but taking quick ownership is not so often seen, nice job.