# Getting security bad md5 certificate after running configureRemotingForAnsible.ps1

**URL:** <https://forum.ansible.com/t/getting-security-bad-md5-certificate-after-running-configureremotingforansible-ps1/28329>\
**Category:** Ansible Project\
**Created:** [August 14, 2018, 4:35pm UTC](https://forum.ansible.com/t/getting-security-bad-md5-certificate-after-running-configureremotingforansible-ps1/28329 "2018-08-14T16:35:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sshort](https://avatars.discourse-cdn.com/v4/letter/s/d07c76/32.png) [@sshort](https://forum.ansible.com/u/sshort)\
**Post date:** [August 14, 2018, 4:35pm UTC](https://forum.ansible.com/t/getting-security-bad-md5-certificate-after-running-configureremotingforansible-ps1/28329/1 "2018-08-14T16:35:00Z")

</div>

Perhaps the script has changed but I ran it 8 months ago off the ansibledoc site.

Has anyone else run into this?

Anyone know how to fix it?

---

<div class="post-metadata">

**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\
**Post date:** [August 14, 2018, 4:56pm UTC](https://forum.ansible.com/t/getting-security-bad-md5-certificate-after-running-configureremotingforansible-ps1/28329/2 "2018-08-14T16:56:16Z")

</div>

If you have run before on the same box you might need use the -ForceNewSSLCert option perhaps? (just a guess, not something I’ve seen myself. If that’s not it, can you send the exact message you get?

Jon

---

<div class="post-metadata">

**Author:** ![purushotham7](https://avatars.discourse-cdn.com/v4/letter/p/7993a0/32.png) [@purushotham7](https://forum.ansible.com/u/purushotham7)\
**Post date:** [August 14, 2018, 4:57pm UTC](https://forum.ansible.com/t/getting-security-bad-md5-certificate-after-running-configureremotingforansible-ps1/28329/3 "2018-08-14T16:57:12Z")

</div>

I faced similar issues once, all our playbook are developed in 2.4 and then when we upgraded our server to 2.5 few roles failed. I assume it would be the same with your case.

---

<div class="post-metadata">

**Author:** ![Tchia04](https://avatars.discourse-cdn.com/v4/letter/t/fbc32d/32.png) [@Tchia04](https://forum.ansible.com/u/Tchia04)\
**Post date:** [August 15, 2018, 3:13pm UTC](https://forum.ansible.com/t/getting-security-bad-md5-certificate-after-running-configureremotingforansible-ps1/28329/4 "2018-08-15T15:13:11Z")

</div>

Have you tried remove the self-signed certified that is generated from configureRemotingForAnsible.ps1 and try running it again?

Tony