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: gjschaller.homeftp.net
I ran this command: certbot-auto
It produced this output:
My web server is (include version): Apache2 (included on ReadyNAS OS 6.9.4)
The operating system my web server runs on is (include version): Debian Linus (ReadyNAS OS 6)
My hosting provider, if applicable, is: (N/A)
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, cannot reach
I am running a ReadyNAS at home, which runs ReadyNAS OS 6.9.4 - basically, Debian with some modifications for the ReadyNAS hardware. A while back, I installed Let’s Encrypt without issue - at the time, I did not choose to enforce HTTPS using the Apache config.
A firmware update came out for the ReadyNAS, and I updated. This overwrote the changes, and the certificate was no longer being used. I re-ran certbot-auto, it found the old cert, and re-enabled it. So far, so good.
This time, I chose to enable the enforcement of HTTPS at the final step. When I did this, the Admin site (control panel web UI) for the ReadyNAS device broke - it’s now giving a “Too Many Redirects” error. Other sites on the device (sub-sites, such as Nextcloud) are fine, so it’s only this one site.
In theory, if I can undo the change that LE made to enforce HTTPS, the issue would be corrected, but I can’t find where this change is made. I’ve been all over my various .conf files for the sites, but no luck so far. Can someone advise where this change is made, and how best to comment it out or disable it?