I use my Synology a long time as a reverse proxy. I would like to run Hassio on a NUC. What about the the certificates used in Hassio? They are installed on my Synology instead on the NUC, so I can use them with my reverse proxy.
Do I have to export the certificates on my Synology and place them in my /ssl/ directory? So I can use them in configuration.yaml (http section) and in the add-on’s (fullchain.pem and privkey.pem).
Could someone guide me here?
I just point it to my Raspberry Pi running Hassio that works fine 
Hassio doesn’t have to use certificates at all. Let your reverse proxy handle the certs.
Use your reverse proxy.
Oké, thanks.
Boom! Thanks this was my issue (working now), I had been trying for days to get this to work! Anyone else with Synology NAS this issue the issue you might be having.
@casperse
Can you explain how do you do it? I created a new second certificate (LetsEncrypt) for my subdomain
hassio.xxxxxx.duckdns.org in diskstation and create a reverse proxy rule + websocket entry (see image). But if I go to https://hassio.xxxxxx.duckdns.org I get a “NET::ERR_CERT_COMMON_NAME_INVALID” from chrome and after ignore it I see the login page from diskstation …
EDIT:
Now the connection works. My mistake was a old wrong port forwarding rule in my fritzbox for DS (443 -> 5001) and I always saw the 443 on the overview page. So I changed it to 443 -> 443. I add a new reverse proxy rule in DS: external 443 to 5001 (DS).
BUT I get still the cert error message 
EDIT2:
Ok I got it. See picture.
