I used notepad++ and that app worked fine once I verified it was set to EOL conversion of unix LF. It will screw up the line feeds and the synology will have issues running it. Oh and if using windows DON'T USE NOTEPAD to edit the script. I don't think you can run this task without root (which synology sets by default as the user for tasks), because I think only root can get access into that cert archive folder, though I'm not an expert. I've set mine to run daily (it won't do anything until it picks up a new cert when the lets encrypt renews), and I added some bits to make sure it generates more outputs if I need to go look at the script outputs. Of course match that to your synology folder location and script name. The task info under the run command user defined script will look something like:īash /volume1/synostuff/scripts/import-syno-cert-script.sh I put in comments to call attention to those variables.Ĥ) Also verify your GITLAB_NAME is correct to match the name of that docker instance for jacobalbery unifi though if everything was setup as default it probably does.ĥ) Throw the script somewhere accessible on the NAS and then make a synology task in task scheduler (in synology control panel) to run it. I've not tested it with the synology lets encrypt GUI process because I wanted a wildcard, so I manually used the acme.sh process.Ģ) Make sure to edit the GITLAB_CERT_DIR value to match yours (CASE matters here! If you get it wrong it won't work properly)ģ) Edit the HOSTNAME value to match yours.

Here's my working script below.ġ) Note that this script assumes you've run the acme.sh stuff to get a let's encrypt cert already and it's showing properly in the synology certificates list. I first started with the tweaks he mentioned then ended up taking it further.

Then I found I had to tweak the script given above by one-eyed-king.

Adguard home synology