{"action":"created","issue":{"url":"https://api.github.com/repos/ebekker/ACMESharp/issues/120","repository_url":"https://api.github.com/repos/ebekker/ACMESharp","labels_url":"https://api.github.com/repos/ebekker/ACMESharp/issues/120/labels{/name}","comments_url":"https://api.github.com/repos/ebekker/ACMESharp/issues/120/comments","events_url":"https://api.github.com/repos/ebekker/ACMESharp/issues/120/events","html_url":"https://github.com/ebekker/ACMESharp/issues/120","id":147043302,"number":120,"title":"Submit-ACMEChallenge : Unable to update challenge :: Challenge data was corrupted","user":{"login":"zawsx","id":6049993,"avatar_url":"https://avatars.githubusercontent.com/u/6049993?v=3","gravatar_id":"","url":"https://api.github.com/users/zawsx","html_url":"https://github.com/zawsx","followers_url":"https://api.github.com/users/zawsx/followers","following_url":"https://api.github.com/users/zawsx/following{/other_user}","gists_url":"https://api.github.com/users/zawsx/gists{/gist_id}","starred_url":"https://api.github.com/users/zawsx/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zawsx/subscriptions","organizations_url":"https://api.github.com/users/zawsx/orgs","repos_url":"https://api.github.com/users/zawsx/repos","events_url":"https://api.github.com/users/zawsx/events{/privacy}","received_events_url":"https://api.github.com/users/zawsx/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-04-08T21:26:25Z","updated_at":"2016-04-11T14:47:34Z","closed_at":null,"body":"First tried DNS challenge but Cloudfare would not accept: \r\n_acme-challenge.www.example.com \r\nas the txt record name - keeps truncating it to:\r\n_acme-challenge.www\r\n\r\nFiled a support ticket with cloudfare.\r\n \r\nSo I switched to the http method:\r\n**Submit-ACMEChallenge dns1 -ChallengeType http-01**\r\n\r\nwhere **dns1** is www.example.com\r\n\r\nProduced this red text:\r\n\r\nSubmit-ACMEChallenge : Unable to update challenge :: Challenge data was corrupted\r\nAt line:1 char:1\r\n+ Submit-ACMEChallenge dns1 -ChallengeType http-01\r\n+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n    + CategoryInfo          : InvalidData: (ACMESharp.Vault.Model.IdentifierInfo:IdentifierInfo) [Submit-ACMEChallenge\r\n   ], AcmeWebException\r\n    + FullyQualifiedErrorId : urn:acme:error:malformed (400),ACMESharp.POSH.SubmitChallenge\r\n\r\n\r\nI then tried to create a cert for the apex:\r\n**Submit-ACMEChallenge dns2 -ChallengeType http-01**\r\nwhere **dns2** is example.com\r\n\r\nThat works fine with the http method.\r\n\r\nI read that, if you try both dns and http methods, this error happens - is that true?\r\nAlso read about mime types, mine are text/plain and, as example.com verifies, so that can't be it.\r\nIs there a way to delete both www.example.com challenges and start again?\r\n"},"comment":{"url":"https://api.github.com/repos/ebekker/ACMESharp/issues/comments/208381735","html_url":"https://github.com/ebekker/ACMESharp/issues/120#issuecomment-208381735","issue_url":"https://api.github.com/repos/ebekker/ACMESharp/issues/120","id":208381735,"user":{"login":"zawsx","id":6049993,"avatar_url":"https://avatars.githubusercontent.com/u/6049993?v=3","gravatar_id":"","url":"https://api.github.com/users/zawsx","html_url":"https://github.com/zawsx","followers_url":"https://api.github.com/users/zawsx/followers","following_url":"https://api.github.com/users/zawsx/following{/other_user}","gists_url":"https://api.github.com/users/zawsx/gists{/gist_id}","starred_url":"https://api.github.com/users/zawsx/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zawsx/subscriptions","organizations_url":"https://api.github.com/users/zawsx/orgs","repos_url":"https://api.github.com/users/zawsx/repos","events_url":"https://api.github.com/users/zawsx/events{/privacy}","received_events_url":"https://api.github.com/users/zawsx/received_events","type":"User","site_admin":false},"created_at":"2016-04-11T14:47:34Z","updated_at":"2016-04-11T14:47:34Z","body":"Thanks for taking the time to explain - really appreciate it. \r\n\r\nIt's not a bug then but maybe it's worth the client highlighting the error trap, as you say, using the same alias for two different challenge types is illegal and defeated me, idiot that I am.\r\n\r\nSomething like 'each challenge type on the same domain requires a unique alias'\r\nOr maybe if the client auto-appended the challenge-type internally to the alias, as in dns1-http01 or somesuch?\r\n\r\nThanks again."}}