teams webhook 403

[JPRauwolf]

Hi,
I'm trying to configure a teams webhook running on the watchtower:latest docker image.
The webhook created has the following form:
https://<organization>.webhook.office.com/webhookb2/<abc-abc-abc>@<def-def-def>/IncomingWebhook/<xxxx>/<yyyy>/<zzzz>
from the documentation I know that it should be like this:
https://<organization>.webhook.office.com/webhookb2/<group>@<tenant>/IncomingWebhook/<altId>/<groupOwner>
The first parts organization, group and tenant are obvious but I dont know how to split the <xxxx>/<yyyy>/<zzzz> parts into <altId>/<groupOwner>.
As the final URL teams://group@tenant/altId/groupOwner?host=organization.webhook.office.com has altId and groupOwner in the same order I just substituted it for the <xxxx>/<yyyy>/<zzzz> part.
That returns a 403 error.

If I try using <xxxx>/<yyyy>/<zzzz> I get a 403.
If I try only using <xxxx>/<yyyy> I also get a 403.
If I try only using <xxxx>/<zzzz> I get an error that the token is incomplete.
If I try only using <yyyy>/<zzzz> I get an error that the third token part is invalid.

I did a sanity check and using curl and the same link the webhook works.

my compose.yaml looks the following

services:
  monitor:
    image: containrrr/watchtower:latest
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - WATCHTOWER_NOTIFICATIONS=shoutrrr
      - WATCHTOWER_NOTIFICATION_URL=<url>

Is there any configuration I do wrong?
Best regards Jan Philipp

[serverleader]

same issue getting 403 here even running the binary from the CLI

[ggolebio]

In my case exactly the same, curl works fine, watchtower/shoutrrr fail:

In log i see:

level=trace msg="created Shoutrrr URL from legacy notifier" URL="teams://e46135e4-XXXX-XXXX-XXXX-34a692a9132a@38ae3bcd-9579-XXXX-XXXX-XXXX1495d55a/d39395bXXXXXXXXXbc6205e9f9a7282/93b42652-XXXX-XXXX-XXXX-2d45a4XXXXXX?color=%23406170&host=mydomain.webhook.office.com"

level=error msg="Failed to send shoutrrr notification" error="failed to send notification to teams, response status code 403 Forbidden" index=0 notify=no service=teams

[serverleader]

hey guys I forked the repo and fixed the issue to only support the new format
new guide here:
https://github.com/serverleader/shoutrrr/blob/main/docs/services/teams.md

just use my code changes from:
https://github.com/serverleader/shoutrrr/

and then the teams notification works like a charm :)

[JPRauwolf]

looks good, merge and ship it!
I'd still have to wait until the pr gets merged and watchtowerrr also updates to the new version, or is there a quick way to use a custom shoutrrr version for watchtowerrr?

[ggolebio]

Can I force watchtowerrr/shouturrr to use teams:// link preaperd by me manually and avoid parsing/preparing it automatically E.g. by WATCHTOWER_NOTIFICATION_MSTEAMS_HOOK_URL variable?

[serverleader]

@JPRauwolf I'm going to look into watchtowerrr... I have never used it before...

I fixed it so I could use it in bezsel.

henrygd/beszel#207 (comment)

[serverleader]

hey guys I made a docker image of watchtower 1.7.1 with the patched shoutrrr for the teams notification fix ...

docker pull serverleader/watchtower

https://hub.docker.com/r/serverleader/watchtower

[JPRauwolf]

Thank you very much, works like a charm with the fix,
I'll leave the issue open until #460 is merged