> For the complete documentation index, see [llms.txt](https://service.block-pro.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://service.block-pro.net/mainnet/celestia/troubleshooting.md).

# Troubleshooting

**Mainnet** · Chain ID `celestia`

| Symptom                               | First check                                                                       |
| ------------------------------------- | --------------------------------------------------------------------------------- |
| Wrong chain or genesis error          | Verify genesis chain\_id is celestia; do not reuse the other network's data.      |
| gRPC connection refused               | Confirm application gRPC is enabled and the host, port and TLS mode match.        |
| Bridge cannot find old blocks         | Use an archival consensus source with the required historical coverage.           |
| Service keeps restarting              | Read the first error in journalctl; check binary path, user and file permissions. |
| catching\_up is false but no progress | Compare block timestamps and height with an independent, current source.          |
| Snapshot database error               | Stop the node and check app version, backend and archive layout.                  |
| Insufficient fees                     | Recheck the endpoint's current fee policy and the gas-price denomination.         |
| Full command is unavailable           | Follow the release-specific migration path; do not reuse the store as a bridge.   |

## Ask for help

Include the network, node type, binary version and the relevant error lines. Remove recovery phrases, private keys and authentication tokens before sharing logs.

[Contact BlockPro](https://t.me/BLOCK_PR0) · [Celestia troubleshooting](https://docs.celestia.org/operate/maintenance/troubleshooting/)