2024-06-20, 03:05 PM
That was a good idea TheDreadPirate, but unfortunately making those modifications to the Nginx config directly on Synology seems to be a no-go. That entire reverse-proxy folder structure gets re-written by the software. Doing so completely killed the services that rely on the reverse-proxy. I saved a backup of the original config so I have been able to recover via shell.
However, I did find the solution:
SOLUTION:
When you import new certificate files for a WILDCARD CERTIFICATE on a Synology NAS, you will be prompted to input three files:
Private Key:
Certificate:
Intermediate certificate (optional):
The private key and certificate are self explanatory, but when you are importing a wildcard certificate, make sure you obtain a CA Bundle from the certificate authority to import into the 'Intermediate certificate' field. I'm not completely sure what I input into that field originally, but when I obtained that 3-certificate bundle from my provider it fixed this issue. Thanks @TheDreadPirate for all your help.
However, I did find the solution:
SOLUTION:
When you import new certificate files for a WILDCARD CERTIFICATE on a Synology NAS, you will be prompted to input three files:
Private Key:
Certificate:
Intermediate certificate (optional):
The private key and certificate are self explanatory, but when you are importing a wildcard certificate, make sure you obtain a CA Bundle from the certificate authority to import into the 'Intermediate certificate' field. I'm not completely sure what I input into that field originally, but when I obtained that 3-certificate bundle from my provider it fixed this issue. Thanks @TheDreadPirate for all your help.