I have made the changes as above. Let me know how it goes!

Still no joy. Here's another version of websocketservice-debug.js that unmasks the data in multiple steps, so hopefully this'll work. If not, it'll log an error on the server side pinpointing exactly where the unmasking is failing.

https://tinyurl.com/yc2c86ys

---
þ Synchronet þ fTelnet Demo Server - ftelnet.synchro.net

Ignore my previous message -- I was able to get a virtual raspi working with qemu, and the version I linked to in the previous message still doesn't work.

But after a bunch more trial-and-error, I think I finally have a fixed version. It works on the virtual instance, hopefully it works on real hardware too!

https://tinyurl.com/2xmvr447

---
þ Synchronet þ fTelnet Demo Server - ftelnet.synchro.net

Ignore my previous message -- I was able to get a virtual raspi working with qemu, and the version I linked to in the previous message still doesn't work.

But after a bunch more trial-and-error, I think I finally have a fixed version. It works on the virtual instance, hopefully it works on real hardware too!

Behold! I put your new websocketservice.js in place (not on the debug port, but the standard port) and it seems to be working well! This is fantastic!

---
þ Synchronet þ Tucumcari BBS

Behold! I put your new websocketservice.js in place (not on the debug port, but the standard port) and it seems to be working well! This is fantastic!

Awesome, glad that finally did the trick! I'm still doing a bit of investigating to see if I can find a better option, because this is more of a workaround than a fix, and the bug we're working around here could crop up elsewhere and need another workaround, so a proper fix would be best. I'll let you know if I have something more to test later, if that's OK with you.

And thanks again for your help testing.

---
þ Synchronet þ fTelnet Demo Server - ftelnet.synchro.net