Topic: Bitcoin node issues (Read 233 times)

It's because whatismyip shows your public IP (which given by your ISP). ipconfig command and website (such as whatismyip) show different kind of IP. But surely you know when to use local or public IP.

Off the top of my head, I would have a watch only wallet on the game server so it can see what transactions come in.
I would then have the server generate a list of the transactions that must go out. The server with the wallet queries an API on the game server that gives it s list of addresses and amounts to be paid. Which you can then verify and send.

With your method, there would be no human intervention. So if the game server gets compromised, the person who does it has full access to the wallet since they are on the accepted IP of your node and have it's RPC username and password.

There are other better, more secure ways but to start this is still way more secure then what you are doing.

-Dave

I did a fresh install and was able to install just bitcoind. So no more GUI, I added the directory through the command line pointed to the bitcoin folder on my ssd.

Ok, i will add the data dir to the config file and give it a shot.  Thanks


I'ts strange because when I look up my IP on a site like whatismyip it shows up with another IP and not the one on my ipconfig command, not sure what would be causing that. I do know that ipconfig wouldnt lie and would show the real ip, so i will stick with the ip from ipconfig. Thanks


Yes the node is in my house
Server is in friends house in same city close by.
Yes people will be playing on server in friends house and that server will be connecting to my server with bitcoin node.

I am def looking into using tor now to help with security, but i feel like i will have to learn this first thing before the tor aspect comes in.
Ok, for port forwarding to same ports.

1, is there a way to keep this the same?
2. Yeah i just checked and my ip (with node) already has been changed in the last day.
3. whats the safe way? tor?


We are experimenting and learning as we go, I was eventually thinking of throwing all of this up on a dedicated server, the main site on one server and the node on another. Yes its complex but in my thinking is that it will help if the server is hacked, i rather the main site be hacked then the site and node at the same time.
Whats a more secure way your thinking of storing the money?

Any reason you have the machines in 2 separate locations? It's adding complexity and lowering security.
For small amounts it's probably not that big a deal, but if you are ever storing a significant amount of funds you probably want to do it in a more secure way.

-Dave

I don't think dynamic IP is an issue here, if so then using DDNS would solve the issue as well. The local IP assignment can be changed to be static and it usually doesn't really change so the port forwarding sticks.

---

For starters, 8333 is the wrong port. You are looking to access your RPC from outside your LAN, which requires you to portforward your RPC port, which should be 8332 by default. You don't need to accept incoming connections for your RPC usage.

Just to verify:
The BTC node is in your house.
The server that people will be playing on is in another house.
People will be plating on the other server, which will at times connect to the node at your house to send / receive BTC.

If you are not going to be using a VPN / TOR or anything else that provides security for this setup then you are going to have to use the public IP of the server that people are playing on. And you will have to as others have said forward the public port of your router to the port & ip of the machine that your node is on.
Keep in mind the following.
1) Most home internet providers use DHCP so both your public IP and your friends public IP will change
2) If your server is getting DHCP from your router then if the PC or router reboots you may get a different IP.
3) Opening up ports like this is insecure.

-Dave

IP shown by ipconfig is your local IP (which given by your router).

That's because the start parameter you added to bitcoin-qt wont be used by bitcoind or you're using it with default start parameters.
You mentioned that you've used the GUI to set the custom data directory.

Anyway, to make a global default, add datadir=YOUR_SSD_DATA_DIR to your "bitcoin.conf" file in the default data directory.
If you don't have a bitcoin.conf file there, create one.

Default bitcoin datadir: https://en.bitcoin.it/wiki/Data_directory#Default_Location

Ok, i did a fresh install of ubuntu, was able to install bitcoind successfully. I got in the cli.

Learning how to open up my port 8333 on my router. Issue with this is that ipconfig is showing a different IP address then whatismyip.
So when i insert my ipconfig IP on my router it goes through but nothing is happening. I also let bitcoin core run for over 10 minutes. https://bitnodes.io/#join-the-network is also showing a different IP address.
I opened the port on my router with the ipconfig IP and bitnodes cannot reach it either but there is activity happening on the bitcoin core.


