# Umbrel stuck in sync state still after reinstalling os and trying other troubleshooting

**URL:** <https://community.umbrel.com/t/umbrel-stuck-in-sync-state-still-after-reinstalling-os-and-trying-other-troubleshooting/5351>\
**Category:** Support and Troubleshooting\
**Created:** [December 22, 2021, 9:41pm UTC](https://community.umbrel.com/t/umbrel-stuck-in-sync-state-still-after-reinstalling-os-and-trying-other-troubleshooting/5351 "2021-12-22T21:41:18Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jonsyu](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/jonsyu/32/1803_2.png) [@jonsyu](https://community.umbrel.com/u/jonsyu)\
**Post date:** [December 23, 2021, 8:18pm UTC](https://community.umbrel.com/t/umbrel-stuck-in-sync-state-still-after-reinstalling-os-and-trying-other-troubleshooting/5351/2 "2021-12-23T20:18:39Z")

</div>

Hey @PumbrelWumbrel, sorry to hear about the stall (actually had a similar issue myself recently), curious if you’re able to get some logs for us to look at - curious to see whether the sync is actually happening on the backend (in which case you might just need to wait).

Probably could use both the general debug logs, and also the bitcoin-specific logs:  
docker-compose logs --tail=300 bitcoin

> [@How to Generate Debugging Logs](http://community.umbrel.com/t/how-to-generate-debugging-logs/5110):
>
> There are a variety of logs that provide useful information on your Umbrel machine. In every case, we need you to copy the log entries and input them into an online service like [0bin](https://0bin.net/) (set the expiration to 1 month) or [pastebin.com](https://pastebin.com/), which will provide a link that you can share. If you are able to log into Umbrel through a browser Logs are available under Settings-\>Troubleshooting. Please note that it may take a moment to output all the logs. [image] [image] If you are unable to log into Umbr…

---

_[View the full topic](https://community.umbrel.com/t/umbrel-stuck-in-sync-state-still-after-reinstalling-os-and-trying-other-troubleshooting/5351)._
