I don't plan to put any node in the attic. I was talking about running ethernet cables through my attic to the different rooms in the house and how hot it will be to do that now during the summer months. Really, I guess it would be best to do it now before it is the absolute hottest days or I will have months of ethernet cables laying in my hallways.

I have recently connected a ethernet cable, but I now have a ethernet wire though my hallways..... I should run cable through the entire house one of these weekends soon... should have done this over the winter when it wasn't so hot in the attic.


I used GUI to access and edit the config file and the command was me trying to control the GUI through Windows PowerShell.

Although I have deleted everything on my external. Everything started to mess up and I became frustrated and reformatted the external hd so i could return it. figured that the files were corrupted anyways... at least that was my thinking atm I was frustrated.

I will have a new ssd soon and after the setting everything back up and redownloading the blockchain, I will post brand new ways that I screw everything up

hehe so I had another error near the end of the reindex.

it might have been my fault, idk

I had to stop the reindex and shut Bitcoin Core off. I used the Bitcoin Core console to shut it down and checked my task manager that it was good.
I didn't disconnect the external HD.

When I restarted Bitcoin Core, a tiny window popped up about "Loading Wallet" and it never went away nor did Bitcoin Core ever fully start. Eventually the "Not Responding" window appeared and yeah. This happened over and over but strangely, no bug log of it.

Sudden idea popped in my head, I still had the "-reindex" command enabled when Bitcoin Core started. I deleted the command and the wallet problem went away. However, I'm guessing, since it never fully reindexed, it was still fucked, so I restarted the reindexing.... another fatal error popped up after maybe 8 hrs or so.... in the bug log it said something about the error possibly being the reason of an "I/O" and there wasn't anything else. Bitcoin Core terminated itself after I clicked ok to the fatal error message.

I do not have a bug log to show everyone bc out of frustration I formatted the external and packed it up to return it. Figured that whatever was on the external HD was corrupted anyway and was useless to transfer to the new internal ssd I am ordering.

I'm thinking that it might just be better to return this external, and pay a bit extra for a bigger internal ssd. I'm still in my 30 day return window.

You're right, I misspoke. What happens is I lose internet connection because of my internet browser, usually from a website that is too much. I don't know if it is a wifi signal thing or if my network adapter needs to be replaced, but I guess that is the next problem I need to tackle. probably for another website forum though. idk

thanks for bringing that to my attention

I have already created a bitcoin.conf file using Bitcoin Core GUI on my external HD following the instructions from https://sparrowwallet.com/docs/connect-node.html

server=1
rpcuser=bitcoin
rpcpassword=yourpassword

[main]
rpcbind=127.0.0.1
rpcbind=192.168.0.10
rpcallowip=127.0.0.1
rpcallowip=192.168.0.0/16

I just don't know why it tries to find it in C:\Users\john\AppData\Roaming\Bitcoin\bitcoin.conf


From my other post, I was having trouble with shutting down Bitcoin Core all the way. In order to make sure that it was shut down, it was suggested to me to use CLI to make certain. So I am trying to learn how to do so I can start learning to fix my own problems.

Also, I use the same computer to run other labor intensive programs and I need to stop Bitcoin Core in order for things to run more smoothly. Once, I have an upgraded computer, then I might be able to keep it running all the time.

But you are right, I do try to make things more difficult than they should lol.

I want to contribute to the network and I read that running a full node is how I can do that. I have yet to actually use my own node for a transaction for I have only recently started this entire process. I will eventually but I guess it is best to go through all the pains now instead of worrying that I lost something from some error like this. For now I want to run a full node, even if I am not using it myself, on the external hard drive, and upgrade my internal storage when I can.

Bitcoin Client Software and Version Number: Bitcoin Core v25.0.0
Operating System: Windows 11
System Hardware Specs:
Processor - 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz   2.80 GHz
RAM - 16.0 GB
Toshiba 1 TB external hard drive

Description of Problem:

I am trying to use CLI with Bitcoin Core.

I want to do things like start/stop Bitcoin Core with CLI.

I am using the info from https://bitcoin.org/en/full-node#windows-10 to figure out the commands but I am running into problems possibly from a lack of knowledge of how to use Windows command prompt.

for example, to stop Bitcoin Core
C:\Program Files\Bitcoin\daemon\bitcoin-cli stop
but I get the message that "'C:\Program' is not recognized as an internal or external command..."

I figure that I maybe need to change the directory so I entered "cd C:\Program Files\Bitcoin\daemon\" and then enter "bitcoin-cli stop" in which i receive the message "error: Could not locate RPC credentials. No authentication cookie could be found, and RPC password is not set.  See -rpcpassword and -stdinrpcpass.  Configuration file: (C:\Users\john\AppData\Roaming\Bitcoin\bitcoin.conf)"

I do know that my config file is not in C:\Users\john\AppData\Roaming\Bitcoin\. That folder doesn't even exist. I have my data all on an external hard drive.

