Problem solved, worst part was I posted the solution in my opening post. Ofc its important to place the code at the right place…
bastienroussel was using apache, I’m using nginx so I fist tried to convert it to nginx and it was the 2nd time that X-Forwarded-Ssl on;
was part of a fix for a similar error. So I continued my search…
Topics with 422 fixes with X-Forward-SSL:
Solution:
I pasted
proxy_set_header X-Forwarded-Ssl on;
Under server { } in /etc/nginx/sites-available/zammad.conf
But It should have been placed under location { } in /etc/nginx/sites-available/zammad.conf
This is the code I have in my zammad.conf file.
location / {
proxy_set_header Host $http_host;
proxy_set_header CLIENT_IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_read_timeout 180;
proxy_pass http://zammad;
#FIX FOR ERROR 422 on Chrome/Firefox > 69
proxy_set_header X-Forwarded-Ssl on;
gzip on;
gzip_types text/plain text/xml text/css image/svg+xml application/javascript application/x-javascript application/json application/xml;
gzip_proxied any;
}