another issue is that I have my blockchain downloaded on my ssd drive, i do the bitcoin-cli datadir to it, it connects but bitcoincore is still downloading the blocks to my home folder. I am unsure how to stop this other download.

RPC is by default only enabled within your local network. If you want to expose it over the internet, then you can port forward it. Fair warning though, be prepared for scripts hammering your RPC logins once you expose it. I would recommend you setting up a VPN instead.

You can specify your own RPC port, but it is usually 8332 by default. Port forward that on your router, then give your friend your IP and port.

ok so still having issues.

I installed bitcoin core with snap,

I have my blockchain downloaded on an ssd, so I routed the bitcoin core gui to read from the ssd, it connected and synced and is running.

i created the config file in the home directory and added the lines ETFbitcoin wrote. I was able to get my public ip4 ad ip6, not sure which one i need to give my friend.

server=1
rpcuser=your_username
rpcpassword=your_password
rpcallowip=1.2.3.4

do i create a username and password here in the config file? or is there a command that needs to be done to create the username and password?

the rpcallowip is my public ip?

it seems like my bitcoin core gui is not picking up the config file correctly.

also when i run this command in the ubuntu terminal
bitcoin-core.cli -rpcuser=your_username -rpcpassword=your_password getnetworkinfo

it shoots this out, not sure what im looking at here 

{
  "version": 220000,
  "subversion": "/Satoshi:22.0.0/",
  "protocolversion": 70016,
  "localservices": "0000000000000409",
  "localservicesnames": [
    "NETWORK",
    "WITNESS",
    "NETWORK_LIMITED"
  ],
  "localrelay": true,
  "timeoffset": 0,
  "networkactive": true,
  "connections": 10,
  "connections_in": 0,
  "connections_out": 10,
  "networks": [
    {
      "name": "ipv4",
      "limited": false,
      "reachable": true,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "ipv6",
      "limited": false,
      "reachable": true,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "onion",
      "limited": true,
      "reachable": false,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "i2p",
      "limited": true,
      "reachable": false,
      "proxy": "",
      "proxy_randomize_credentials": false
    }
  ],
  "relayfee": 0.00001000,
  "incrementalfee": 0.00001000,
  "localaddresses": [
    {
      "address": "2600:1012:b015:c695:1111:111:11b8:40ca",
      "port": 8333,
      "score": 1
    },
    {
      "address": "2600:1012:b015:c695:72e9:1111:111:1111",
      "port": 8333,
      "score": 1
    }
  ],
  "warnings": ""
}


Thanks for all your help guys/gals and for being patient. Its a completely new language for me.

Also afaik you may need to have port forwarding (for the RPC port) set correctly (in your router), else you will remain unreachable.

RPCs should ideally not be exposed to the internet, nor should it be unsecured. The RPC within Bitcoin Core is not encrypted, so it would be a better to run a network tunneling, ie. VPN to your friend's computer.

For RPC username/password, you're supposed to configure it manually from bitcoin.conf or as parameter when you launch Bitcoin Core. Here's an example for bitcoin.conf, where rpcallowip is used to protect your node from brute-force attempt.


As for your node IP address, it should be IP given by your ISP. To verify whether it works, restart your Bitcoin Core and run this command.

Bitcoin Client Software and Version Number: 22.0 bitcoin core installed from snap
Operating System: Ubuntu 20.04.3 LTS
Description of Problem: Unable to get into bitcoind cli and obtaining info

I am creating an small game site with one game so far, im working with a friend in the same city but the development server is in his house, im looking to run the bitcoin node from my house.
we are trying to set up the rpc connection to process the small transaction going into and from the gamers wallets from the games and their external btc wallets, everything is pretty much setup but i am not able to find my nodes ip address and user name and password. Ive been searching for hours on how to get this info but nothing is popping up. I know its something super easy (maybe). Well thanks for the help, would love to get this going.