httpx.RemoteProtocolError: peer closed connection without sending complete message body (incomplete chunked read)
See original GitHub issueThis error is occurring repeatedly every 90 seconds or so:
File "/home/user/.cache/pypoetry/virtualenvs/lnbits-c9dgov88-py3.9/lib/python3.9/site-packages/httpx/_transports/default.py", line 77, in map_httpcore_exceptions
raise mapped_exc(message) from exc
httpx.RemoteProtocolError: peer closed connection without sending complete message body (incomplete chunked read)
There are also errors arising from handling the error. Here’s the screen shot:
If any more information is useful, happy to provide.
This is lnbits-legend running on a VPS with NGINX and Let’s Encrypt certification. Just the way Option 1 (Poetry) made it.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
What behavior do we expect when a server issues an ... - GitHub
I think that our "ConnectionClosed: peer closed connection without sending complete message body (received 3743 bytes, expected 11628)" error ...
Read more >httpx.RemoteProtocolError: peer closed connection without ...
I've got the same error when using httpx via openapi-client autogenerated client response = httpx.request(verify=client.verify_ssl,**kwargs,).
Read more >peer closed connection without sending complete message ...
RemoteProtocolError : peer closed connection without sending complete message body (incomplete chunked read) The above exception was the direct cause of the ...
Read more >encode/community - Gitter
Hello everyone :) I have been using HTTPX for async requests with asyncio. ... peer closed connection without sending complete message body ......
Read more >API documentation — h11 0.14.0+dev documentation
A marker that indicates whether this data object is from the start of a chunked transfer encoding chunk. This field is ignored when...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
LNBITS_ENDPOINT=https://2b21057be1.d.voltageapp.io
Replaced the funding backend with an LNbits account running on a Voltage.cloud lite node and all the error messages have vanished.
Not exactly sure what’s happening here but I would guess this might have to do with the invoice listeners that are maybe broken on the remote instance. Which version is running there? Might be worth an update.