# Websockify protocol errors
**URL:** https://discourse.openondemand.org/t/websockify-protocol-errors/4600
**Category:** Get Help
**Created:** [October 23, 2025, 9:08pm UTC](https://discourse.openondemand.org/t/websockify-protocol-errors/4600 "2025-10-23T21:08:24Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@mrobbert](https://discourse.openondemand.org/u/mrobbert)
#### Post date: [October 23, 2025, 9:08pm UTC](https://discourse.openondemand.org/t/websockify-protocol-errors/4600/1 "2025-10-23T21:08:24Z")
I’m working on a new deployment of OnDemand and ran into a problem with websockify when trying to get a batch\_connect session running. We’re currently running the OnDemand 4.0.7 on Rocky 9.6 using the OSC repo RPMS. The compute nodes that we’re connecting to are running SLES 15.4. I was initially testing with the Suse provided package python-websockify-0.8.0-9.3.1.
It looks like that has been seen a few times in the past the most relevant thread that helped me is here:
[https://discourse.openondemand.org/t/novnc-failed-to-connect-to-server-ondemand-3-0-1/2711/30](https://discourse.openondemand.org/t/novnc-failed-to-connect-to-server-ondemand-3-0-1/2711/30)
The relevant errors are from the websockify.log as seen below.
```auto
x.x.x.x - - [23/Oct/2025 11:30:29] code 400, message Client must support 'binary' or 'base64' protocol
x.x.x.x - - [23/Oct/2025 11:30:29] code 405, message Method Not Allowed
```
I tested the change to websock.js that was mentioned in the previous topic
```auto
open(uri, protocols) {
//this.attach(new WebSocket(uri, protocols));
this.attach(new WebSocket(uri, ['binary', 'base64']));
}
```
That worked, but I don’t want to go into production with a change to an RPM provided file so the next thing I tried (after changing the file back) was to install a newer version of websockify using conda. That pulled in 0.13.0 and that worked to fix the problem. I can probably work it out to get that conda environment installed in a shared space that is available to all users, but wanted to make sure that is necessary. Is it possible that I missed something else when using the python3-websockify 0.8.0 package? The documentation still says that 0.8.0 is the minimum required version or is a newer version actually required?
Thanks for any information you can provide.
---
### Author:  [@Dzung.Nguyen](https://discourse.openondemand.org/u/Dzung.Nguyen)
#### Post date: [October 27, 2025, 2:46pm UTC](https://discourse.openondemand.org/t/websockify-protocol-errors/4600/2 "2025-10-27T14:46:28Z")
Dear Michael,
I can confirm that Websockify equal to or below 0.80 won’t work. The problem was only able to be solved when a higher version of Websockify was used. Websockify 0.13.0 definitely works
Our cluster (LRZ) at the time installed SLES 15.5, so there was only a lower version of Websockify even from Python packages. I worked around it by providing Websockify from a Charliecloud image.
Kind regards,
Dzung
---
### Author:  [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)
#### Post date: [October 27, 2025, 2:51pm UTC](https://discourse.openondemand.org/t/websockify-protocol-errors/4600/3 "2025-10-27T14:51:05Z")
> [@Dzung.Nguyen](#):
>
> Websockify 0.13.0 definitely works
That could definitely be the case. I’ll update the documentation shortly.
---
### Author:  [@system](https://discourse.openondemand.org/u/system)
#### Post date: [April 25, 2026, 2:51pm UTC](https://discourse.openondemand.org/t/websockify-protocol-errors/4600/4 "2026-04-25T14:51:53Z")
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.