bash script from automation quietly failing

[woeful jetty]

Trying to automate ssl cert renewal - the script works fine when ran manually via terminal add-on, but when trying to run it from an automation it says" Action ran successfully" but the script doesn't run.

automation:

description: ""
triggers:
  - trigger: calendar
    entity_id: calendar.calendar_my_local
    event: start
    offset: "0:0:0"
    id: trigger1
conditions:
  - condition: template
    value_template: "{{ trigger1.calendar_event.summary == 'SSL Certificate Renewal' }}"
actions:
  - action: shell_command.renew_ssl_certificate
    data: {}
mode: single```

**configuration.yaml entry:**
```shell_command:
  renew_ssl_certificate: /bin/bash /root/homeassistant/certbot/renewSSL.sh```

**bash script (anonymised):**
```#!/bin/bash

#renew certificate
certbot --manual certonly --preferred-challenges dns -d "haos.mydomain.com" --email [e-mail]

#Saving debug log to /var/log/letsencrypt/letsencrypt.log

#migrate files

cp /etc/letsencrypt/archive/haos.mydomain.com/cert1.pem /root/homeassistant/certbot/cert.pem
cp /etc/letsencrypt/archive/haos.mydomain.com/chain1.pem /root/homeassistant/certbot/chain.pem
cp /etc/letsencrypt/archive/haos.mydomain.com/fullchain1.pem /root/homeassistant/certbot/fullchain.pem
cp /etc/letsencrypt/archive/haos.mydomain.com/privkey1.pem /root/homeassistant/certbot/privkey.pem```

(file permissions should be fine)

[remote lintel]

I doubt your home assistant instance can access to root folder?

is it HAOS or docker or how are you running HA?

I think usually scripts are placed inside the /config/ folder, but not fully sure what HA can access

[woeful jetty]

haos, installed from the (vmware) .ova

[remote lintel]

HA is running in docker container, afaik and it most probably cannot access to /root

For HAOS there should be some letsencrypt addons available

https://community.home-assistant.io/t/automate-lets-encrypt-certificate-renewals/509668

[woeful jetty]

hm I just realised /root/homeassistant is a symlink (and so is /config by the way, it's basically just an alias to /homeassistant)

no clue why this tangleweb exists but I'm sure there's a good reason

I'll try moving things around

[woeful jetty]

I think the addon only works for a public IP

but I tried a few methods to getting it to work in the first place and just certboting from command line was the only one that worked

[remote lintel]

Okay, I cannot say how it should be done correctly. I'm using nginx reverse proxy to create https connection

I think it is also commonly used as addon

https://theprivatesmarthome.com/how-to/set-up-nginx-proxy-manager-in-home-assistant/

[woeful jetty]

no luck, changed the paths to /homeassistant/certbot with no change

[woeful jetty]

tried it, had some issues with that too

[proper grove]

The condition will never be true

There is no variable named trigger1

Use a script or remove the condition to get everything working first, then you can focus on the automation part of the problem afterwards

[woeful jetty]

...isn't that what the id field is supposed to do?

though I ended up just yeeting the summary part and making a dedicated calendar and using a second script that runs via ASWT to get this to work