Ein Sun, 16 Oct 2016 10:28:25 -0500, Neill Miller <neillm@???> schrieb:
Hrm, specifying the server on the command line appears broken (at
> least in a v2 build of bx). I am also receiving connection timed out
> when using it for servers that are up, however setting the url in the
> bx.cfg to the same thing works.
>
> Can you try editing your bx.cfg instead?
>
> -Neill.
>

Here is the result:

> bx settings -c bx.cfg

settings
{
    network
    {
        channel_handshake_seconds 60
        connect_retries 1
        connect_timeout_seconds 30
        debug_file debug.log
        error_file error.log
        hosts_file hosts.cache
        identifier 3652501241
        seeds seed.bitnodes.io:8333,seed.bitcoinstats.com:8333,seed.bitcoin.sipa.be:8333,dnsseed.bluematt.me:8333,seed.bitcoin.jonasschnelli.ch:8333,dnsseed.bitcoin.dashjr.org:8333
    }
    server
    {
        client_private_key 0000000000000000000000000000000000000000
        connect_retries 1
        connect_timeout_seconds 30
        server_public_key 0000000000000000000000000000000000000000
        url tcp://libbitcoin1.thecodefactory.org:30000
    }
    wallet
    {
        hd_public_version 76067358
        hd_secret_version 76066276
        pay_to_public_key_hash_version 0
        pay_to_script_hash_version 5
        transaction_version 1
        wif_version 128
    }
}

> bx fetch-height -c bx.cfg
connection timed out
Exit 255


Regards,
Uwe H.

Uwe H.