# Ubuntu wireguard blokada conf parsing error

**URL:** <https://community.blokada.org/t/ubuntu-wireguard-blokada-conf-parsing-error/11577>\
**Category:** Support\
**Created:** [March 9, 2021, 6:51pm UTC](https://community.blokada.org/t/ubuntu-wireguard-blokada-conf-parsing-error/11577 "2021-03-09T18:51:21Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sch](https://avatars.discourse-cdn.com/v4/letter/s/d26b3c/32.png) [@sch](https://community.blokada.org/u/sch)\
**Post date:** [March 9, 2021, 6:51pm UTC](https://community.blokada.org/t/ubuntu-wireguard-blokada-conf-parsing-error/11577/1 "2021-03-09T18:51:21Z")

</div>

Hi there!  
On a PC running Ubuntu 20.04.2 LTS, I’m trying to use Wireguard to connect to Blokada Plus VPN :

- Activated Blokada Plus service and then created and downloaded the Blokada conf file by using [app.blokada.org](http://app.blokada.org)
- Installed Wireguard on the PC and started going through the Quick Start guide on [www.wireguard.com/quickstart](http://www.wireguard.com/quickstart) : cli interface, there’s no gui in the Ubuntu version.
- First two steps ok, created a wg0 interface and assigned ip address.
- Third step is to apply the conf file to the interface, but here there’s a parsing error, it doesn’t like the Address= line for some reason, see attached screen shot.  
Could you help, please? I’m not a network guy and don’t have a lot of time to delve into the cause…  
Also a question : If Ubuntu succeeds in using Wireguard + Blokada VPN, it’s going to loose the advantage of the Pi-hole DNS filter on my home network… Is there a way to have DNS filtering in the Blokada DNS service via VPN ?  
Thanks for your help!  
Sean ![WireguardConfParsingError](https://europe1.discourse-cdn.com/flex017/uploads/blokada/original/2X/2/27e94feb647d658a1d81596986894de520968a62.jpeg)

---

<div class="post-metadata">

**Author:** ![elburg](https://dub1.discourse-cdn.com/flex017/user_avatar/community.blokada.org/elburg/32/7014_2.png) [@elburg](https://community.blokada.org/u/elburg)\
**Post date:** [March 9, 2021, 10:23pm UTC](https://community.blokada.org/t/ubuntu-wireguard-blokada-conf-parsing-error/11577/2 "2021-03-09T22:23:45Z")

</div>

Try checking for any updates by using

```bash
sudo apt update
sudo apt upgrade

```

or it may be because Linux works in a really weird way.

---

<div class="post-metadata">

**Author:** ![sch](https://avatars.discourse-cdn.com/v4/letter/s/d26b3c/32.png) [@sch](https://community.blokada.org/u/sch)\
**Post date:** [March 9, 2021, 11:30pm UTC](https://community.blokada.org/t/ubuntu-wireguard-blokada-conf-parsing-error/11577/3 "2021-03-09T23:30:35Z")

</div>

Thanks elburg for your advice. Upgraded 3 packages, but unfortunately the parsing error is still happening. The packages were libxnvctrl0, nvidia-prime and nvidia-settings, so probably not related to my problem.  
Regarding my pi-hole question, I discovered there are several publicly available pi-hole dns servers, for example [ahadns.com](http://ahadns.com) so that’s a possible solution once I get wireguard configured 🙂

---

<div class="post-metadata">

**Author:** ![sch](https://avatars.discourse-cdn.com/v4/letter/s/d26b3c/32.png) [@sch](https://community.blokada.org/u/sch)\
**Post date:** [March 10, 2021, 11:59pm UTC](https://community.blokada.org/t/ubuntu-wireguard-blokada-conf-parsing-error/11577/4 "2021-03-10T23:59:36Z")

</div>

Hi again,  
Just to let you know Wireguard is now working fine on my Ubuntu. My error was to follow the Quick Start guide on the Wireguard site. In fact it’s simpler than that: you just copy the conf file that was generated by the Blokada app website to the /etc/wireguard/ directory, and rename the conf file to wg0.conf  
Then you start the VPN tunnel with the command: wg-quick up wg0  
To stop the tunnel: wg-quick down wg0

---

<div class="post-metadata">

**Author:** ![sch](https://avatars.discourse-cdn.com/v4/letter/s/d26b3c/32.png) [@sch](https://community.blokada.org/u/sch)\
**Post date:** [March 11, 2021, 12:02am UTC](https://community.blokada.org/t/ubuntu-wireguard-blokada-conf-parsing-error/11577/5 "2021-03-11T00:02:48Z")

</div>

Oh yeah, forgot to say: I removed the ipv6 address from the conf file, that solved the parsing error. Probably not the right solution but…

---

<div class="post-metadata">

**Author:** ![RPMozley](https://dub1.discourse-cdn.com/flex017/user_avatar/community.blokada.org/rpmozley/32/11658_2.png) [@RPMozley](https://community.blokada.org/u/RPMozley)\
**Post date:** [March 11, 2021, 10:29pm UTC](https://community.blokada.org/t/ubuntu-wireguard-blokada-conf-parsing-error/11577/6 "2021-03-11T22:29:34Z")

</div>

It might have been the ipv6 address, as looking at it with the error message, it looks like a link local address and may not have been correct for your device or interface. (if I remembered that info correctly)

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/flex017/user_avatar/community.blokada.org/system/32/7003_2.png) [@system](https://community.blokada.org/u/system)\
**Post date:** [March 18, 2021, 10:30pm UTC](https://community.blokada.org/t/ubuntu-wireguard-blokada-conf-parsing-error/11577/7 "2021-03-18T22:30:29Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
