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: massdefect.org
I ran this command:
It produced this output:
My web server is (include version):Apache version 2.4.62
The operating system my web server runs on is (include version): Debian 12
My hosting provider, if applicable, is: Dyn Dns
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):Webmin
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you're using Certbot):certbot 2.1.0
I have two desktop computers, one 5 years old, the other brand new, that are both running Debian 12 both updated to the most current versions. The old machine was the original server the new machine works as a file server, webdav server and web server. Originally installed the letsencript keys on the old desktop but cant seem to get the keys transfered to the new desktop. I use DynDNS for the registered domain of: massdefect.org. the old desktop still works - I just would like the new server to act as the main server with the letsencrypt keys working. I use my router to port forward the addresses to each server as needed and use comcast as the internet provider. Again I cant seem to get the keys to work on the new server.