Quote from: NotATether on Today at 10:59:39 AM

Quote from: patelbhavin on Today at 10:17:19 AM

Just a small query: Why do we need it behind the webserver? From the document, I understand that the Bitcoin core full node works for syncing the blockchain with other nodes and provides one more medium for confirmation, which the Bitcoin network can use. And yes this will not be for any kind of wallet services.

Also, can you please throw some light on some documents which can make me more aware of RPC?

Among other things, Bitcoin Core does not use HTTPS, so all of the communication is, by default, exposed to third-parties. Although that part is not a big deal, there are some other reasons:

- Rate limiting, as I mentioned
- For security reasons, as a web server like Nginx or Apache is more hardened against security bugs so it can catch some of the exploits that might compromise Bitcoin Cora via the RPC port
- If you want to forward traffic to port 80

It makes it all very simple, really.

Yup, that I understood, my friend. What I am not able to understand is what RPC port you are talking about for the Bitcoin core full node server that needs to be open. As I can read on Bitcoin core documents, there is only one port that is required, which is 8333, to be open to sync and service other nodes for confirmation and transactions.