⚠️ Please verify that your question has not already been reported
🛡️ Security Policy
📝 Describe your problem
Hello, I've been running the beta version for a while now and have been using the new Teams Webhook notifications via Power Automate workflows for a couple months with no issues. The other day I noticed my setup has been pretty quiet so I decided to test my teams notifications to learn that they are no longer working.
In the last couple weeks I upgraded from beta.0 to beta.1 and then beta.2, unfortunately without proper regression testing because I don't know if the teams notifications were working before the upgrade or not. I have since tested rolling back to beta.0 and even upgrading to the latest beta.3 but I get the exact same Axios error in each release so I am starting to think this is external to Kuma.
I've tested and confirmed the webhook URL I am using works from within the Kuma container using Curl, so reachability is OK.
Just trying to reach out and see if anyone else is having issues with their Teams Channel notifications in Kuma, specifically using the new Power Automate workflows method.
For context my workflows are setup using the default template like mentioned here:
#4934 (comment)
I am using the "Microsoft Teams" notification type. When I hit "Test" on the notification I get the following in the GUI. Container logs shows the same error.
📝 Error Message(s) or Log
Error: Error: AxiosError: Request failed with status code 400 <HTML><HEAD>
<TITLE>Request Error</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Request Error (invalid_request)</big>
<BR>
<BR>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
Your request could not be processed. Request could not be handled
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
This could be caused by a misconfiguration, or possibly a malformed request.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica" SIZE=2>
<BR>
For assistance, contact your network support team.
</FONT>
</TD></TR>
</TABLE>
</blockquote>
</FONT>
</BODY></HTML>
at Teams.throwGeneralAxiosError (/app/server/notification-providers/notification-provider.js:116:15)
at Teams.send (/app/server/notification-providers/teams.js:235:18)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Socket.<anonymous> (/app/server/server.js:1471:27)🐻 Uptime-Kuma Version
2.0.0-beta.3
💻 Operating System and Arch
Container deployment with podman
🌐 Browser
MS Edge
🖥️ Deployment Environment
Red Hat Enterprise Linux release 9.5 (Plow)
podman version 5.2.2
🛡️ Security Policy
📝 Describe your problem
Hello, I've been running the beta version for a while now and have been using the new Teams Webhook notifications via Power Automate workflows for a couple months with no issues. The other day I noticed my setup has been pretty quiet so I decided to test my teams notifications to learn that they are no longer working.
In the last couple weeks I upgraded from beta.0 to beta.1 and then beta.2, unfortunately without proper regression testing because I don't know if the teams notifications were working before the upgrade or not. I have since tested rolling back to beta.0 and even upgrading to the latest beta.3 but I get the exact same Axios error in each release so I am starting to think this is external to Kuma.
I've tested and confirmed the webhook URL I am using works from within the Kuma container using Curl, so reachability is OK.
Just trying to reach out and see if anyone else is having issues with their Teams Channel notifications in Kuma, specifically using the new Power Automate workflows method.
For context my workflows are setup using the default template like mentioned here:
#4934 (comment)
I am using the "Microsoft Teams" notification type. When I hit "Test" on the notification I get the following in the GUI. Container logs shows the same error.
📝 Error Message(s) or Log
🐻 Uptime-Kuma Version
2.0.0-beta.3
💻 Operating System and Arch
Container deployment with podman
🌐 Browser
MS Edge
🖥️ Deployment Environment
Red Hat Enterprise Linux release 9.5 (Plow)
podman version 5.2.2