Cant create new ticket on mobile view

Technical assistance
1
  • Used Zammad version: 6.5.0
  • Browser + version: Chrome. Safari

image
image472×1024 53 KB

On mobile view, when creating a new ticket show me this error: “Error: the ticket could not be created.”. Tried on iOS Chrome, and Safari

2

Your websocket connection does not work. This has been posted dozen of times already in the past. Ensure that your virtual host file does meet the requirement, you can find the upstream versions here: nginx; apache2.

Should you use two proxies in a row, adjust the first proxy accordingly.

If all that doesn’t add up, you may want to provide much more input than you did.

The current Zammad version is 6.5.2 which fixes some delicate security issues.

3

Hello again¡

I have this docker container:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c2ad8a5b8e44 ghcr.io/zammad/zammad:6.5.0-75 “/docker-entrypoint.…” 2 days ago Up 44 minutes 0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp zammad-docker-compose-zammad-nginx-1
be4fe82710d8 ghcr.io/zammad/zammad:6.5.0-75 “/docker-entrypoint.…” 2 days ago Up 44 minutes zammad-docker-compose-zammad-websocket-1
32437323f0b5 ghcr.io/zammad/zammad:6.5.0-75 “/docker-entrypoint.…” 2 days ago Up 44 minutes zammad-docker-compose-zammad-railsserver-1
b8896efb79bc ghcr.io/zammad/zammad:6.5.0-75 “/docker-entrypoint.…” 2 days ago Up 44 minutes zammad-docker-compose-zammad-backup-1
894ed33cf02e ghcr.io/zammad/zammad:6.5.0-75 “/docker-entrypoint.…” 2 days ago Up 44 minutes zammad-docker-compose-zammad-scheduler-1
471098d139e4 postgres:17.5-alpine “docker-entrypoint.s…” 2 days ago Up 44 minutes 5432/tcp zammad-docker-compose-zammad-postgresql-1
e48636132009 bitnami/elasticsearch:8.18.0 “/opt/bitnami/script…” 2 days ago Up 44 minutes 9200/tcp, 9300/tcp zammad-docker-compose-zammad-elasticsearch-1
2ee1e9abb978 memcached:1.6.38-alpine “docker-entrypoint.s…” 2 days ago Up 44 minutes 11211/tcp zammad-docker-compose-zammad-memcached-1
09aca0140cf8 redis:7.4.3-alpine “docker-entrypoint.s…” 2 days ago Up 44 minutes 6379/tcp zammad-docker-compose-zammad-redis-1
f64b35cf786d jc21/nginx-proxy-manager “/init” 2 days ago Up 44 minutes 0.0.0.0:80-81->80-81/tcp, [::]:80-81->80-81/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp zammad-docker-compose-nginx-proxy-manager-1

And i have this document in sites-enabled in the container nginx called default:

this is an example nginx config for Zammad

Please visit https://docs.zammad.org for further input on how to configure

your nginx to work with Zammad

This is a NON SSL configuration, DO NOT use in production!

upstream zammad-railsserver {
server 127.0.0.1:3000;
}

upstream zammad-websocket {
server 127.0.0.1:6042;
}

server {
listen 8080;
listen [::]:8080;

replace ‘localhost’ with your fqdn if you want to use zammad from remote

server_name _;

security - prevent information disclosure about server version

server_tokens off;

root /opt/zammad/public;

access_log /dev/stdout;
error_log /dev/stdout;

client_max_body_size 50M;

location ~ ^/(assets/|robots.txt|humans.txt|favicon.ico|apple-touch-icon.png) {
expires max;
}

legacy web socket server

location /ws {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “Upgrade”;
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;
proxy_read_timeout 86400;
set $zammad_websocket_url http://zammad-websocket:6042; proxy_pass $zammad_websocket_url;
}

action cable

location /cable {
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “Upgrade”;
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;
proxy_read_timeout 86400;
set $zammad_railsserver_url http://zammad-railsserver:3000; proxy_pass $zammad_railsserver_url;
}

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;

# Change this line in an SSO setup
proxy_set_header X-Forwarded-User "";

proxy_read_timeout 300;
set $zammad_railsserver_url http://zammad-railsserver:3000; proxy_pass $zammad_railsserver_url;

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;

}
}

I dont know how can i resolv this.

Thank you for your reply.