# Could not activate remote peer.

**URL:** https://discourse.pi-hole.net/t/could-not-activate-remote-peer/28652
**Category:** Help
**Created:** [February 23, 2020, 11:38pm UTC](https://discourse.pi-hole.net/t/could-not-activate-remote-peer/28652 "2020-02-23T23:38:10Z")
**Posts on this page:** 1
**Showing post:** 39

<div class="post-metadata">

### Author: ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)
#### Post date: [February 25, 2020, 3:43pm UTC](https://discourse.pi-hole.net/t/could-not-activate-remote-peer/28652/39 "2020-02-25T15:43:36Z")

</div>

> [@docbill](#):
>
> That is almost never the right things to do, since this is a file managed by Network Manager. So in Fedora 31,

Doc, your configuration is full of suprises you are revealing to us only piece by piece: 🥳  
A separate `dnsmasq` instance, `libvirt`, a VPN of undisclosed provenience, SELinux, and now `NetworkManager` and a probably not yet supported Fedora release... 🤔

Any more surprises, and I am going to call it a premature xmas 🎄😉

@devs: Any chances to have the template ask for some of the basics that would reduce our guesswork, for future topics?

`NetworkManager` is another tool that starts its own `dnsmasq` by default.  
Your `netstat -nltup` shows a `dnsmasq` intance running alongside `pihole-FTL`, which may still lead to conflicts. I think the link I provided above contains some details on how to disable that for NM (towards the end).

I agree that this is likely not the cause for _Could not activate remote peer_, but I suspect `resolv.conf` to be involved in this as well.

A multitude of network daemons may be using that file, including but not limited to `systemd-resolvd`, `NetworkManager` and `dhclient`, as may Pi-hole v4 during installation (but that should be confirmed by a dev).

Have you probed into my hint at verifying that `systemd-resolved` is up and running yet?

---

_[View the full topic](https://discourse.pi-hole.net/t/could-not-activate-remote-peer/28652)._