Hello, I'm building Windows AMIs in AWS, and am having trouble connecting via WinRM to Win 2012 and 2016 versions. However, the same configs work for Win 2008 R2.
When I enabled Packer debugging, I see the following errors (repeated until it hits the *winrm_timeout*): 2017/09/01 18:18:19 packer: 2017/09/01 18:18:19 [ERROR] connection error: http response error: 503 - invalid content type 2017/09/01 18:18:19 packer: 2017/09/01 18:18:19 [ERROR] WinRM connection err : http response error: 503 - invalid content type (BTW, searching for these errors either associated with 'winrm' and/or 'packer' does not return much. I also have a sense that the 'invalid content type' message is returned from Go.) Running packer build using Linux' strace didn't produce anything valuable. When the temporary instance boots, I can connect successfully to the WinRM port including using the *_pywinrm_* library to create a session using the credentials in my JSON config, so I know that my user data script is successfully enabling WinRM and setting the credentials. Is there something in particular that changed since Windows 2008? Is there a neat way to capture the WinRM commands/traffic that Packer is sending/receiving? Thanks! -- Khalid -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/dc92c327-457f-43f3-bcd1-c56a0d215c39%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
