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.

On Sun, Oct 16, 2016 at 05:20:35PM +0200, bug456@??? wrote:
>
>
> Ein Sun, 16 Oct 2016 06:46:42 -0700, Eric Voskuil <eric@???> schrieb:
> On 10/15/2016 11:58 PM, bug456@??? wrote:
> > > When I instead use 'libbitcoin-explore-master/data/bx-testnet.cfg' a
> > > the configuration file, I receive a number.
> >
> > This is the blockchain height at that server, so it is working.
> >
> > > I had a working version of bx on the same machine some months ago, but
> > upgraded the system.
> >
> > I don't see that you have any problem except that the server is down and
> > the configuration file is not located. If you call:
> >
> > $ bx fetch-height -c bx.cfg
> >
> > The default path for the process is used. If you call:
> >
> > $ bx fetch-height
> >
> > The file 'bx.cfg' in the installed location is used. Use the command:
> >
> > $ bx settings
> >
> > to determine if your configuration file is actually being used.
> >
> ...
>
> Thanks. I understand all of that. To clarify again, here is my output (now using specification of the server on the command line, thanks for the hint):
>
> > bx fetch-height tcp://obelisk-testnet.airbitz.co:9091
> 645774
>
> > bx fetch-height tcp://obelisk.airbitz.co:9091
> connection timed out
> Exit 255
>
> > bx fetch-height tcp://obelisk.bysh.me:9091
> connection timed out
> Exit 255
>
> > bx fetch-height tcp://libbitcoin1.thecodefactory.org:30000
> connection timed out
> Exit 255
>
>
> Is this some problem in my configuration, or is it saying that the last three servers I was trying to point to are down?
>
> Regards,
> Uwe H.
>
> Uwe H.
> _______________________________________________
> Libbitcoin mailing list
> Libbitcoin@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin