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. crt.sh | 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:english.readover.online
I ran this command:automatic wacs.exe
It produced this output:I dont know how to do it
My web server is (include version):.NET Core running on 64bit Amazon Linux 2
The operating system my web server runs on is (include version):Linux 2
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):I don't know
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):aws
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you're using Certbot):I have no idea
I have been using Let's Encrypt successfully on a VPS running Windows Server to manage my websites hosted via IIS. Recently, I decided to introduce a subdomain to one of my sites.
Here's the current setup:
- Primary domain: readover.online
- SSL certificate: Let's Encrypt (already in place)
- Hosting: VPS running Windows Server with IIS
- Subdomain: english.readover.online
- Hosting: AWS (.NET Core on 64-bit Amazon Linux 2)
The subdomain, english.readover.online, points to a website hosted on AWS. It has replaced the default address provided by AWS.
My question is: What is the recommended approach to secure this subdomain with Let's Encrypt? Should I run Let's Encrypt on the AWS server where the subdomain points, or is it more appropriate to run Let's Encrypt on my existing VPS where I added the A record that points the subdomain to my AWS site?
Any advice or guidance on the best course of action would be greatly appreciated.