Closed wycl16514 closed 7 months ago
because Ordhook can't use a https endpoint, therefore I used nginx as proxy, 47.128.200.237
You should be able to use https 🤔 What do you see?
hi,@lgalabru , if we use https endpoint, ordhook will show http transport erorr 400, that's because rust-bitcoinrpc crat can't support https. By the way, do you know why we stuck in there without receiving any data notification? Thanks alot.
I think it is not yet ready with syncing with blockchain? I see at your log that it is only at block 78017 (that is a long long time ago).
I did start ordhook 2 days ago. and it just indexed a block from 2021.
it should use a bootstrap. but I see https://archive.hiro.so/mainnet/ordhook/mainnet-ordhook-sqlite-latest is empty.
I see there is a https://archive.hiro.so/mainnet/ordhook/mainnet-ordhook-sqlite-latest.tar.gz do we need to set this url? will try this later today.
@blieb new snapshots are ready, you should be able to use them to shortcut the initial indexing.
Feel free to re-open this issue with more logs and more details if you're still struggling with the setup!
dear friends:
I am new to ordhook and trying ordhook to stream ordinal activities to my endpoint, I used a CHAINSTACK endpoint, and following is my Ordhook.toml:
because Ordhook can't use a https endpoint, therefore I used nginx as proxy, 47.128.200.237 is the ip of my nginx server. I used the following command to start the service:
ordhook service start --post-to=http://localhost:3000/api/events --config-path=./Ordhook.toml
and the service stuck in the following state and without sending any data to my endpoint:
I guest the problem lies in the field bitcoind_zmq_url = "tcp://IP:PORT", I saw from the doc that, this field is set to tcp://0.0.0.0:18543, which means the bitcoin node should locate at the same machine as ordhook, but I don't have a full bitcoin node in my local and I have to use a remote bitcoin service.
Do you know what's my problem, how can I fix that, I am highly appreciate your help, thank you very much.