yes, I have the -s issue but the --server-rpc-endpoint is working ok.

Quote from: xeroc on March 30, 2017, 04:46:40 AM
For some reason, the short forms of the parameters don't work everywhere.
Also the API node of bitshares.eu is called 'node.bitshares.eu':

Try this:

Code Select Expand


./programs/cli_wallet/cli_wallet --server-rpc-endpoint=wss://node.bitshares.eu


Quote from: roelandp on April 02, 2017, 06:43:53 PM
HI Mostar, I noticed the same error on one of my servers.... it happens to be a conflict with UFW / Iptables to my best guess...

I have not yet debugged it, since I managed to run the cli_wallet with local ws connection on the other server. On the not working server the aformentioned suggestions using a trusted wsS remote websocket does work as well.

Looks like that is it most likely. I was able to recreate that on my server and got the same error. To get it working again I had to disable ufw AND reboot the server, it connected right away after that.

Quote from: roelandp on April 02, 2017, 06:43:53 PM
HI Mostar, I noticed the same error on one of my servers.... it happens to be a conflict with UFW / Iptables to my best guess...

I have not yet debugged it, since I managed to run the cli_wallet with local ws connection on the other server. On the not working server the aformentioned suggestions using a trusted wsS remote websocket does work as well.

Howdy Roland - annnd welcome on board here :) !

HI Mostar, I noticed the same error on one of my servers.... it happens to be a conflict with UFW / Iptables to my best guess...

I have not yet debugged it, since I managed to run the cli_wallet with local ws connection on the other server. On the not working server the aformentioned suggestions using a trusted wsS remote websocket does work as well.

For some reason, the short forms of the parameters don't work everywhere.
Also the API node of bitshares.eu is called 'node.bitshares.eu':

Try this:

./programs/cli_wallet/cli_wallet --server-rpc-endpoint=wss://node.bitshares.eu



./programs/cli_wallet/cli_wallet -s wss://bitshares.opedger.info/ws:8090
./programs/cli_wallet/cli_wallet -s wss://openledger.io/
./programs/cli_wallet/cli_wallet -s wss://openledger.io/:8090
./programs/cli_wallet/cli_wallet -s wss://openledger.io:8090
./programs/cli_wallet/cli_wallet -s wss://wallet.bitshares.eu/
./programs/cli_wallet/cli_wallet -s wss://wallet.bitshares.eu/:8090
./programs/cli_wallet/cli_wallet -s wss://wallet.bitshares.eu:8090


It all fail on the same above error

I have not had a chance to recreate it but try adding the port number at the end:

./programs/cli_wallet/cli_wallet -s wss://bitshares.openledger.info/ws:8090

Hello,

I download and compile fresh copy of bitshares code.
Now I want to connect the cli_wallet to remote server.  The command:


./programs/cli_wallet/cli_wallet -s wss://bitshares.openledger.info/ws


Quote
Fail on
ogging RPC to file: logs/rpc/rpc.log
3536112ms th_a       main.cpp:120                  main                 ] key_to_wif( committee_private_key ): 5.........
3536112ms th_a       main.cpp:124                  main                 ] nathan_pub_key: BTS......
3536112ms th_a       main.cpp:125                  main                 ] key_to_wif( nathan_private_key ): 5.........
Starting a new wallet with chain ID 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8 (from egenesis)
3536113ms th_a       main.cpp:172                  main                 ] wdata.ws_server: ws://127.0.0.1:8090
0 exception: unspecified
Underlying Transport Error
    {"message":"Underlying Transport Error"}
    asio  websocket.cpp:449 operator()

    {"uri":"ws://127.0.0.1:8090"}
    th_a  websocket.cpp:678 connect

Changing -s wss: to any other open witness_node fail on the same error.
I don't run local witness_node.

What I'm missing?

Mostar