There are no usable args when specifying a URL (help would override and I believe -c would be ignored), but if it affects your results I would assume it's being treated as part of the URL, which could only happen if it was to the right of the URL, though I wouldn't expect this because the URL should be single token.

e

> On Oct 16, 2016, at 9:22 AM, Neill Miller <neillm@???> wrote:
>
> Just try: bx fetch-height with no args and be sure the default config has the proper URL. And args to bx fetch-height causes connection timed out.
>
>> On October 16, 2016 11:10:14 AM CDT, Eric Voskuil <eric@???> wrote:
>> The first server is correct. I know that the second server has been down, and I would assume the third is (the unsystem listings are dated). The only question then is why you cannot reach the fourth. Neill should be able to help. I don't see anything wrong with your build or config.
>>
>> e
>>
>>> On Oct 16, 2016, at 8:20 AM, 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
>
> --
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.