Watchtower with Gotify

[SAOPP]

Guys, I have an this stack:

version: "2"
services:
  watchtower-adguard:
    image: containrrr/watchtower:latest
    container_name: watchtower-adguard
    hostname: watchtower-adguard
    restart: unless-stopped
    command: adguard
    environment:
      - TZ=Europe/Kiev
      - DOCKER_HOST=tcp://192.168.0.19:2375
      - WATCHTOWER_DEBUG=true
      - WATCHTOWER_TRACE=true
      - WATCHTOWER_CLEANUP=true
      - WATCHTOWER_NOTIFICATIONS=gotify
      - WATCHTOWER_NOTIFICATION_GOTIFY_URL=http://192.168.0.29:6688
      - WATCHTOWER_NOTIFICATION_GOTIFY_TOKEN=AwyN9Ak44Wr7Os_
      - WATCHTOWER_NOTIFICATION_GOTIFY_TLS_SKIP_VERIFY=true

Strange, but in log I see failed shoutrrr's notify, but I don't have this service yet, and watchtower can't connect to my gotify server also, with strange issue, WATCHTOWER_NOTIFICATION_GOTIFY_TLS_SKIP_VERIFY is not working property like.

Failed to send notification via shoutrrr (url=gotify://192.168.0.29:6688/AwyN9Ak44Wr7Os_):  failed to send notification to Gotify: Post "https://192.168.0.29/message?token=AwyN9Ak44Wr7Os_": x509: cannot validate certificate for 192.168.0.29 because it doesn't contain any IP SANs,time="2021-01-16T13:35:04+02:00" level=debug,
time="2021-01-16T13:35:04+02:00" level=warning msg="Using an HTTP url for Gotify is insecure",
time="2021-01-16T13:35:04+02:00" level=debug msg="Sleeping for a second to ensure the docker api client has been properly initialized.",
time="2021-01-16T13:35:05+02:00" level=debug msg="Retrieving running containers",
time="2021-01-16T13:35:05+02:00" level=debug msg="There are no additional watchtower containers",
time="2021-01-16T13:35:05+02:00" level=debug msg="Watchtower HTTP API skipped.",
time="2021-01-16T13:35:05+02:00" level=info msg="Starting Watchtower and scheduling first run: 2021-01-17 13:35:05 +0200 EET m=+86400.427736061"

[SAOPP]

Also, my previous wt-instance work fine with gotify with the same settings.

[piksel]

You don't need the shoutrrr container at all, it's just for running shoutrrr standalone.
It's a library that is built into watchtower.

[SAOPP]

Excellent, somehow there is not enough description on this subject in the watchtower itself ... I'll go and try something.

[piksel]

You can find an example in the docs:
https://containrrr.dev/watchtower/notifications/#containrrrshoutrrr

And the telegram service info can be found in the shoutrrr documentation:
https://containrrr.dev/shoutrrr/services/telegram/

Note that channel names starts with "@", you can also supply chat IDs, but there is no good way to find what those IDs are from the usual telegram clients...

[virtualex-itv]

hello - curious if there's been any update to this as I am plagued by the same issue. Apparently, it doesn't seem like WATCHTOWER_NOTIFICATION_GOTIFY_TLS_SKIP_VERIFY=true is working correctly. I keep getting the following:

Failed to send notification via shoutrrr (url=gotify://gotify.lab.local/TOKENREMOVED):  failed to send notification to Gotify: Post "https://gotify.lab.local/message?token=REMOVED": x509: certificate signed by unknown authority

[SAOPP]

This is will be fixed in the next version of Gotify.

[simskij]

For future reference, this should be fixed by now.

Yeah, gotify only works with TLS (https) in v1.1.6 due to #767
Should be fixed in next release!