# Authorization Error while client - server connection

**URL:** <https://hub.mender.io/t/authorization-error-while-client-server-connection/6194>\
**Category:** General Discussions\
**Created:** [September 12, 2023, 8:56am UTC](https://hub.mender.io/t/authorization-error-while-client-server-connection/6194 "2023-09-12T08:56:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dekan](https://avatars.discourse-cdn.com/v4/letter/d/ad7895/32.png) [@dekan](https://hub.mender.io/u/dekan)\
**Post date:** [September 12, 2023, 8:56am UTC](https://hub.mender.io/t/authorization-error-while-client-server-connection/6194/1 "2023-09-12T08:56:21Z")

</div>

Hello,

I have accomplished the self hosted mender server installation.Now, I am trying to connect my beaglebone black which has Debian buster to my server. I have followed these two documentation ([Convert a Mender Debian image | Mender documentation](https://docs.mender.io/3.4/system-updates-debian-family/convert-a-mender-debian-image) and [GitHub - mendersoftware/mender-convert: An easy way to integrate the Mender client into an existing image](https://github.com/mendersoftware/mender-convert)) at the same time, and finished the client installation. Then, when I look at the mender-client.service, the output is the following

 ![2](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/d/d34f79a5d1c032af6ab0686082440cd8a1a944c7.png)

The client is running, I can see it with

 ![Ekran görüntüsü 2023-09-12 112659](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/8/83fb338fe09c68954ce5f9a5a336503278e8dedf.png)

But, it seems that there is an issue about certificate, authorization etc.I also checked this topic [Authorization Failed while connecting mender-client to the self signed mender server](https://hub.mender.io/t/authorization-failed-while-connecting-mender-client-to-the-self-signed-mender-server/5164) and applied the steps there.But, it does not give me any solution.

Could you please help me ?  
Thanks in advance.

---

<div class="post-metadata">

**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\
**Post date:** [September 12, 2023, 9:39am UTC](https://hub.mender.io/t/authorization-error-while-client-server-connection/6194/2 "2023-09-12T09:39:51Z")

</div>

Hi, to get more detailed information on your issue, I would recommend using ‘openssl s\_client’ to connect to your server and verify your certificate chain is valid and correctly configured.

[https://docs.pingidentity.com/r/en-us/solution-guides/htg\_use\_openssl\_to\_test\_ssl\_connectivity](https://docs.pingidentity.com/r/en-us/solution-guides/htg_use_openssl_to_test_ssl_connectivity)

---

<div class="post-metadata">

**Author:** ![dekan](https://avatars.discourse-cdn.com/v4/letter/d/ad7895/32.png) [@dekan](https://hub.mender.io/u/dekan)\
**Post date:** [September 12, 2023, 11:48am UTC](https://hub.mender.io/t/authorization-error-while-client-server-connection/6194/3 "2023-09-12T11:48:06Z")

</div>

Thank you first, but  
How to be sure that the certificate chain is valid ? I used  
openssl s\_client -connect hostname:port -showcerts, and this gives me 3 certificates, but I am not sure about these.

---

<div class="post-metadata">

**Author:** ![mister\_kanister](https://avatars.discourse-cdn.com/v4/letter/m/8edcca/32.png) [@mister\_kanister](https://hub.mender.io/u/mister_kanister)\
**Post date:** [September 18, 2023, 7:53am UTC](https://hub.mender.io/t/authorization-error-while-client-server-connection/6194/4 "2023-09-18T07:53:40Z")

</div>

Try the setup routine and restart the client. It seems that polling intervals are not defined as well.

```auto
mender setup \
--device-type $DEVICE_TYPE \
--server-url $SERVER_URL \
--server-cert /etc/mender/server.crt \
--config /mnt/mender/mender.conf \
--data /mnt/mender \
--demo-polling 

# Set the public key in mender.conf to verify signed artifacts
# { 
# "ArtifactVerifyKey": "/etc/mender/artifact-verify-key.pem" 
# }

```

For some reason I had to set the `--server-cert` explicitly due to certificate errors and double check your URL `--server-url` that it has `https://<domain>.com`