Switch to Self-Hosted Mempool

[peridendes]

Good Morning.

I've been getting a lot of connection errors, and I would like to use my self-hosted instance of mempool.space to avoid rate limits.

I would like to use my self-hosted mempool.space to get the LastBlock and MempoolFees.

I've updated the code to use https://blockchain.info/ticker for the price, which works fine, but I replaced mempool.space with https://192.168.0.123:4081/api/blocks/tip/height I'm getting connection error. Same thing with https://192.168.0.123:4081/api/v1/fees/recommended. Both of these API work in a web browser on my computer, and I'm not sure why I'm seeing Connection Error for both on the OrangeClock after uploading the changes.

Additionally, it would be nice to have these updates as a backup or using mempool.space as a backup so I have two sets of APIs I can use in the even that I hit rate limits.

[marc3linho]

Same issue, on my side 👎
I'll take a look at that

[epiccurious]

How long were you running OrangeClock before mempool.space started rate limiting you? I've been running it for about 24 hours and haven't seen any issues, but will leave it running indefinitely.

Regarding the API endpoints not working in the script despite working on the browser, this could be related to a missing/invalid certificate on your self-hosted mempool server. Have you gone through the process of generating a self-signed certificate?

[peridendes]

I plugged the OrangeClock in yesterday at block 828122 and noticed the Connection Error - Error - Connection Error screen 18 hours later. I connected the OrangeClock to a 2.4GHz guest network thinking that might help but started seeing connection error - error - connection error within a half hour.

I can't remember if I setup up a self-signed certificiate or not. I've "decommissioned" my previous node setup and haven't gotten around to setting up a self-hosted instance of mempool on my new build. I'll look into getting that and the certificate done in the next 24 hours and report back.