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:
I ran this command:
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for taskbang.com
Successfully received certificate.
Certificate is saved at: /etc/letsencrypt/live/taskbang.com/fullchain.pem
Key is saved at: /etc/letsencrypt/live/taskbang.com/privkey.pem
This certificate expires on 2023-10-07.
These files will be updated when the certificate renews.
Certbot has set up a scheduled task to automatically renew this certificate in the background.
If you like Certbot, please consider supporting our work by:
- Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate
- Donating to EFF: Support EFF's Work on Let's Encrypt | Electronic Frontier Foundation
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or 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):
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
The first site I set up was dowerhousecats.com. With a single site, never would have bumped into this issue. Upon setting up the cert for the second site, the issue presents itself.
The root IP for this is: 220.127.116.11
During the first cert installation, all HTTPS traffic began being redirected to https://dowerhousecats.com. It ignores all of my configurations.
If I visit any of these URLs, it redirects to https://dowerhousecats.com:
I did a search, but could not find anything related. If you can help, much appreciated!