Infos: Used Zammad version: 7.2.2-1791798728.24a62d0.ubuntu24 Used Zammad installation type: package Operating system: Ubuntu 24.04.5 LTS Browser + version: Microsoft Edge 155.0.4283.45 Expected behavior: Tickets can be created and saved, and existing tickets can be updated. Actual behavior: Tic…

Hi, i can confirm this issue, we are on 7.2.2 now and ticket creation no longer works for users that come over Azure Application Proxy.

[image] Zammad 7.2.1 behind Nginx Proxy Manager: signin returns 422 and WebSocket fails with 502 despite correct HTTPS headers. Technical assistance Infos: I am not a support or hosted customer. I am an open-source user running Zammad in a self-managed Docker …

Hello, thank you. As I understand it is the same root cause. Is it a bug or is it related to a wrong configuration at our site? I checked the post and tried to get all the details to make sure the configuration is correct. Both settings, the http_type is HTTPS as well as the FQDN is the same as…

It’s normal that it’s running via an Nginx proxy, but the configuration needs to match. You should check if the https/fqdn inside the browser is matching with Zammad and the other palces.

Hello everyone, I have checked the configuration and cannot find any errors. To verify the problem, I installed the application on our Nginx proxy and reconfigured some test clients to connect through it. The problems we were having with the Microsoft App Proxy have disappeared. I think it is no…

Hi @maurice , thanks for testing it with your own Nginx, that narrows it down a lot. Since 7.2.1, the WebSocket connection of the browser authenticates with the session cookie, and Zammad only accepts that cookie when the Origin header of the WebSocket request matches your configured Zammad URL (ht…

We will try to make the test as soon as possible.

Hello, I reconfigured the nginx config as described. The output of the logfile 27/Oct/2026:12:50:27 +0100 123.123.123.123 origin="-" host="``company-zammad.intern.company.de``" session_cookie=present 27/Oct/2026:12:51:31 +0100 123.123.123.123 origin="-" host="``company-zammad.intern.company.de``…

Problem creating tickets through Microsoft AppProxy since Update 7.2.2

Technical assistance

dominikklein October 13, 2026, 1:41pm 3

It’s related to an security issue → fix, the origin is now checked for the old websocket server (which is already the case for the new one).