Timeout Error with Raspberry Pi about btc-rpc-explorer

[PatrickZGW]

Thank you very much, this solved the issue for me.

[dawiepoolman]

I have the same setup and I also get timeouts when trying to connect to my RPi3 from my laptop.
The timeout messages occur when I run on my laptop:
npm start

[dawiepoolman]

I have also tried changing the bitcoin port to 8333 in credentials.js (instead of the 8332 as the default) but no luck yet. I doubt it can be a timeout because of speed. It might be related to rpc credentials/config..

[dawiepoolman]

My bad. Seems like 8332 is reserved as the rpc port for bitcoin. We might have to give it explicit firewall access on the RPi..

[PatrickZGW]

It does work for me if I select /peers for example. I think it is just a timeout error with the requests module of nodejs

[dawiepoolman]

I have managed to run it by referencing my full node on my laptop but I cant seem to get it running when pointing to the RPi LAN IP and rpc credentials of the pi. I have also explicitly gave only my laptop LAN ip access through my Pis firewall but no joy.

I think you are right that it is highly likely to be the request.js module somewhere around line 843 being too aggressive with the timeout logic.

[gdassori]

The RPC timeout is quite strict. I would love to customize it. Thanks.

Edit:
Found how to do it, this may help with timeouts in raspberry:
It is expressed in milliseconds, increase it and should work.

btc-rpc-explorer/app.js

Line 92 in 8588c56

timeout: 5000