On a related note: maybe try just tweaking the existing setup to use `ansible_winrm_message_encryption=never` on your Windows host(s) in the inventory or via `-e` to prove if it's related to the new message encryption support. You've clearly been running unencrypted in the past- we'll leave the discussion of that being a good idea for another thread ;) but disabling message encryption that way should put you back to exactly the way it was working before.
-Matt On Wednesday, February 28, 2018 at 12:51:49 PM UTC-8, Jordan Borean wrote: > > Are you able to try port 5986 and see if that works. Potentially port 5985 > is failing because the encryption process is creating a bad request causing > the 400 but it would be good to know if your setup works with HTTPS where > WinRM encryption isn't happening. > > Thanks > > Jordan > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/20465b88-74f6-4123-8244-d3b86f599895%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
