Intermittent errors connecting to signaling server #31
Assignees
Labels
Projects
Comments
|
|
Looks like at some point the websockets connection to heroku gets corrupted. When PeerJS tries to recover and connect with its known peerid, the signaling server thinks that it is a conflicting registration from a different peer instead of reconnection attempt from the same peer. One possible solution is to pause a bit longer to give the signaling server a chance to clean up the peer id from its realm due to inactivity. Then try to reconnect. Another option is to make the signaling server smarter and make it check the source of the reconnection request against the original source. If they are the same, allow the reconnect with same Peer ID. |
|
The issue is still present. After a few hours of normal operation, the python peer eventually goes into this endless loop unable to regain connection to the signaling server due to its peer ID already being reserved. |
|
🎉 This issue has been resolved in version 1.4.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
ivelin
pushed a commit
to ambianic/ambianic-edge
that referenced
this issue
Nov 28, 2020
github-actions bot
pushed a commit
to ivelin/peerjs-python
that referenced
this issue
Sep 21, 2021
## [1.4.1](v1.4.0...v1.4.1) (2021-09-21) ### Bug Fixes * allow more lenient peers id load ([1fe71b6](1fe71b6)), closes [ambianic#51](https://github.com/ivelin/peerjs-python/issues/51) * allow more lenient peers id load ([981ae27](981ae27)) * load peer ID from an empty file ([4cfe6fb](4cfe6fb)), closes [ambianic#52](https://github.com/ivelin/peerjs-python/issues/52) * load peer ID from an empty file ([b9ff9fa](b9ff9fa)) * log_level not found in config ([fb0a2da](fb0a2da)), closes [ambianic#53](https://github.com/ivelin/peerjs-python/issues/53) * log_level not found in config ([ddfedea](ddfedea)) * merge pull request [ambianic#38](https://github.com/ivelin/peerjs-python/issues/38) from ivelin/master ([12a4365](12a4365)) * peer reconnect error; closes [ambianic#31](https://github.com/ivelin/peerjs-python/issues/31) ([6b68cfa](6b68cfa)) * rename http-proxy to http_proxy ([8ee5e0b](8ee5e0b)), closes [ambianic#50](https://github.com/ivelin/peerjs-python/issues/50)
ivelin
pushed a commit
that referenced
this issue
Sep 24, 2021
* build: update deps versions * build: test sem rel action * build: update access tokens * build: sem rel fix * build: sem rel * build: test new script Signed-off-by: ivelin <ivelin@ambianic.ai> * chore(release): 1.4.1 [skip ci] ## [1.4.1](ivelin/peerjs-python@v1.4.0...v1.4.1) (2021-09-21) ### Bug Fixes * allow more lenient peers id load ([1fe71b6](ivelin@1fe71b6)), closes [#51](https://github.com/ivelin/peerjs-python/issues/51) * allow more lenient peers id load ([981ae27](ivelin@981ae27)) * load peer ID from an empty file ([4cfe6fb](ivelin@4cfe6fb)), closes [#52](https://github.com/ivelin/peerjs-python/issues/52) * load peer ID from an empty file ([b9ff9fa](ivelin@b9ff9fa)) * log_level not found in config ([fb0a2da](ivelin@fb0a2da)), closes [#53](https://github.com/ivelin/peerjs-python/issues/53) * log_level not found in config ([ddfedea](ivelin@ddfedea)) * merge pull request [#38](https://github.com/ivelin/peerjs-python/issues/38) from ivelin/master ([12a4365](ivelin@12a4365)) * peer reconnect error; closes [#31](https://github.com/ivelin/peerjs-python/issues/31) ([6b68cfa](ivelin@6b68cfa)) * rename http-proxy to http_proxy ([8ee5e0b](ivelin@8ee5e0b)), closes [#50](https://github.com/ivelin/peerjs-python/issues/50) * build: test new script Signed-off-by: ivelin <ivelin@ambianic.ai> * build: test new script Signed-off-by: ivelin <ivelin@ambianic.ai> * fix: test new script Signed-off-by: ivelin <ivelin@ambianic.ai> * chore(release): 1.4.2 [skip ci] ## [1.4.2](ivelin/peerjs-python@v1.4.1...v1.4.2) (2021-09-21) ### Bug Fixes * test new script ([5090913](ivelin@5090913)) Co-authored-by: semantic-release-bot <semantic-release-bot@martynus.net>
ivelin
pushed a commit
that referenced
this issue
Oct 5, 2021
* build: update deps versions * build: test sem rel action * build: update access tokens * build: sem rel fix * build: sem rel * build: test new script Signed-off-by: ivelin <ivelin@ambianic.ai> * chore(release): 1.4.1 [skip ci] ## [1.4.1](ivelin/peerjs-python@v1.4.0...v1.4.1) (2021-09-21) ### Bug Fixes * allow more lenient peers id load ([1fe71b6](ivelin@1fe71b6)), closes [#51](https://github.com/ivelin/peerjs-python/issues/51) * allow more lenient peers id load ([981ae27](ivelin@981ae27)) * load peer ID from an empty file ([4cfe6fb](ivelin@4cfe6fb)), closes [#52](https://github.com/ivelin/peerjs-python/issues/52) * load peer ID from an empty file ([b9ff9fa](ivelin@b9ff9fa)) * log_level not found in config ([fb0a2da](ivelin@fb0a2da)), closes [#53](https://github.com/ivelin/peerjs-python/issues/53) * log_level not found in config ([ddfedea](ivelin@ddfedea)) * merge pull request [#38](https://github.com/ivelin/peerjs-python/issues/38) from ivelin/master ([12a4365](ivelin@12a4365)) * peer reconnect error; closes [#31](https://github.com/ivelin/peerjs-python/issues/31) ([6b68cfa](ivelin@6b68cfa)) * rename http-proxy to http_proxy ([8ee5e0b](ivelin@8ee5e0b)), closes [#50](https://github.com/ivelin/peerjs-python/issues/50) * build: test new script Signed-off-by: ivelin <ivelin@ambianic.ai> * build: test new script Signed-off-by: ivelin <ivelin@ambianic.ai> * fix: test new script Signed-off-by: ivelin <ivelin@ambianic.ai> * chore(release): 1.4.2 [skip ci] ## [1.4.2](ivelin/peerjs-python@v1.4.1...v1.4.2) (2021-09-21) ### Bug Fixes * test new script ([5090913](ivelin@5090913)) * chore: checkpoint Signed-off-by: ivelin <ivelin@ambianic.ai> Co-authored-by: semantic-release-bot <semantic-release-bot@martynus.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: