# Mender-connect dbus errors that "AuthenticationManager was not provided"

**URL:** <https://hub.mender.io/t/mender-connect-dbus-errors-that-authenticationmanager-was-not-provided/3143>\
**Category:** General Discussions\
**Tags:** yocto, orangepi, dunfell\
**Created:** [January 27, 2021, 8:34pm UTC](https://hub.mender.io/t/mender-connect-dbus-errors-that-authenticationmanager-was-not-provided/3143 "2021-01-27T20:34:36Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![HerrMuellerluedensch](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/herrmuellerluedensch/32/513_2.png) [@HerrMuellerluedensch](https://hub.mender.io/u/HerrMuellerluedensch)\
**Post date:** [January 27, 2021, 8:34pm UTC](https://hub.mender.io/t/mender-connect-dbus-errors-that-authenticationmanager-was-not-provided/3143/1 "2021-01-27T20:34:36Z")

</div>

Hey,  
I just upgraded mender to the latest `dunfell` release to test `mender-connect`. I configured the bare minimum which is setting the client user to a non-root user.  
The last two log messages are:

```auto
Jan 27 20:23:53 CI-570A7 mender-connect[261]: time="2021-01-27T20:23:53Z" level=warning msg="call to GetJWTToken on the Mender D-Bus API failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name io.mender.AuthenticationManager was not provided by any .service files"
Jan 27 20:23:53 CI-570A7 mender-connect[261]: time="2021-01-27T20:23:53Z" level=info msg="waiting for JWT token (waitForJWTToken)"

```

Any ideas what the error message indicates?

---

<div class="post-metadata">

**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\
**Post date:** [January 29, 2021, 7:56pm UTC](https://hub.mender.io/t/mender-connect-dbus-errors-that-authenticationmanager-was-not-provided/3143/2 "2021-01-29T19:56:06Z")

</div>

I’ve not seen anything like that myself. @kacf any ideas?

---

<div class="post-metadata">

**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\
**Post date:** [February 1, 2021, 8:01am UTC](https://hub.mender.io/t/mender-connect-dbus-errors-that-authenticationmanager-was-not-provided/3143/3 "2021-02-01T08:01:40Z")

</div>

> [@HerrMuellerluedensch](#):
>
> I configured the bare minimum which is setting the client user to a non-root user.

Do you mean that you modified the `mender-client.service` file to run the mender client under a different UID, or that you set the `User` field in the `mender-connect.conf` to a different user?

If it was the former, then I think DBus communication will not work out of the box, because you need root permissions to query the endpoint (mender-connect is querying mender-client for authentication information). Something along these lines in a `mender-client_%.bbappend` file should fix it:

```auto
do_install_append() {
    sed -i -e 's/<policy user="root">/<policy user="myuser">/' ${D}/${datadir}/dbus-1/system.d/io.mender.AuthenticationManager.conf
}

```

I didn’t test that, but hopefully you get the idea.

Also note that mender-connect will need to be run under the same UID.

---

<div class="post-metadata">

**Author:** ![HerrMuellerluedensch](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/herrmuellerluedensch/32/513_2.png) [@HerrMuellerluedensch](https://hub.mender.io/u/HerrMuellerluedensch)\
**Post date:** [February 23, 2021, 12:55pm UTC](https://hub.mender.io/t/mender-connect-dbus-errors-that-authenticationmanager-was-not-provided/3143/4 "2021-02-23T12:55:38Z")

</div>

Thanks for the hint. I tried using a non-root user but dropped back to root as the mender-connect user to avoid permission issues. Still, the error persists.

This is my `mender-connect_%.bbappend`:

```
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

SRC_URI_append = " \
    file://mender-connect.conf \
"

do_install_append() {
    install -m 600 ${WORKDIR}/mender-connect.conf ${D}${sysconfdir}/mender/mender-connect.conf
}

```

where `mender-connect.conf` is:

```
{
    "ClientProtocol": "https",
    "ServerURL": "https://hosted.mender.io",
    "User": "root",
    "Terminal": {
        "Height": 24,
        "Width": 128
    },
    "Sessions": {
      "StopExpired": false,
      "ExpireAfter": 255,
      "ExpireAfterIdle": 16,
      "MaxPerUser": 4
    }
}

```

`mender-client` works fine.  
The error stated above is followed by:

```auto
Jan 01 01:41:07 6D86AA69 mender-connect[251]: time="1970-01-01T01:41:07Z" level=info msg="waiting for JWT token (waitForJWTToken)"

```

which sounds to me like the client is working. Still, the remote terminal is not available at `hosted.mender`. Am I missing something?

---

<div class="post-metadata">

**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\
**Post date:** [February 24, 2021, 8:14am UTC](https://hub.mender.io/t/mender-connect-dbus-errors-that-authenticationmanager-was-not-provided/3143/5 "2021-02-24T08:14:46Z")

</div>

I noticed that the year in your log message is 1970. Is the time not set correctly on the device? The client will not be able to connect if the clock is wrong, because the certificate is only valid within a given time period.

---

<div class="post-metadata">

**Author:** ![HerrMuellerluedensch](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/herrmuellerluedensch/32/513_2.png) [@HerrMuellerluedensch](https://hub.mender.io/u/HerrMuellerluedensch)\
**Post date:** [March 1, 2021, 8:10pm UTC](https://hub.mender.io/t/mender-connect-dbus-errors-that-authenticationmanager-was-not-provided/3143/6 "2021-03-01T20:10:49Z")

</div>

I just revisited the problem. Turned out that I had pending client authentications. After I dismissed older ones the remote client worked using the exact configuration and recipe above.

---

<div class="post-metadata">

**Author:** ![gust1n](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/gust1n/32/1112_2.png) [@gust1n](https://hub.mender.io/u/gust1n)\
**Post date:** [March 26, 2021, 7:00am UTC](https://hub.mender.io/t/mender-connect-dbus-errors-that-authenticationmanager-was-not-provided/3143/7 "2021-03-26T07:00:50Z")

</div>

Sorry if I’m hi-jacking this thread, but I’m having the same problems, and is not fixed by the above suggestions.

It seems to be a race condition, since the mender-connect.service is started conditionally when the mender-client starts, but it seems like the mender-client doesn’t have time to get the dbus API up in time.

Manually restarting mender-connect.service works every time.

Relevant logs:  
Mar 26 06:54:47 apalis-imx6 systemd[1]: Started Mender Connect service.  
Mar 26 06:54:48 apalis-imx6 mender-connect[639]: time=“2021-03-26T06:54:48Z” level=info msg=“Loaded configuration file: /etc/mender/mender-connect.conf”  
Mar 26 06:54:48 apalis-imx6 mender-connect[639]: time=“2021-03-26T06:54:48Z” level=warning msg=“call to GetJWTToken on the Mender D-Bus API failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name io.mender.AuthenticationManager was not provided by any .service files”  
Mar 26 06:54:48 apalis-imx6 mender-connect[639]: time=“2021-03-26T06:54:48Z” level=info msg=“waiting for JWT token (waitForJWTToken)”  
Mar 26 06:54:49 apalis-imx6 mender-connect[639]: time=“2021-03-26T06:54:49Z” level=warning msg=“The server certificate cannot be loaded: no file provided”  
Mar 26 06:55:29 apalis-imx6 systemd[1]: Stopping Mender Connect service…  
Mar 26 06:55:29 apalis-imx6 systemd[1]: mender-connect.service: Succeeded.  
Mar 26 06:55:29 apalis-imx6 systemd[1]: Stopped Mender Connect service.  
Mar 26 06:55:29 apalis-imx6 systemd[1]: Started Mender Connect service.  
Mar 26 06:55:29 apalis-imx6 mender-connect[830]: time=“2021-03-26T06:55:29Z” level=info msg=“Loaded configuration file: /etc/mender/mender-connect.conf”  
Mar 26 06:55:30 apalis-imx6 mender-connect[830]: time=“2021-03-26T06:55:30Z” level=warning msg=“The server certificate cannot be loaded: no file provided”

---

<div class="post-metadata">

**Author:** ![gust1n](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/gust1n/32/1112_2.png) [@gust1n](https://hub.mender.io/u/gust1n)\
**Post date:** [March 26, 2021, 10:45am UTC](https://hub.mender.io/t/mender-connect-dbus-errors-that-authenticationmanager-was-not-provided/3143/8 "2021-03-26T10:45:48Z")

</div>

Hmm, I might have been wrong, the mender-connect outputs “waiting for jwt token” and then seems to successfully (but quietly) succeed, so now I can connect using the web UI. Must have been something else.

---

<div class="post-metadata">

**Author:** ![raza707mirza](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/raza707mirza/32/2567_2.png) [@raza707mirza](https://hub.mender.io/u/raza707mirza)\
**Post date:** [September 22, 2025, 2:45pm UTC](https://hub.mender.io/t/mender-connect-dbus-errors-that-authenticationmanager-was-not-provided/3143/11 "2025-09-22T14:45:02Z")

</div>

I faced similar issue. I did an offline installation of mender on ubuntu. Found that mender-authd.service was failing.

mender-authd was failing because configuration was not in place yet and this service was started and stopped after failing.

After doing the configuration before installation of mender-authd package resolved the issue.  
Alternatively do a restart on mender-authd.service after configuration