Commenting and chat seem to be broken
-
@mfalkvidd said in Commenting and chat seem to be broken:
@NeverDie kill it with fire 😁
I nuked it from orbit. It's the only way to be sure.... :wink:
Reporting back: Rechecked just now, though, after wiping and re-installing Windows 10 fresh, and the same problem persists when using Chrome and trying to comment on lcduino. Mysterious! At least Firefox is a workaround.
-
@mfalkvidd said in Commenting and chat seem to be broken:
@NeverDie kill it with fire 😁
I nuked it from orbit. It's the only way to be sure.... :wink:
Reporting back: Rechecked just now, though, after wiping and re-installing Windows 10 fresh, and the same problem persists when using Chrome and trying to comment on lcduino. Mysterious! At least Firefox is a workaround.
@NeverDie said in Commenting and chat seem to be broken:
after wiping and re-installing Windows 10 fresh
Do you really do that just for a problem on one website with one browser ? That's a bit extreme :D
-
@NeverDie said in Commenting and chat seem to be broken:
after wiping and re-installing Windows 10 fresh
Do you really do that just for a problem on one website with one browser ? That's a bit extreme :D
@Nca78 said in Commenting and chat seem to be broken:
@NeverDie said in Commenting and chat seem to be broken:
after wiping and re-installing Windows 10 fresh
Do you really do that just for a problem on one website with one browser ? That's a bit extreme :D
Yup. I really did, but only because it looked like something a virus might do: force some bogus login to steel a password. Not that a mysensors password has monetary value, but an indiscriminate virus wouldn't know that.
-
Hmm.. something seems to be broken (for me as well). The "Login" button should not be present if you are logged in to the forum. Clicking it seems to generate a js-error.
This all might be triggered by some new cross-site security feature of chrome and it could take some time for me to figure out a solution.
-
Not sure if it is related, but https://www.mysensors.org/build/raspberry is pretty broken. Code is not formatted as code, but some of the regular text is formatted as code instead. Images are missing. I'll take a look later.
This screen shot was taken with Safari on ipad. -
Not sure if it helps. But chrome changed things for CORS. If the CURS headers aren't set correctly you can not use a rest api anymore.
-
Not sure if it is related, but https://www.mysensors.org/build/raspberry is pretty broken. Code is not formatted as code, but some of the regular text is formatted as code instead. Images are missing. I'll take a look later.
This screen shot was taken with Safari on ipad.I fixed the raspberry article, the updated markup-parser seems a bit more picky about newlines before/after headers and code-blocks for some reason.
Edit: Correction, the bare <br> html-elements all over the article needs to be separated with newlines -
Hmm, I also have an issue, although it's likely unrelated. Every few minutes, there are three or four consecutive polling requests - some of which are also quite slow (>500ms) - by the sockets.io script that are all responded with a 405 (method not allowed). Right after that, it switches protocol from HTTP2 to HTTP1.1 and sends another few requests, which now are all responded with a 200 (OK).
It doesn't break anything as far as I can tell. It shows a "Looks like your connection was lost" modal in the bottom right corner and the forum's navigation bar shifts to the side (and sometime appears as if I'm logged out). After a few seconds, it's all back to normal. It just happens very frequently since a few weeks or so.
I'm using Firefox (86), but I have seen it happen in Chromium-based browsers as well.
-
@hek Can confirm. Didn't get any 405 responses nor pesky modals over the last few hours. Thank you!
@BearWithBeard
Good!Still investigating the comment problems on openhardware.io. Might need to do manual restarts of the forum to test things later on.
-
Ok, could not find the root cause for why the embedded forum thread on openhardware.io couldn't detect if user has a valid session/is logged in to the forum.
Did a workaround by adding a "Comment" button which redirect user to the thread on the forum.
