Comments on How to Setup Zammad Ticketing System on Ubuntu 16.04
Zammad is an open source helpdesk/customer support system written in Ruby. It's a web-based ticketing system with many features, including support to manage customer communication over several channels like Facebook, telegram, chat, and emails. In this tutorial, we will show you how to install and configure Zammad Ticketing System using Nginx web server and PostgreSQL for the database system.
8 Comment(s)
Comments
Didint worked at all :(
followed it 2 times step by step -_-
check the zammad site, the repo is oudated.
Is it possible to run Zammad in an existing web server instance where web hosting related packages are already installed ? (ngix, postgresql , apache ).
My goal is to host the mailserver, website and zammad same server.
Replace STEP 2 with:
wget -qO- https://dl.packager.io/srv/zammad/zammad/key | sudo apt-key add -
sudo wget -O /etc/apt/sources.list.d/zammad.list https://dl.packager.io/srv/zammad/zammad/stable/installer/ubuntu/16.04.repo
For STEP 4 Replace "zammad.irsyadf.me" in the zammad.conf file with your FQDN
I also added my FQDN in /etc/hosts with loopback IP.
Worked for me.
i am stuck at step 3 when running letsencrypt certonly --standalone -d zammad.hakase-labs.coit said that port 80 is used by Nginx and temporary stop it. I did what it asked then I got dns problem looking up a for zammad.hakase-labs.co. I enable nginx and it again said that port 80 has taken by nginx. I even tried to chagne its port to 8082, however that didn't seem to work.
same Problem here. Can't get Certificate:
letsencrypt certonly --standalone -d mydomain.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for mydomain.com
Cleaning up challenges
Problem binding to port 80: Could not bind to IPv4 or IPv6.
First, use your own domain name and not zammad.hakase-labs.coit and the domain name that you use must point to the IP address of your server so that let's encrypt is able to reach it from their servers. Then you will have to stop nginx temporarily before you run the command, otherwise port 80 is used by nginx and certbot will fail.
Unfortunately, Elasticsearch is no longer running for me. However, I have other ports for http and https.
I have adjusted the following
server { listen 123; return 301 https://$host:234$request_uri; } server { listen 234 http2 ssl;}