[
https://issues.jenkins-ci.org/browse/JENKINS-12232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
francis Upton resolved JENKINS-12232.
-------------------------------------
Assignee: francis Upton (was: Kohsuke Kawaguchi)
Resolution: Cannot Reproduce
I can't make this happen with using the new API which will be available in
1.14, and I'm not sure this is a Jenkins problem to begin with. If you can make
it happen in 1.14, please provide steps and reopen.
> "hostname in certificate didn't match" when testing connection to new EC2
> cloud
> -------------------------------------------------------------------------------
>
> Key: JENKINS-12232
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12232
> Project: Jenkins
> Issue Type: Bug
> Components: ec2
> Affects Versions: current
> Environment: Jenkins 1.445, EC2 plugin 1.13
> Reporter: Craig Cottingham
> Assignee: francis Upton
> Priority: Blocker
>
> 1. Manage Jenkins
> 2. Configure System
> 3. "Add cloud" in EC2 section.
> 4. Supply region, access key ID, secret access key, and EC2 RSA private key.
> 5. Click "Test Connection".
> 6. Get this error:
> hostname in certificate didn't match:
> <us-east-1.ec2.amazonaws.com/207.171.162.73> != <ec2.us-east-1.amazonaws.com>
> OR <us-east-1.ec2.amazonaws.com> OR <ec2.amazonaws.com> OR
> <ec2.us-east-1.amazonaws.com>
> "host 207.171.162.73" resolves to "ec2.amazonaws.com".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
