# Unicode-objects must be encoded before hashing

**URL:** <https://forum.ansible.com/t/unicode-objects-must-be-encoded-before-hashing/25824>\
**Category:** Ansible Project\
**Created:** [October 25, 2017, 8:44pm UTC](https://forum.ansible.com/t/unicode-objects-must-be-encoded-before-hashing/25824 "2017-10-25T20:44:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Laurent\_Goussard](https://avatars.discourse-cdn.com/v4/letter/l/eb8c5e/32.png) [@Laurent\_Goussard](https://forum.ansible.com/u/Laurent_Goussard)\
**Post date:** [October 25, 2017, 8:44pm UTC](https://forum.ansible.com/t/unicode-objects-must-be-encoded-before-hashing/25824/1 "2017-10-25T20:44:53Z")

</div>

My brand new ARM server, freshly installed refuse to be managaed by ansible.

As soon as I try to reach it, here is the error I get back :

`ansible chronos -m ping -u root -k SSH password: chronos.du-jour.fr | UNREACHABLE! => { "changed": false, "msg": "Unicode-objects must be encoded before hashing", "unreachable": true }Saisissez le code ici...`

I use ansible 2.4 :

`

```auto
ansible 2.4.0.0
  config file = /Users/loranger/.ansible.cfg
  configured module search path = [u'/Users/loranger/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/Cellar/ansible/2.4.0.0/libexec/lib/python2.7/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 2.7.14 (default, Sep 25 2017, 09:54:19) [GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37)]

```

`

My other servers answers flawlessly, but not this one.  
Did I miss something ?

---

<div class="post-metadata">

**Author:** ![tkuratom](https://avatars.discourse-cdn.com/v4/letter/t/b19c9b/32.png) [@tkuratom](https://forum.ansible.com/u/tkuratom)\
**Post date:** [October 25, 2017, 9:18pm UTC](https://forum.ansible.com/t/unicode-objects-must-be-encoded-before-hashing/25824/2 "2017-10-25T21:18:21Z")

</div>

We’ll need more information than this, I’m afraid. I don’t see anything in the information so far given that would explain what’s happening. What are some differences between the machine that’s most like this one and the one having problems?

---

<div class="post-metadata">

**Author:** ![Laurent\_Goussard](https://avatars.discourse-cdn.com/v4/letter/l/eb8c5e/32.png) [@Laurent\_Goussard](https://forum.ansible.com/u/Laurent_Goussard)\
**Post date:** [October 26, 2017, 12:17pm UTC](https://forum.ansible.com/t/unicode-objects-must-be-encoded-before-hashing/25824/3 "2017-10-26T12:17:34Z")

</div>

Thank you Toshi

I’m sorry, but I haven’t got a lot of informations :

My new server is an ARM based one, with a fresh debian 8 installed whereas the other ones are x86 running debian 8 too (but are already ansible’ provisioned).  
That’s the only difference I could notice. The host is the same (OVH). Maybe the new server is using ipv6 whereas the other are ipv6 ready only, I have to check this.

---

<div class="post-metadata">

**Author:** ![Laurent\_Goussard](https://avatars.discourse-cdn.com/v4/letter/l/eb8c5e/32.png) [@Laurent\_Goussard](https://forum.ansible.com/u/Laurent_Goussard)\
**Post date:** [October 26, 2017, 1:41pm UTC](https://forum.ansible.com/t/unicode-objects-must-be-encoded-before-hashing/25824/4 "2017-10-26T13:41:33Z")

</div>

It seems Ansible (via Paramiko) [has issues](https://github.com/paramiko/paramiko/issues/1039) with ED25519 SSH keys.  
I temporarily disabled mine and it now works…