{"action":"created","issue":{"url":"https://api.github.com/repos/vmware/harbor/issues/4670","repository_url":"https://api.github.com/repos/vmware/harbor","labels_url":"https://api.github.com/repos/vmware/harbor/issues/4670/labels{/name}","comments_url":"https://api.github.com/repos/vmware/harbor/issues/4670/comments","events_url":"https://api.github.com/repos/vmware/harbor/issues/4670/events","html_url":"https://github.com/vmware/harbor/issues/4670","id":314195462,"number":4670,"title":"VCH cannot communicate with VIC Default Registy - No IP SANs","user":{"login":"nojg","id":38360095,"avatar_url":"https://avatars0.githubusercontent.com/u/38360095?v=4","gravatar_id":"","url":"https://api.github.com/users/nojg","html_url":"https://github.com/nojg","followers_url":"https://api.github.com/users/nojg/followers","following_url":"https://api.github.com/users/nojg/following{/other_user}","gists_url":"https://api.github.com/users/nojg/gists{/gist_id}","starred_url":"https://api.github.com/users/nojg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nojg/subscriptions","organizations_url":"https://api.github.com/users/nojg/orgs","repos_url":"https://api.github.com/users/nojg/repos","events_url":"https://api.github.com/users/nojg/events{/privacy}","received_events_url":"https://api.github.com/users/nojg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-13T17:47:34Z","updated_at":"2018-04-13T18:46:43Z","closed_at":null,"author_association":"NONE","body":"New install of vic 1.3 appliance and VCH's.  VCH was deployed using vic-machine tool, including   --registry-ca certificate flag.  When trying to run 'docker -H _vchhostname_:2376 --tls login _vicipaddr_ I get the following error:\r\n\r\nError response from daemon: Get https://_vicip_/v2/: x509: cannot validate certificate for _vicip_ because it doesn't contain any IP SANs\r\n\r\nI downloaded the ca.crt file from the VIC management portal, but looking at the cert shows nothing in the way of hostnames or IP addresses in the subject field.  \r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/vmware/harbor/issues/comments/381227668","html_url":"https://github.com/vmware/harbor/issues/4670#issuecomment-381227668","issue_url":"https://api.github.com/repos/vmware/harbor/issues/4670","id":381227668,"user":{"login":"nojg","id":38360095,"avatar_url":"https://avatars0.githubusercontent.com/u/38360095?v=4","gravatar_id":"","url":"https://api.github.com/users/nojg","html_url":"https://github.com/nojg","followers_url":"https://api.github.com/users/nojg/followers","following_url":"https://api.github.com/users/nojg/following{/other_user}","gists_url":"https://api.github.com/users/nojg/gists{/gist_id}","starred_url":"https://api.github.com/users/nojg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nojg/subscriptions","organizations_url":"https://api.github.com/users/nojg/orgs","repos_url":"https://api.github.com/users/nojg/repos","events_url":"https://api.github.com/users/nojg/events{/privacy}","received_events_url":"https://api.github.com/users/nojg/received_events","type":"User","site_admin":false},"created_at":"2018-04-13T18:46:43Z","updated_at":"2018-04-13T18:46:43Z","author_association":"NONE","body":"Never mind, turns out this was an issue with the proxy configuration.  The VCH was set to use a proxy server however the proxy server would return a blocked page because of an internal resource.  "}}
{"actor":{"display_login":"nojg"}}