In case it helps anyone else, for us the issue was addressed by this from the Packer docs:
"Where Packer is configured for an outbound proxy but WinRM traffic should be direct, ssh_interface must be set to private_dns and <region>.compute.internal included in the NO_PROXY environment variable." So I had to put "ssh_interface": "private_dns", in the template, and I had to add .ec2.internal to the NO_PROXY environment variable. Sean On Thursday, September 26, 2019 at 6:50:56 PM UTC-5, Sean Nolan wrote: > > Did you ever find a reliable fix for this issue? > > Thanks > Sean > > On Wednesday, April 10, 2019 at 3:40:29 AM UTC-5, John Roh wrote: >> >> tried ssh_interface: private_ip or export >> no_proxy=localhost,169.254.169.254, us-west-1.compute.internal (described @ >> https://github.com/hashicorp/packer/issues/4857). >> So far no luck...I even defined vpc_id, subnet_id, and security_group_id >> that 5986 is opened in our existing networks since there is additional >> firewall I need to go through. >> >> >> >> On Monday, March 18, 2019 at 2:03:16 AM UTC-7, [email protected] >> wrote: >>> >>> Hi guys, >>> >>> I have the following problem already described on github: >>> >>> https://github.com/hashicorp/packer/issues/7420#issue-422085957 >>> >>> Any suggestions or missing information ? >>> >> -- 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/d8e53b62-ff03-4eb0-82ae-7374b3f7689c%40googlegroups.com.
