-
When trying to configure the sending of e-mail in watchtower I get the error:
When I try to send the same via the shoutrrr container, it seems to add a starttls option in the URL it shows. With starttls=No it does not work. If I include startls=Yes in the URL, it does work!
The configuration in docker-compose for watchtower looks like:
Using -- debug does not help, it does not show additional information in watchtower. To make it even curiouser: it is probably a networking problem. The above docker compose file does not work. The below docker run command does work. Watchtower sends an e-mail when started up via docker run.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Encryption is by default set to |
Beta Was this translation helpful? Give feedback.
Encryption is by default set to
auto
which by default means ExplicitTLS (using StartTLS) except for port 465 (which tends to be used for Implicit TLS), or ifstarttls=no
is passed.If you start watchtower with the
--trace
flag, you can see in the log exactly what URL the legacy notification handler converts your e-mail variables into. You can also just put that URL into the environment variableWATCHTOWER_NOTIFICATION_URL
and setWATCHTOWER_NOTIFICATIONS
toshoutrrr
for complete control over the config.