I see. Were you not getting these errors earlier? We have seen these errors in the past, and it is due to an issue with the Go standard library which was just recently fixed (i.e. not yet in a released Go version). But it shouldn’t have to do anything with websockets.