("Connection broken: ConnectionResetError(104, 'Connection reset by peer')", ConnectionResetError(104, 'Connection reset by peer'))
The majority of the connected Prusa disconnects for a few seconds and reconnects. While it does not disrupt the ongoing printing, the problem is seen with transfers.
The most common way to manage any of Prusas to lose connection is to begin a transfer and eventually, it will disconnect and reconnect. The transfers seem to continue for a little while but eventually fail to upload them to printers. But not all transfers fail, because if you restart the printer after it is on for a while, regardless of disconnects the transfers will be successful.
Another noticeable thing is that after a while, while PrusaConnect has the ability to communicate with Printers, the PrusaLink IP addresses no longer respond with access e.g. you cannot access the https://ip-here address not until you restart.
- PrusaLink0.7.0.rc1
- PrusaConnect SDK0.7.0.rc1
- Prusa MK3S
- Raspberry Pi Zero 2 W
- Transfer ID 2709354680332144600
Common error logs :
- ("Connection broken: ConnectionResetError(104, 'Connection reset by peer')", ConnectionResetError(104, 'Connection reset by peer'))
- HTTPSConnectionPool(host='connect.prusa3d.com', port=443): Read timed out.
RE:
Yes, I see them and bring them up constantly in the office. I am not sure what can I myself do, maybe I can run Wireshark to see where are the poor packets getting stuck. But I don't know much about diagnosing network traffic :/ Sorry it's giving you trouble.