Why is it empty when sending rpc via curl?

ABCbits

legendary

Activity: 2870

Merit: 7490

Crypto Swap Exchange

Quote from: ?? on ??

Quote from: serhack on October 10, 2022, 10:59:42 AM

--snip--

The funny thing is that I don't know where to get them from.(
IP I took from the seeds
In curl, I specify any login and password, but I don’t know where to get which one is needed (

FYI, if that node isn't owned by you or the owner doesn't give RPC credential to you, your only option is connect to that node using P2P protocol[1][2]. But you only can get limited data such as transaction, block and block header.

Quote from: DaveF on October 10, 2022, 03:01:15 PM

You also have this file generator: https://jlopp.github.io/bitcoin-core-config-generator/ I have not used it so I can't comment on how accurate it is, but I know people who have used it that say it does generate valid files.

I used it and it generate valid/accurate config file, but i used it 1-2 years ago.

[1] https://developer.bitcoin.org/devguide/p2p_network.html
[2] https://en.bitcoin.it/wiki/Protocol_documentation#Message_types

NotATether

legendary

Activity: 1568

Merit: 6660

bitcoincleanup.com / bitmixlist.org

Note that you can also rent your own Bitcoin node with JSON-RPC access from GetBlock. Never used them myself, but they seem pretty good.

DaveF

legendary

Activity: 3500

Merit: 6320

Crypto Swap Exchange

Quote from: ?? on ??

Quote from: DaveF on October 10, 2022, 12:05:53 PM

You should only talk to your own nodes through RPC. In the conf file you need to specify a user and password and IP range for RPC to talk to.

If you need to pull other information there are various services that allow for API calls, but since access to RPC more or less means you have access to the wallet that is there you are probably not going to be able to find anyplace that allows remote calls. It's just basic bitcoin security and security in general.

-Dave

Can you link to documentation and examples?

Take a look at: https://riptutorial.com/bitcoin/example/26000/node-configuration that more or less gives all the options that are available in the conf file.

You also have this file generator: https://jlopp.github.io/bitcoin-core-config-generator/ I have not used it so I can't comment on how accurate it is, but I know people who have used it that say it does generate valid files.

Keep in mind when running this against your own node that it does have to be fully synced for some things. I know some (most?) commands will not work until your node has finished the IBD and if you re-start it until it finishes whatever housekeeping it has to do at startup.

What are you trying to do anyway?

-Dave

n0nce

hero member

Activity: 910

Merit: 5935

not your keys, not your coins!

Quote from: ?? on ??

Then how to be? Out of 100 ip 6-8 ips give out 401 and the rest are not working at all

Wait, why are you trying to connect to 100 IP addresses? Did you get IP addresses of random Bitcoin nodes and try to query them? That doesn't work. Especially since they most likely do not expose their RPC interface to the internet. That would be highly insecure.

Do you even have your own Bitcoin node?

DaveF

legendary

Activity: 3500

Merit: 6320

Crypto Swap Exchange

You should only talk to your own nodes through RPC. In the conf file you need to specify a user and password and IP range for RPC to talk to.

If you need to pull other information there are various services that allow for API calls, but since access to RPC more or less means you have access to the wallet that is there you are probably not going to be able to find anyplace that allows remote calls. It's just basic bitcoin security and security in general.

-Dave

serhack

member

Activity: 107

Merit: 168

Security Researcher and Writer

Quote from: ?? on ??

Quote from: serhack on October 10, 2022, 10:59:42 AM

Quote from: ?? on ??

https://pastenow.ru/1c82e9f8c232c55ba2f7e0e8a3acbae1

Exactly, look at HTTP status code. 401 means Unauthorized, you need to supply valid username and password to be able to use RPC interface for that node.

The funny thing is that I don't know where to get them from.(
IP I took from the seeds
In curl, I specify any login and password, but I don’t know where to get which one is needed (

Why should you have the username/password if the node is not yours? Anyone can start a node, and can restrict the json API interface.

serhack

member

Activity: 107

Merit: 168

Security Researcher and Writer

Quote from: ?? on ??

https://pastenow.ru/1c82e9f8c232c55ba2f7e0e8a3acbae1

Exactly, look at HTTP status code. 401 means Unauthorized, you need to supply valid username and password to be able to use RPC interface for that node.

serhack

member