Server does not respond to fetch_history2 when using cert

[hoffmabc]

We are noticing on our OpenBazaar libbitcoin nodes that they've seemed to stop responding to fetch history calls even they show in the requests log. They also respond to fetch height as well.

[evoskuil]

Does fetch-history work via bx?

[hoffmabc]

No

[evoskuil]

Glad to help but need more information.

• Can you post or send me a log covering the activity?
• Is the endpoint public, and if so can you give me that and a reproducing address?
• Is the server not responding at all, or is it an empty response?
• Is the history height configured to zero?
• Is it happening on more than one server?
• Have you restarted the server?

[hoffmabc]

I'll get you the log shortly and give you the connect info. It's not responding at all for the fetch_history2. Height is 0. It's happening on more than one server. We did not reboot the whole VPS.

[evoskuil]

Were these requests working on the same server but then stopped while it was running?

Are you getting a timeout?

If bx fetch-history is not getting a response it implies an issue with address.fetch_history (as well as address.fetch_history2). libbitcoin-client doesn't expose call to address.fetch_history2 so is it safe to assume you are using a custom client implementation?

[hoffmabc]

We are using curve keys so it's below.

libbitcoin3.openbazaar.org
pco)6}^g!]5b7#byrx>[=MCI#W?DCF}K3FoS6nTu

[hoffmabc]

Yeah we're using the python client.

[evoskuil]

port: 9091?

Also:

Were these requests working on the same server but then stopped while it was running?
Are you getting a timeout?

[hoffmabc]

yes port 9091. so just for shits and giggles I turned off encryption on that node and it works great. with the curve stuff turned on it's a no go.

[evoskuil]

So it's intermittent, as this was working earlier. Sounds like the problem you identified earlier.

[hoffmabc]

This one is a little different though. It seems to show in the logs as responding to the request (i.e. it shows fetch_history2 coming in and responding) but it never comes back to bx or the python client.

[evoskuil]

OK, is this a priority for you or can you live without the server cert for a while?

[hoffmabc]

We will have to disable encrypted libbitcoin connections for the time being which is a security threat but if it resolves the issues our software is having in the meantime we will probably resort to doing that. Do you have thoughts on what it might be?

[evoskuil]

I don't know, I haven't spent much time in this code. Do you know exactly what versions (or builds) of libzmq and czmq you are using?

Given the system is trustless, why would it be important that the client-server connection be encrypted?

[hoffmabc]

I can get you that info.

Well it would be nice to know that the results weren't tampered by anyone in the middle on the way to my OpenBazaar node. I may not trust the end server but at least I know it originated from that node. Also if you're running your own trusted node somewhere it would be hugely important.