Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error with WebSockets and UTF-8 encodings

See original GitHub issue

If within an instance you write curl www.google.com you’ll see that the javascript console shows: WebSocket connection to 'ws://play-with-docker.com/sessions/952dc23e-c830-40e2-ba0d-35ec548d0127/instances/goofy_keller/attach' failed: Could not decode a text frame as UTF-8. and terminal stops working

Issue Analytics

State:
Created 7 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

akalipetiscommented, Oct 11, 2016

I think we could go with Socket.io - @alexellis also had an issue connecting to WebSockets over a proxy. I might jump into this sometime during the week 🎉

1reaction

xetorthiocommented, Oct 11, 2016

Related to this is that maybe we should switch to socket.io. It has lots of fallbacks and seems to sve all these crazy issues.

On Mon, Oct 10, 2016, 20:04 Marcos Nils notifications@github.com wrote:

If within an instance you write curl www.google.com you’ll see that the javascript console shows: WebSocket connection to ‘ws:// play-with-docker.com/sessions/952dc23e-c830-40e2-ba0d-35ec548d0127/instances/goofy_keller/attach’ failed: Could not decode a text frame as UTF-8. and terminal stops working

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/franela/play-with-docker/issues/10, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIhp72_I5K_GyfY0tT1Pd3AlylIwzx1ks5qysRkgaJpZM4KTE9T .