# Default error at fednode install full master **URL:** \ **Category:** Support\ **Created:** [March 3, 2019, 6:40am UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386 "2019-03-03T06:40:45Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![jeroensbel](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jeroensbel](https://forums.counterparty.io/u/jeroensbel)\ **Post date:** [March 3, 2019, 6:40am UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/1 "2019-03-03T06:40:46Z")
Hi, first post: I am doing a, fednode install full master on Ubuntu1604. First error in fednode.py was the logname which I changed to whoami. Next error is the following: Traceback (most recent call last): File “/usr/lib/python3.6/configparser.py”, line 1138, in \_unify\_values sectiondict = self.\_sections[section] KeyError: ‘Default’ During handling of the above exception, another exception occurred: Traceback (most recent call last): File “/usr/local/bin/fednode”, line 464, in main() File “/usr/local/bin/fednode”, line 291, in main build\_config = config.get(‘Default’, ‘config’) File “/usr/lib/python3.6/configparser.py”, line 781, in get d = self.\_unify\_values(section, vars) File “/usr/lib/python3.6/configparser.py”, line 1141, in \_unify\_values raise NoSectionError(section) configparser.NoSectionError: No section: ‘Default’ I did a search and someone had the similar in ´16 but no resolution, any one? TY:v:👉💪🙏 ---
**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:** [March 4, 2019, 5:57pm UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/2 "2019-03-04T17:57:26Z")
You might want to update your ubuntu version. I am running Ubuntu 18.04 with no issues. ---
**Author:** ![jeroensbel](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jeroensbel](https://forums.counterparty.io/u/jeroensbel)\ **Post date:** [March 11, 2019, 6:34pm UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/3 "2019-03-11T18:34:56Z")
Great,I will use 1804 then. TY ---
**Author:** ![jeroensbel](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jeroensbel](https://forums.counterparty.io/u/jeroensbel)\ **Post date:** [April 18, 2019, 4:14am UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/4 "2019-04-18T04:14:00Z")
Okay updated to 18.04 but how do I update Bitcoin core to v17.1? I cp all blockchain data from a fully synced v17.1 node to the /volumes/federatednode\_bitcoin-data/\_data/ folder and I keep getting a reindex message in the log. ---
**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:** [April 18, 2019, 4:43am UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/5 "2019-04-18T04:43:45Z")
Bitcoin 0.17.1 isn’t officially supported on Counterparty yet… but I’ve been running it for a month or so with no issues. you can edit `federatednode/extras/docker/bitcoin/Dockerfile` to replace the following lines : ```auto # install bitcoin core ENV BITCOIN_VER="0.17.1" ENV BITCOIN_FOLDER_VER="0.17.1" ENV BITCOIN_SHASUM="53ffca45809127c9ba33ce0080558634101ec49de5224b2998c489b6d0fc2b17" ``` then run `fednode rebuild bitcoin` ---
**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:** [April 18, 2019, 4:46am UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/6 "2019-04-18T04:46:32Z")
> [@jeroensbel](#): > > I keep getting a reindex message in the log Yes, the blockchain data format changed slightly in 0.17.1 so 0.16.3 can’t read the block data. ---
**Author:** ![jeroensbel](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jeroensbel](https://forums.counterparty.io/u/jeroensbel)\ **Post date:** [April 18, 2019, 4:47am UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/7 "2019-04-18T04:47:24Z")
> [@jdogresorg](#): > > ENV BITCOIN\_VER=“0.17.1” ENV BITCOIN\_FOLDER\_VER=“0.17.1” ENV BITCOIN\_SHASUM=“53ffca45809127c9ba33ce0080558634101ec49de5224b2998c489b6d0fc2b17” Jip, thats why I asked, thank you for your fast replies. ---
**Author:** ![jeroensbel](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jeroensbel](https://forums.counterparty.io/u/jeroensbel)\ **Post date:** [April 18, 2019, 5:09am UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/8 "2019-04-18T05:09:58Z")
> [@jdogresorg](#): > > fednode rebuild bitcoin yesss, working. On to the next one. TY Ps: are you one of the coders of counterparty or a “poweruser”? 🕶 ---
**Author:** ![jeroensbel](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jeroensbel](https://forums.counterparty.io/u/jeroensbel)\ **Post date:** [April 18, 2019, 5:25am UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/9 "2019-04-18T05:25:00Z")
Inb4 I tried to change the fednode-bitcoin.conf so it could use my running 17.1 node as that is serving my external wallets, LND and are fully synced. But the docker containers have an iptables/UFW issue. They do not want to talk to the node on the host. I am building a full counterparty stack with my running bitcoin node, Lightning node, BTCpayserver and some minor other additions. As the docker - UFW issue is stopping me from connecting to my running node, I now use the Counterparty bitcoin node and will see if I can connect with LND, etc. Any ideas suggestions how to solve the container issue or what am I doing wrong? is it even an issue? TY ---
**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:** [April 18, 2019, 5:43am UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/10 "2019-04-18T05:43:25Z")
> [@jeroensbel](#): > > Ps: are you one of the coders of counterparty or a “poweruser”? 🕶 I am not a counterparty coder, I have written some Counterparty Improvement Proposals (CIPs), the [xchain.io](http://xchain.io) block explorer, and some other misc Counterparty projects, but I don’t actually work on the python codebase. As far as the docker communication issues, I am not really a big docker user, so probably best to ask someone like @chiguireitor who has more experience with docker. It might be something simple like exposing a port via the `EXPOSE` keyword in the dockerfile. ---
**Author:** ![jeroensbel](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jeroensbel](https://forums.counterparty.io/u/jeroensbel)\ **Post date:** [April 18, 2019, 5:47am UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/11 "2019-04-18T05:47:08Z")
Okay, good to know. So you have built the full counterparty stack from source without the dockers? ---
**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:** [April 18, 2019, 5:58am UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/12 "2019-04-18T05:58:53Z")
I have not. I tend to stick with fednode build process as it greatly simplifies the building/updating process. ---
**Author:** ![jeroensbel](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jeroensbel](https://forums.counterparty.io/u/jeroensbel)\ **Post date:** [April 18, 2019, 6:07am UTC](https://forums.counterparty.io/t/default-error-at-fednode-install-full-master/5386/13 "2019-04-18T06:07:59Z")
Right, I see I assumed wrongly that “I am not really a big docker user” meant you where not using the Counterparty dockers at all. My bad.