Can not access to zammad using FQDN

Technical assistance
1

Infos:

  • Used Zammad version: 3.3.x
  • Used Zammad installation source: (source, package, …) package
  • Operating system: Centos7
  • Browser + version: firefox 75.x

Expected behavior:

  • my fqdn works

Actual behavior:

  • I am using a private ip 10.x.x.x and my fqdn : mydomaine.x.x.x
    *I’am testing locally using hosts file
    *Now zammad works fine with my ip adresse

the error DNS_PROBE_FINISHED_NXDOMAIN keep appearing I understand that is a dns problem where is the problem?

This is my hosts file:

 10.x.x.x   mydomaine.x.x.x  mydomaine

This is nginx file:

upstream zammad-railsserver {
server 127.0.0.1:3000;
}

upstream zammad-websocket {
  server 127.0.0.1:6042;
 }

 server {
 listen 80;

# replace 'localhost' with your fqdn if you want to use zammad from remote
 server_name mydomaine.x.x.x;


# security - prevent information disclosure about server version
server_tokens off;

root /opt/zammad/public;

access_log /var/log/nginx/zammad.access.log;
error_log  /var/log/nginx/zammad.error.log;

client_max_body_size 50M;

location ~ ^/(assets/|robots.txt|humans.txt|favicon.ico) {
    expires max;
location /ws {
    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-websocket;
}

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;
    proxy_read_timeout 300;
    proxy_pass http://zammad-railsserver;

    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;
}
}

Ps: I a have restarted nginx after updating the config file

Steps to reproduce the behavior:

2

only port 80?

change your 2 proxy_set_header X-Forwarded-Proto $scheme; to proxy_set_header X-Forwarded-Proto http;

restart server then try again

3

Ensure that this local FQDN you’re playing around with is available for both: Your server and the client you’re testing with.

Keep in mind to restart nginx after wards, as it might not notice the “DNS” change from your end.

4

yes the hosts file in the client side was wrong thank you

5

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.