[GH-ISSUE #2245] Resolve Webhook sending text instead of JSON #1395

New issue

Open

opened 2026-03-02 02:22:56 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 02:22:56 +03:00

Owner

Originally created by @buuugs on GitHub (Jun 11, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2245

Server Info:

OS: Linux Tactical-RMM 5.10.0-22-amd64 #1 SMP Debian 5.10.178-3 (2023-04-22) x86_64
Browser: FireFox
RMM Version: 1.2.0

Installation Method:

Standard
Standard with --insecure flag at install
Docker

Agent Info:

Agent version: 2.9.1
Agent OS: Windows Server 2019

Describe the bug
I have noticed that there is an issue with the data format in the resolved webhook in Tactical RMM. While the error webhook works correctly and sends data in JSON format, the resolved webhook sends the body as plain text instead of JSON.

Expected behavior
I expect the resolved webhook to send data in JSON format, just like the error webhook. This would allow for consistent data handling and seamless integration with systems that expect JSON responses.

Screenshots

Same for both:

Output from error webhook:

Output from resolve webhook:

Additional context

Originally created by @buuugs on GitHub (Jun 11, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2245 **Server Info:** - OS: Linux Tactical-RMM 5.10.0-22-amd64 #1 SMP Debian 5.10.178-3 (2023-04-22) x86_64 - Browser: FireFox - RMM Version: 1.2.0 **Installation Method:** - [x] Standard - [ ] Standard with `--insecure` flag at install - [ ] Docker **Agent Info:** - Agent version: 2.9.1 - Agent OS: Windows Server 2019 **Describe the bug** I have noticed that there is an issue with the data format in the resolved webhook in Tactical RMM. While the error webhook works correctly and sends data in JSON format, the resolved webhook sends the body as plain text instead of JSON. **Expected behavior** I expect the resolved webhook to send data in JSON format, just like the error webhook. This would allow for consistent data handling and seamless integration with systems that expect JSON responses. **Screenshots** <img width="724" alt="Image" src="https://github.com/user-attachments/assets/8b4bf756-e0bc-427c-b793-64c6de63f586" /> <img width="1097" alt="Image" src="https://github.com/user-attachments/assets/881a392f-cc6a-41d2-bbf0-13c636d5e355" /> <img width="1088" alt="Image" src="https://github.com/user-attachments/assets/675718d1-30f7-4a46-828d-6d714570c690" /> Same for both: <img width="356" alt="Image" src="https://github.com/user-attachments/assets/3293b7a5-546a-4a4b-be46-e0bcf3714531" /> Output from error webhook: ![Image](https://github.com/user-attachments/assets/2e324815-4111-497e-b0b4-d430c481c7c2) Output from resolve webhook: ![Image](https://github.com/user-attachments/assets/db9e8baa-bedb-45d2-8357-5ab9f5e75472) **Additional context**

kerem commented

2026-03-02 02:22:57 +03:00

Author

Owner

@ZzBombardierzZ commented on GitHub (Jun 11, 2025):

@buuugs I had the same issue. Fix was to remove action_stdout from the resolve json.

https://discord.com/channels/736478043522072608/1346330801083514981/1350226007206002809

@ZzBombardierzZ commented on GitHub (Jun 11, 2025): @buuugs I had the same issue. Fix was to remove action_stdout from the resolve json. https://discord.com/channels/736478043522072608/1346330801083514981/1350226007206002809