Zammad Mobile View - Failure

[zammad-friend]

Infos:

• Used Zammad version: 6.4.1
• Used Zammad installation type: docker-compose
• Operating system: linux
• Browser + version: mobile phone browser (chrome)

Expected behavior:

• create ticktes in mobile view and use mobile view

Actual behavior:

• don’t works

Steps to reproduce the behavior:

• when I use the site on my PC browser it works perfectly.
  If I use it on the mobile phone, the login works fine, but then I get “Network connection lost” in the view and in the log of zammad then appears zammad-railsserver-1 ERROR – : Failed to upgrade to WEbSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: Upgrade, HTTP_UPGARDE:)

[ecomsilio]

Have you checked this?

New Major Release: Zammad 6.0!

Manual Update Action Required by the Administrator
When updating to Zammad 6.0 from a previous version, the system administrator needs to add some content to the configuration of the reverse proxy.

Example for Apache:
ProxyPass /cable ws://127.0.0.1:3000/cable

Example for nginx:
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;
}

This is required to enable the new Rails Action Cable based realtime communication. You can find more details about this change at this github commit.

[zammad-friend]

Hello ecomsilio,
I did not do an upgrade but from scratch with docker compose up -d.
Your mentioned changes are already in the last version from my point of view.
on my verison it is already configured under /etc/nginx/sites-enabled/default.

what would be the correct way to fix this error with docker compose?

I have done a test with a VM and the error does not occur there

here is a picture of the error when i call it up on mobile

[MrGeneration]

Same issue like this thread technically:

CSRF token verification failed! Fresh install

Used Zammad version: Latest Used Zammad installation type: Build From Repository Operating system: Windows server 2022 Browser + version: Edge + Chrome Expected behavior: To be able to logn Actual behavior: Once i have finished the install, i am logged in. However, once i logout and want back in i get the CSRF token verification failed! Steps to reproduce the behavior: Tried reinstalling, but it keeps happening.

[zammad-friend]

@CSRF token verification failed! Fresh install

Used Zammad version: Latest Used Zammad installation type: Build From Repository Operating system: Windows server 2022 Browser + version: Edge + Chrome Expected behavior: To be able to logn Actual behavior: Once i have finished the install, i am logged in. However, once i logout and want back in i get the CSRF token verification failed! Steps to reproduce the behavior: Tried reinstalling, but it keeps happening.

I only have the problem when I want to use mobile on phone or tablett.
also with the test http://myzammadinstance.tld/mobile produces the same error
Using it on the PC works without any problems

[MrGeneration]

@zammad-friend

Using it on the PC works without any problems

No, the websocket won’t work still.

[zammad-friend]

@MrGeneration

No, the websocket won’t work still.

Perhaps I expressed myself incorrectly before.

I have a setup with zammad as Docker compose that has the error when I access it via mobile.

another setup with ubuntu 24.04 apache2 and zammad does not have this error when I access it via mobile.

[zammad-friend]

who can provide me with updates on this?

[MrGeneration]

This is a community forum without any guruanteed help or answer time. Please be patient.

If you require commercial grade responses and speed, consider a support contract.

[zammad-friend]

Update from my site:

only when I use a mobile phone or for testing or “https://myinstance.tld/mobile” in the desktop browser do I get the error

in the zammad-railserver-1 console logs i can see this entry:

E, [2025-01-30T16:30:07.004093#1-253120] ERROR – : Failed to upgrade to WebSocket (REQUEST_METHOD: GET, HTTP_CONNECTION: Upgrade, HTTP_UPGRADE: )

on the zammad nginx container i can see this in the log:

• • [30/Jan/2025:16:26:00 +0100] “GET /cable HTTP/1.1” 404 14 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36”

When I log in on my mobile device, it works without any problems, but there is nothing else I can do. neither create a ticket

[zammad-friend]

@ecomsilio yes, but i didn’t do an update but started over and used the latest docker-compose

[zammad-friend]

Hi Community,

yesterday i have tested a new setup with docker-compose.
i have changed in den docker-compose.yml file the Version from
6.4.1-29 to 6.4.1-32 and another test to 6.4.1-41 but allways the same failure.

What could be the error?
Does anyone have any ideas?

[Lucas-Bryant]

I’ve run into similar problems with Zammad’s mobile view when using a docker-compose setup. The login usually works, but afterwards the WebSocket upgrade can fail depending on the server configuration or proxy settings. On desktop browsers it works fine, but on mobile browsers it sometimes triggers the “Network connection lost” error you mentioned.

I’m also looking into how to optimize the website overall so it performs better on mobile devices, not just for Zammad but for the full user experience. Has anyone found a reliable fix for WebSocket handling in mobile environments, or tips on improving website performance alongside it?