Chris Marget

Several IP addresses might map to a single MAC address (though the reverse cannot be true). Perhaps the proposed SearchByMac() function should return a slice of IP addresses (all matches...

I have a theory (argparser returns varying types depending on object count) about this error, but it's pretty much moot now: https://community.letsencrypt.org/t/2018-01-09-issue-with-tls-sni-01-and-shared-hosting-infrastructure/49996

Yes, it's the same issue. My point is, the plugin is dead. With LetsEncrypt no longer supporting TLS-SNI-01, there's nothing to fix.

This plugin. certbot-asa. It's dead.

> Any plans to update this to update this so that TLS-SNI-01 is not used? The alternatives are HTTP and DNS challenges. I don't think an ASA can respond to...

The web server used for the HTTP challenge needs to be at the same address as the thing using the certificate for TLS services. I suppose it'd be possible to...

I've not been down this road on Ubuntu. Is the `curl` test (the one without the -k option specified in the readme) working? Asking to make sure you're clear of...

The error indicates that the servers at LetsEncrypt are connecting to your ASA for validation, but it's giving them the wrong certificate. Specifically, it's returning the _management_ certificate (the trustpoint...

You'll have a window to kill the script when it says "waiting for validation" or something along those lines. That's when the validators run by the LE folks should be...

Interesting. You might be able to learn something from debugging the REST API on the ASA. The way this works is this: The temporary certificate is created by certbot code...