Mobile Error - Cloudlfare config error I think?

Technical assistance
1

Infos:

  • Used Zammad version: Zammad version 6.4.0-1732617118.28f54743.jammy
  • Used Zammad installation type: (source, package, docker-compose, …) Package
  • Operating system: 22.04
  • Browser + version: Chrome Current

Expected behavior:

  • To work on mobile client as this snip is in the nginx config:
# action cable
  location /cable {
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header CLIENT_IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_read_timeout 86400;
    proxy_pass http://zammad-railsserver;
  }

  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_set_header X-Forwarded-Proto  $scheme;

Actual behavior:

  • connection to server lost on mobile browser
  • I am using a cloudflare tunnel to present zammad to the web.
  • Maybe a config issue?

Steps to reproduce the behavior:

  • browse to public url on phone
  • I cannot login when browsing via ip as m365 sso doesnt work
2

Zammad expects that the FQDN and HTTP type are consistent from all clients you use. You cannot have several ones. So my guess is that you have an internal FQDN configured in Zammad which (of course) miss matches from what you’re using via Cloudfare. This would explain why the callback URL of Microsoft 365 are invalid and why your websocket doesn’t work.

Also see: