having trouble with my bitcoin core node

I'm trying to get my bitcoin node running to finish downloading and validating, but it’s stuck like this for over 15 minutes. I’ve tried closing it and restarting, but no luck. My internet connection is solid. Anyone got any ideas on what could be causing this?

Please provide some detail, so other member could give more specific suggestion. You can use [READ BEFORE POSTING] Tech Support Help Request Format as reference, although i expect content of debug.log on folder where you store blockchain likely contain most helpful information. For now, have you tried very common suggestion, such as restart your computer, restart internet connection or update Bitcoin Core to latest version?

initially it started but i noticed there was no progress so i checked the peers i'm connected to and i realized it was only one peer that was there which normally used to be 10 that was  when i closed it to rerun it again and since then i have been experiencing this.

How do you close the Bitcoin core? Did you just click X to close? Have you check your disk space? If it is full it might be the cause of this issue. If not, try this basic solution: - Close it via Task Manager and restart the Bitcoin Core. - Still the same try renaming the peers.dat, close it via task manager and then rerun Bitcoin Core. If the issue still there, bring the debug.log here to troubleshoot the issue.

it worked  thank you so much locking the thread right away.

I'm just guessing here with so little information: chances are it's a firewall problem.

This Node i was running actually crashed… I guess I’ve not had the time to talk about it here it was around 40% of it download of the block before the light went off and the system also went off, and when I put  the system on it started afresh from sync the blocks headers I felt discouraged as it was actually my first time trying to be part of the network with the bad network in my country and epileptic electricity supply. I really do not know what went wrong? Could it be that the file got corrupted? What would have caused that I really want to know so that it doesn’t happen again when I want to start another one again ?

So much information that could have been posted weeks ago, when you created this topic! First: a power failure is not a computer crash. It's just that: a power failure. It can corrupt files and even your file system. If your power is notoriously unreliable, you're better off with a laptop (which comes with a built-in UPS). Is there a reason you choose Bitcoin Core? Electrum is much easier for most users.

Don't get discouraged yet, "Unknown. Syncing Headers" doesn't necessarily means that it started over. Actual syncing is when it shows the actual number of blocks to sync, you'll see lots of "blocks left" relative to the current tip if it started over. Now, if it's stuck in that syncing headers message, it means that it can't get past that part literally. You can see what's wrong in the "debug.log" file that's located in your bitcoin data directory, Default path Bitcoin Wiki: en.bitcoin.it/wiki/Data_directory#Default_Location Note: in Windows, Bitcoin Core v28.0 and above use appdata\local\bitcoin if the original default path isn't present. Open it as text and share the last few lines (check the logs' timestamps), If there's too many and you can't differentiate the sessions, you can create a fresh log file: Close Bitcoin Core.Rename the "debug.log" file to something like "debug_old.log".Start Bitcoin Core and wait until it reproduces the issue.Then open the newly created debug.log file as text and share it here using [code][/code] tags.