> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/archive/solo-stakers/operation-solo-staker/obol-dvt-explained/avado-setup/troubleshooting.md).
# Troubleshooting
## Nethermind is saying "Blocks synced: 0" so is it working?
If you're not sure that a package is working, the best place to start is to look at the logs 👀
Don't panic! While the logs may look technical, they provide very useful information that anyone can read and understand.
For Nethermind, to view the logs, navigate to the "My DApps" menu and click on the "Manage" button.
Then scroll to the very bottom of the page and you'll see the "Logs" section. If you've recently turned on your machine, you should see something like this, showing the progress of the sync.
To make it even easier to read, you can filter by the search term you want, e.g. "progress" to see how it's doing.
I'm not sure why the blocks are showing 0 synced on the Avado dashboard when it appears to be syncing in the logs, but at least by looking at the logs you can see what's actually going on.
If you don't see the progress like in the screenshots, but instead see errors, copy the error and share it with the Ether.fi or Avado support and they will be able to help further.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://etherfi.gitbook.io/etherfi/archive/solo-stakers/operation-solo-staker/obol-dvt-explained/avado-setup/troubleshooting.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
