ThomasFreedman
commented
6 years ago I bypassed nginx and the proxy and just used a local non-ssl ws address (ws://127.0.0.1:8090/) and it also fails, but with "[Errno 104] Connection reset by peer". In this case I'm running on the host of a docker container which proxies the witness_node running in the container (which is successfully synced to ppy chain).
The whole point of using python-peerplays was to validate correct port access on the docker host to the node running in the container. Although netstat on the host reports the correct ports are being proxied by docker, there may still be an issue I have yet to discover within the container.
I was using a different API node URL which doesn't involve docker when I got the ssl errors above, so these issues have different contexts, tho the same python-peerplays program . Also, it's possible there are differences between bitshares and peerplays python libs I am not aware of related to this problem, as I mentioned in my first report above.
Here is an excerpt from the results of "docker inspect
"PortBindings": {
"7887/tcp": [
{
"HostIp": "0.0.0.0",
"HostPort": "7887"
}
],
"8090/tcp": [
{
"HostIp": "127.0.0.1",
"HostPort": "8090"
}
],
"8092/tcp": [
{
"HostIp": "127.0.0.1",
"HostPort": "8092"
}
]I should be able to connect using python-bitshares running on the host. I have a cli_wallet in the container which I can access from the host with:
sudo docker exec -it ppy cli_wallet -H 127.0.0.1:8092 -s ws://127.0.0.1:8090Here are the import lines from my python script, which I believe are correct:
from peerplays import PeerPlays
from peerplays.account import Account
from peerplays.witness import Witnessand the failure is occurring at:
API = PeerPlays("ws://127.0.0.1:8090/")From inside the container here is what netstat -tulpn reports:
tcp 0 0 127.0.0.1:8090 0.0.0.0:* LISTEN 7/witness_node
tcp 0 0 127.0.0.1:8092 0.0.0.0:* LISTEN 56/cli_wallet
tcp 0 0 0.0.0.0:7887 0.0.0.0:* LISTEN 7/witness_node
udp 0 0 0.0.0.0:54368 0.0.0.0:* 7/witness_node 
roelandp
xeroc
This may be a known issue, but I just tried to use a python-bitshares program as a starting point (template) for peerplays and it cannot connect to an API node, at least not in the same way.
I did install and use python-peerplays earlier to sign the email for PBSA confluence, but that installation is now gone. The docs for python-peerplays look further out of date than for bitshares, again this may be a known issue.
Here is the call that fails and the error:
Note that the SSL certificates are indeed valid. The websocket URL is an nginx proxy. That nginx server also serves a web page using the same cert and according to firefox the cert is valid, plus the cli_wallet has no problem with that websocket address.
I suspect when fabian updates python-peerplays with the changes he's made to python-bitshares this issue may well go away.