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: mightyfortress.ddns.net
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version): Synology 6.2.4 to Win 10 Home
My hosting provider, if applicable, is:
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):
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
I was running my apps on Synology under Docker, and had everything set up and working. I'm moving them to a Win 10 Home box. I have searched around a little, but I'm not seeing how to redirect/transfer my incoming secure requests to my new Windows box. I do know how to forward the incoming ports to the correct IP address with my router. But, to my superficial understanding, without the certificate set up on the Windows box, that's only one piece in the puzzle?
Do I just remove the certificates from my Synology control panel and set up my Windows machine as if it's a brand new Let's Encrypt installation? If so, does anyone have a HOWTO/tutorial address handy?
Alternatively, is there a way to let the secure request go ahead and hit the Synology, and it then strips the encryption and redirects everything to/from the Windows IP address?
I'm fine, either way. Going directly to the Windows box is probably the most flexible, going forward. Fewer dependencies.