Hello Arindam,

Did you read my post with my solution in this thread 
<https://groups.google.com/d/msg/packer-tool/MUzIHYnU-9Y/_a2_43GyAAAJ>? I 
think you should be able to develop a solution based on that. Of course, 
YMMV.

-- Khalid

On Thursday, April 19, 2018 at 1:21:15 PM UTC-4, ARINDAM HAZRA wrote:
>
> Hello All,
>
> Do we have any solution for this issue yet. I am still getting the same 
> error and not able to move ahead with AMI creation for Windows 2016 in AWS.
> My Builder and Provisioner are working fine when we don't use Proxy. But, 
> in my company all our traffic pass  through Proxy and not able to get AMI  
> created.
> Getting error :
>  [INFO] Attempting WinRM connection...
>  [DEBUG] connecting to remote shell using WinRM
>  [ERROR] connection error: http response error: 503 - invalid content type
>  [ERROR] WinRM connection err: http response error: 503 - invalid content 
> type
>
> I have tried setting Proxy in Userdata , also, I am using WinRM over HTTP.
>
> Please help!
>
> Thanks,
> Arindam
>
> On Friday, 1 September 2017 14:58:40 UTC-4, Khalid Hosein wrote:
>>
>> 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/8c0f0be7-d3c2-4499-88b8-b4a2cc7a4549%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to