I'm having troubles using cli-wallet to connect to the public node listed.
Running ./programs/cli_wallet/cli_wallet -s wss://bitshares.openledger.info/ws gets me:
Logging RPC to file: logs/rpc/rpc.log
406168ms th_a main.cpp:131 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
406168ms th_a main.cpp:135 main ] nathan_pub_key: BTS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
406168ms th_a main.cpp:136 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Starting a new wallet with chain ID 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8 (from egenesis)
406168ms th_a main.cpp:183 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
I can't connect to a running witness node over localhost either.
are you sure the output of your command is the one provided ? it seems to me it is trying to connect to localhost instead of the server provided: wdata.ws_server: ws://127.0.0.1:8090
here is my output for the same command:
alfredo@alfredo-Inspiron-5559 ~/pull430/bitshares-core $ ./programs/cli_wallet/cli_wallet -s wss://bitshares.openledger.info/ws
Logging RPC to file: logs/rpc/rpc.log
1309572ms th_a main.cpp:131 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
1309721ms th_a main.cpp:135 main ] nathan_pub_key: BTS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
1309722ms th_a main.cpp:136 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Starting a new wallet with chain ID 4018d7844c78f6a6c41c6a552b898022310fc5dec06da467ee7905a8dad512c8 (from egenesis)
1309886ms th_a main.cpp:183 main ] wdata.ws_server: wss://bitshares.openledger.info/ws
1315739ms th_a main.cpp:188 main ] wdata.ws_user: wdata.ws_password:
Please use the set_password method to initialize a new wallet before continuing
new >>>
are you maybe using windows ? my output is from linux.
So is there a solution for this problem?
i think there is no problem here, need @torkelrogstad to confirm.
Yep.This is not a problem.I just made a mistake on spelling command line. Thx!!!
@torkelrogstad what's your boost version? AFAIK there is a bug with boost 1.60, need to remove the white space after -s (and any other options) to let the program recognize the parameter specified. For example, use ./programs/cli_wallet/cli_wallet -swss://bitshares.openledger.info/ws. Boost 1.57 and 1.58 don't have this issue.
no further response - not an issue.