I am at a lost on what I need to do from here in order to use Bitcoin Core CLI.

Any Related Addresses: n/a
Any Related Transaction IDs: n/a
Screenshot of the problem: n/a
Log Files from the Bitcoin Client: n/a

Yeah, you're right. I should have invested in a bigger internal hard drive.... I can just transfer the files from my external when I get a new internal hard drive right?

I downloaded the crystaldiskinfo, but would this be something I should run while reindexing? I know that it was safe to stop my initial blockchain download, but idk if it would start over if I stop the reindex. I'm about 12% in going 3%+ /hr.

Also, I am seeing in the debug.log that every time it would try to bind to RPC on address 192.168.0.10 port 8332 it would fail. "2023-06-23T19:39:40Z Binding RPC on address 192.168.0.10 port 8332 failed."

and it shows my config files with this address:
2023-06-23T19:39:40Z Config file: D:\Bitcoin Core\bitcoin.conf
2023-06-23T19:39:40Z Config file arg: rpcpassword=****
2023-06-23T19:39:40Z Config file arg: rpcuser=****
2023-06-23T19:39:40Z Config file arg: server="1"
2023-06-23T19:39:40Z Config file arg: [main] rpcallowip="127.0.0.1"
2023-06-23T19:39:40Z Config file arg: [main] rpcallowip="192.168.0.0/16"
2023-06-23T19:39:40Z Config file arg: [main] rpcbind="127.0.0.1"
2023-06-23T19:39:40Z Config file arg: [main] rpcbind="192.168.0.10"

Did I set up my config file wrong here?

and every time is says anything about Socks5 it has a failure. "2023-06-23T08:20:36Z Socks5() connect to 2604:a880:400:d0::261f:6001:8333 failed: general failure"

again, really thanks for everyone's help.

Thanks for the shortcut tip. I've added that and have started Bitcoin Core back up. Hopefully it is reindexing.

I have my external drive on a usb port bus with an external power source to the usb bus. external drive is connected to the usb 3 port on the bus and the bus is connected to the usb 3 on my computer.
When I exit Bitcoin Core, I use the Exit option and wait for all the windows about shutting down to disappear before properly ejecting the external hard drive, always waiting for the windows message that it is safe to disconnect.

For the "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely…" yesterday, I think that is the first time that I actually disconnected my hard drive from my computer after fully downloading the entire blockchain. also ejecting safely before disconnecting.

Is there another way to know if Bitcoin Core is really shut down? Should I be inspecting my task manager to make sure?

Maybe I should connect the hard drive directly into my computer instead of through the bus. Or just never disconnect it lol.

Thanks for looking over my logs.

Bitcoin Client Software and Version Number: Bitcoin Core v25.0.0
Operating System: Windows 11
System Hardware Specs:
Processor - 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz   2.80 GHz
RAM - 16.0 GB
Toshiba 1 TB external hard drive

Description of Problem:
I am running a full node.
I changed the network settings (based off of what I found on the internet in order to use it over Tor. I was trying to do the "private" thing...) to "Connect through SOCKS5 proxy (default proxy):
Proxy IP: 127.0.0.1 Port: 9050
with IPv4 IPv6 and Tor all checked
I set the bitcoin.conf on my external hard drive to:
server=1
rpuser=abc123(not actual)
rpcpassword=******
rpcbind=127.0.0.1
rpcbind=192.168.0.10
rpcallowip=127.0.0.1
rpcallowip=192.168.0.0/16

After fully downloading the entire bitcoin blockchain to my external hard drive I connected to Sparrow wallet (V. 1.7.6) and changed the settings as stated above. I have not made any transactions.
I was connected to the network for several days.
I turned off Bitcoin Core for possibly ~8 hours and disconnected (safely) by external hard drive.
I reconnected my external hard drive and turned Bitcoin Core. Bitcoin Core started, what I presumed, to resync. The message I was provided (attached image):

(all info here is from after error message so might not be the same as started)
Number of blocks left: Unknown. Syncing Headers ((numbers),(percent)...
Last block time: Sat Jan 3 13:15:05 2009
Progress: 0.00%
Estimated time left until synced: Unknown

What was odd was that the progress never changed and everything continued to say unknown. I figured this was normal (never having run a node before), and I left it over night to "sync."
When I woke this morning and checked the progress, I was met with a "Bitcoin Core - Error" message. "Error: A fatal internal error occurred, see debug.log for details".
I have the debug.log in the link below. I have no idea what it is saying to me.

I would greatly appreciate someone enlightening me.
I really want to contribute to the Bitcoin Network.

Any Related Addresses:n/a
Any Related Transaction IDs:n/a

Screenshot of the problem:
https://imgur.com/a/hWJRlQe

Log Files from the Bitcoin Client:
(I am unsure what is relevant. I pasted what didn't seem like a lot of the same thing (even thought idk what I am looking at really))
https://pastebin.com/BUpgPVXq