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.
My domain is:ivorselby.co.uk
I ran this command:
It produced this output:
My web server is (include version): aws linux
The operating system my web server runs on is (include version): apache
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
I found it difficult to post my query, sorry, and thank you very much for your e-mail.
I have installed Let’s Encrypt on a Linux virtual machine running Apache on the Amazon Webservice system.
On a Windows 10 computer when I go to my website using Chrome or Internet Explorer all works well as expected but if I use Edge I get the following error:
Chrome works around the issue by basically redirecting you to https://ivorselby.co.uk/ instead of displaying an error page. Many other browsers will just display the error.
You should issue a new certificate for both names.
What Let’s Encrypt client are you using? What command did you run to create the existing certificate?
As an example, if you used “certbot --apache -d ivorselby.co.uk”, you could use “certbot --apache --expand -d ivorselby.co.uk -d www.ivorselby.co.uk” to replace it. Other clients should have similar options.
Thank you very much for your prompt reply, it is appreciated.
I will try your suggestions.
I plan to set up another virtual server with a different ip address to run as a mail server. I believe I can refer to it as https://ivorselby.co.uk/mail. Can I use a new letsencrypt for it?
You don’t need to in that case, as long as it’s on the same domain you should be fine. But, you would have to issue another cert if it was a subdomain or another domain, not a directory.