# Counterparty problem in the local

**URL:** <https://forums.counterparty.io/t/counterparty-problem-in-the-local/6193>\
**Category:** Counterparty\
**Created:** [August 25, 2021, 3:06pm UTC](https://forums.counterparty.io/t/counterparty-problem-in-the-local/6193 "2021-08-25T15:06:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sangaria](https://avatars.discourse-cdn.com/v4/letter/s/59ef9b/32.png) [@sangaria](https://forums.counterparty.io/u/sangaria)\
**Post date:** [August 25, 2021, 3:06pm UTC](https://forums.counterparty.io/t/counterparty-problem-in-the-local/6193/1 "2021-08-25T15:06:24Z")

</div>

Hello dear.

I set up my own Counterparty “Federated Node” system, on Ubuntu20.04.  
As all requirements Hardware / OS requirements.  
But I have got some problems.  
I tried with the guide [https://counterparty.io/docs/federated\_node/](https://counterparty.io)

1. Bitcoin is syncing now from `fednode tail bitcoin-testnet`  
but I don’t find /root/.bitcoin/testnet3/blocks/index .  
How do I know the sync progress?

2. I have run `fednode exec bitcoin-testnet bitcoin-cli getpeerinfo`  
Then I have got this error.  
error: Could not connect to the server 127.0.0.1:8332  
Make sure the bitcoind server is running and that you are connecting to the correct RPC port.

3. I have got this result from `fednode tail counterpaty-testnet`.

 ![Screenshot from 2021-08-25 13-34-01](https://canada1.discourse-cdn.com/flex004/uploads/counterpartytalk/original/2X/a/ae23bfdf18a2c43b358cbd8066987e581490699f.png)

Is right?  
Someone please help on this.

---

<div class="post-metadata">

**Author:** ![jdogresorg](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/jdogresorg/32/1349_2.png) [@jdogresorg](https://forums.counterparty.io/u/jdogresorg)\
**Post date:** [September 10, 2021, 8:57pm UTC](https://forums.counterparty.io/t/counterparty-problem-in-the-local/6193/2 "2021-09-10T20:57:05Z")

</div>

the fednode install documentation clearly states that first Bitcoin has to sync… then addrindexrs has to sync… THEN counterparty will sync.

My gut says you didn’t read the documentation online and are expecting addrindexrs (backend) to be up immediately, which is not the case

Please review and read ALL of the documentation at [Running a Node | Counterparty](https://counterparty.io/docs/federated_node/)