Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
My web server is (include version): nginx/1.14.0 (Ubuntu)
The operating system my web server runs on is (include version): Ubuntu 18.04.2 LTS
My hosting provider, if applicable, is: AWS
I can login to a root shell on my machine (yes or no, or I don’t know): Yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.31.0
If it’s the Apache authenticator, I would really like to get some more details because people keep having an error like this and helpful forum participants keep successfully getting the users to switch over to the webroot authenticator (with no opportunity for us to figure out why the Apache authenticator fails this way!).
I don’t think medvoice.ca is using the Nginx server.
medvoice.ca is using Amazon CloudFront and the Server header says the backend is running on S3. And it’s using a valid ACM certificate, not a Let’s Encrypt certificate.
Since you do not need the medvoice.ca SSL certificate on your nginx server (because Cloudfront/ACM cover it for you), you could just redefine the certificate to only include www.medvoice.ca.