Getting "Invalid response status: 502 Bad Gateway" updating to 0.3.5

Open
#203 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
networking

Research direction

Start with the WebSocketClient subclass and a websocket server, reproducing the connection with version 0.3.5 and confirming that 0.3.4 succeeds. Compare the connection behavior between those versions; the issue is done when the regression is identified and the connection no longer returns 502.

Written by the indexing model from the issue text.

Description

Since I updated from 0.3.4 to 0.3.5 I'm getting the following error when trying to connect to a websocket server:

Invalid response status: 502 Bad Gateway

The connection is done using a subclass of WebSocketClient. If I downgrade to 0.3.4, it works just fine.

Any Ideas?

Dominant language
Python
Stars
1.1k
Forks
285
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Lawouach/WebSocket-for-Python

All issues in Lawouach/WebSocket-for-Python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.