# WinRM error: ntlm: (u'http', u'Bad HTTP response returned from server. Code 500') **URL:** \ **Category:** Ansible Project\ **Tags:** windows\ **Created:** [June 14, 2017, 10:05am UTC](https://forum.ansible.com/t/winrm-error-ntlm-uhttp-ubad-http-response-returned-from-server-code-500/24722 "2017-06-14T10:05:09Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Onallion](https://avatars.discourse-cdn.com/v4/letter/o/9e8a1a/32.png) [@Onallion](https://forum.ansible.com/u/Onallion)\ **Post date:** [June 14, 2017, 10:05am UTC](https://forum.ansible.com/t/winrm-error-ntlm-uhttp-ubad-http-response-returned-from-server-code-500/24722/1 "2017-06-14T10:05:09Z")
Hey guys, I currently have four Windows Server 2012 servers I want to manage via Ansible. On the first one, I turned off the Windows Firewall, added Ansible user as local admin, and ran the Powershell script. I can win\_ping to that one successfully and it all works fine. For the other three, I went through the exact same steps, the script completed successfully, and yet when I try to win\_ping I get: ntlm: (u’http’, u’Bad HTTP response returned from server. Code 500’) I should mention I can telnet successfully to those servers via port 5985. My configuration is as follows: ` ansible\_user: “MyAnsibleUser@MyDomain” ansible\_password: “{{ windows\_password }}” ansible\_port: 5985 ansible\_connection: winrm ansible\_winrm\_transport: ntlm #ansible\_winrm\_kerberos\_delegation: yes #ansible\_winrm\_scheme: https ansible\_winrm\_server\_cert\_validation: ignore #ansible\_winrm\_realm: [MYDOMAIN.COM](http://MYDOMAIN.COM) windows\_user: MyAnsibleUser ` As you can see I am only using ntlm and port 5985. I’ve kinda hit a dead end here - I also see no issues on the Windows Event log. I should mention these are Amazon EC2 instances, I made sure to enable port 5985 for the security group etc. Any help would be appreciated ---
**Author:** ![jborean](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jborean/32/1525_2.png) [@jborean](https://forum.ansible.com/u/jborean)\ **Post date:** [June 15, 2017, 9:59pm UTC](https://forum.ansible.com/t/winrm-error-ntlm-uhttp-ubad-http-response-returned-from-server-code-500/24722/2 "2017-06-15T21:59:03Z")
Hey Looks like you are trying to connect over port 5985 which is defaulting to [http://hostname:5985/wsman](http://hostname:5985/wsman) instead of [https://hostname:5986/wsman](https://hostname:5986/wsman) and Ansible by default doesn’t allow you to talk through HTTP unless you have disabled some security restrictions on the Windows host itself. For a bit of background the default port for the HTTP listener is 5985 while HTTPS is 5986. You can see what your host is configured with by running the following in powershell on your Windows box. `winrm enumerate winrm/config/Listener` This is the type of output you would expect from this command (note the IP/Hostname/Certificate thumbprint would be different) ` Listener Address = \* Transport = HTTPS Port = 5986 Hostname = HOSTNAME Enabled = true URLPrefix = wsman CertificateThumbprint = A377DD78797710B2E7185682BC32D9C9BE8E8B5D ListeningOn = 192.168.1.2, 127.0.0.1 Listener [Source=“GPO”] Address = \* Transport = HTTP Port = 5985 Hostname Enabled = true URLPrefix = wsman CertificateThumbprint ListeningOn = 192.168.1.2, 127.0.0.1 ` The above tells me I have a HTTP listener running and is over port 5985 while I also have a HTTPS listener running and is over port 5986. As I was saying at the start you can get Ansible to talk over HTTP but you will have to allow unencrypted messages to be received on the host. If you use HTTPS you don’t have to worry about encrypting the messages as it is done over TLS and so Ansible should work with that. Once you have verified the above and ensured you have a HTTPS listener active you will also want to modify you configuration to be something like ` ansible\_user: username@MYDOMAIN ansible\_password: “{{ windows\_password }}” ansible\_port: 5986 # Tell Ansible to use HTTPS ansible\_connection: winrm ansible\_winrm\_transport: ntlm ansible\_winrm\_server\_cert\_validation: ignore ` There were a few entries in there that are not needed for NTLM which I’ve removed. You should be able to specify the user using the UPN format ([username@REALM.COM](mailto:username@REALM.COM)) or Down Level login format (REALM\username), I usually use the down level for NTLM and UPN for Kerberos but they should be interchangable. Hopefully this helps you to get it working and understand a bit more on the transport side. Thanks Jordan ---
**Author:** ![SrinivasaRao\_Nallapa](https://avatars.discourse-cdn.com/v4/letter/s/8e7dd6/32.png) [@SrinivasaRao\_Nallapa](https://forum.ansible.com/u/SrinivasaRao_Nallapa)\ **Post date:** [January 31, 2018, 1:00pm UTC](https://forum.ansible.com/t/winrm-error-ntlm-uhttp-ubad-http-response-returned-from-server-code-500/24722/3 "2018-01-31T13:00:03Z")
Hello, Is this resolved. I am also getting same issue. Please help me . Using module file /usr/local/lib/python2.7/dist-packages/ansible-2.4.1.0-py2.7.egg/ansible/modules/windows/win\_ping.ps1 \<[KOR1074638.kor.apac.bosch.com](http://KOR1074638.kor.apac.bosch.com)\> ESTABLISH WINRM CONNECTION FOR USER: [lsl@APAC.COM](mailto:lsl@APAC.COM) on PORT 5986 TO \<[KOR1074638.kor.apac.bosch.com](http://KOR1074638.kor.apac.bosch.com)\> WINRM CONNECT: transport=ntlm endpoint=https://:5986/wsman Using module file /usr/local/lib/python2.7/dist-packages/ansible-2.4.1.0-py2.7.egg/ansible/modules/windows/win\_ping.ps1 \<10.47.115.103\> ESTABLISH WINRM CONNECTION FOR USER: lsl@APAC…COM on PORT 5986 TO 10.47.115.103 \<10.47.115.103\> WINRM CONNECT: transport=ntlm endpoint=https://:5986/wsman \<[KOR1074638.kor.apac.bosch.com](http://KOR1074638.kor.apac.bosch.com)\> WINRM CONNECTION ERROR: (u’http’, u’Bad HTTP response returned from server. Code 500’) Traceback (most recent call last): File “/usr/local/lib/python2.7/dist-packages/ansible-2.4.1.0-py2.7.egg/ansible/plugins/connection/winrm.py”, line 222, in \_winrm\_connect self.shell\_id = protocol.open\_shell(codepage=65001) # UTF-8 File “/usr/local/lib/python2.7/dist-packages/winrm/protocol.py”, line 132, in open\_shell res = self.send\_message(xmltodict.unparse(req)) File “/usr/local/lib/python2.7/dist-packages/winrm/protocol.py”, line 207, in send\_message return self.transport.send\_message(message) File “/usr/local/lib/python2.7/dist-packages/winrm/transport.py”, line 202, in send\_message raise WinRMTransportError(‘http’, error\_message) WinRMTransportError: (u’http’, u’Bad HTTP response returned from server. Code 500’) ---
**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:** [February 2, 2018, 10:21am UTC](https://forum.ansible.com/t/winrm-error-ntlm-uhttp-ubad-http-response-returned-from-server-code-500/24722/4 "2018-02-02T10:21:42Z")
What version of pywinrm are you using? 0.3.0 is released now and among other changes this version has better error reporting. Worth upgrading to 0.3.0 if you can. I have occasionally encountered this ‘Bad HTTP response returned from server: Code 500’ and in all the cases I have encountered so far either something interrupted the networking on the windows box (usually a reboot) or the machine was busy 100 % cpu utilization (almost always because it has been recompiling .net code following the release of a new .net version via windows updates). Jon