# X509 certificate plugin gets permission denied

**URL:** <https://community.netdata.cloud/t/x509-certificate-plugin-gets-permission-denied/807>\
**Category:** Help\
**Tags:** agent\
**Created:** [January 21, 2021, 11:16am UTC](https://community.netdata.cloud/t/x509-certificate-plugin-gets-permission-denied/807 "2021-01-21T11:16:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbarper](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/mbarper/32/2058_2.png) [@mbarper](https://community.netdata.cloud/u/mbarper)\
**Post date:** [January 21, 2021, 11:16am UTC](https://community.netdata.cloud/t/x509-certificate-plugin-gets-permission-denied/807/1 "2021-01-21T11:16:42Z")

</div>

## Environment

Ubuntu 18.04

## Problem/Question

I guess is a permission problem as the cert file I want to monitor is owned by root. So my real question/problem is, how can I handle this? It is possible to elevate permissions for the plugin to monitor owned by root certificates?

## What I expected to happen

I expect to be able to monitor any file with independence to the owner user.

---

<div class="post-metadata">

**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\
**Post date:** [January 21, 2021, 11:29am UTC](https://community.netdata.cloud/t/x509-certificate-plugin-gets-permission-denied/807/2 "2021-01-21T11:29:22Z")

</div>

Hi @mbarper

Indeed, `netdata` user has no permissions to read files owned by `root`.

I am not a specialist, but i think we had pretty similar issue with `filecheck` collector, see [Running Firefox as root in a regular user's session is not supported. ($HOME is /root which is owned by netdata.) · Issue #10205 · netdata/netdata · GitHub](https://github.com/netdata/netdata/issues/10205)

We ended up with this solution [go.d.plugin/modules/filecheck at master · netdata/go.d.plugin · GitHub](https://github.com/netdata/go.d.plugin/tree/master/modules/filecheck#permissions)

I hope it will help to resolve the problem!
