Jump toSuggest an edit

Deploying the Zammad ticketing solution

Reviewed on 04 April 2024Published on 22 December 2020
  • compute
  • Zammad
  • ticket
  • support
  • chat
  • Elasticsearch

Zammad is an open-source helpdesk system that allows you to oversee customer interactions across various communication channels, encompassing telephone, Facebook, Twitter, chat, and emails. Notably, the software is entirely open-source and distributed under the GNU AFFERO General Public License version 3 (GNU AGPLv3).

This tutorial will guide you through the process of installing Zammad on a Scaleway Instance operating on Ubuntu 20.04 LTS (Focal Fossa). Furthermore, you will receive a brief orientation of the application.


We recommend you follow this tutorial using a Cost-Optimized Instance.

Before you start

To complete the actions presented below, you must have:

  • A Scaleway account logged into the console
  • Owner status or IAM permissions allowing you to perform actions in the intended Organization
  • An SSH key
  • An Instance, running on Ubuntu Focal Fossa (20.04 LTS), with at least 4 GB of RAM
  • A domain name pointed to your Instance

Installing Elasticsearch

Zammad requires an Elasticsearch database to increase search performance and to support advanced features like reports or searching by email attachment contents. Start by installing the Elasticsearch engine on your Instance.

  1. Connect to your Instance using SSH.
  2. Install the Elastic GPG Key to validate the packages.
    wget -qO - | gpg --dearmor -o /usr/share/keyrings/elasticsearch-keyring.gpg
  3. Install HTTPS transport to download the packages over a secure connection.
    apt install curl apt-transport-https gnupg
  4. Add the Elastic repository to the APT configuration.
    echo "deb [signed-by=/usr/share/keyrings/elasticsearch-keyring.gpg] stable main" | tee /etc/apt/sources.list.d/elastic-8.x.list
  5. Update the apt package manager and install Elasticsearch.
    apt update && apt install -y elasticsearch

    Elasticsearch comes with authentication enabled by default for improved security. After installation the autogenerated password and other information displays. Save this information as you will need it later on.

    --------------------------- Security autoconfiguration information ------------------------------
    Authentication and authorization are enabled.
    TLS for the transport and HTTP layers is enabled and configured.
    The generated password for the elastic built-in superuser is : <password>
    If this node should join an existing cluster, you can reconfigure this with
    '/usr/share/elasticsearch/bin/elasticsearch-reconfigure-node --enrollment-token <token-here>'
    after creating an enrollment token on your existing cluster.
    You can complete the following actions at any time:
    Reset the password of the elastic built-in superuser with
    '/usr/share/elasticsearch/bin/elasticsearch-reset-password -u elastic'.
    Generate an enrollment token for Kibana instances with
    '/usr/share/elasticsearch/bin/elasticsearch-create-enrollment-token -s kibana'.
    Generate an enrollment token for Elasticsearch nodes with
    '/usr/share/elasticsearch/bin/elasticsearch-create-enrollment-token -s node'.
  6. Start elasticsearch and enable the service:
    systemctl start elasticsearch.service
    systemctl enable elasticsearch.service

Installing Zammad

  1. Make sure that your system is using a UTF-8 locale, otherwise the PostgreSQL database engine installation may fail. In this tutorial we use the locale en_US.UTF-8:

    locale-gen en_US.UTF-8
    echo "LANG=en_US.UTF-8" > /etc/default/locale
  2. Install the Zammad GPG key on your system:

    curl -fsSL | \
    gpg --dearmor | tee /etc/apt/trusted.gpg.d/pkgr-zammad.gpg> /dev/null
  3. Add the Zammad repository to the apt package manager:

    echo "deb [signed-by=/etc/apt/trusted.gpg.d/pkgr-zammad.gpg] 22.04 main"| \
    tee /etc/apt/sources.list.d/zammad.list > /dev/null
  4. Update the apt package manager to activate the new repository and install Zammad:

    apt update && apt install zammad -y
  5. Configure Zammad with Elasticsearch by running the following two commands:

    zammad run rails r "Setting.set('es_user', 'elastic')"
    zammad run rails r "Setting.set('es_password', '<elastic_password>')"
    zammad run rails r "Setting.set('es_url', 'https://localhost:9200')"
    zammad run rake searchindex:rebuild

Configuring Nginx

Zammad uses the Nginx web server to serve the application. In the following step you configure the web server application and request a TLS certificate, issued by the Let’s Encrypt certificate authority, to secure the connection to between your users and agents using HTTPS. A domain name pointing to the IP address of your Virtual Cloud Instance is required for this step (A-Record).

  1. Open the Nginx configuration file, generated by Zammad, in a text editor. In this tutorial we use nano to edit the file:

    nano /etc/nginx/sites-enabled/zammad.conf

    Do not rename or move this file. Zammad will regenerate it, if the file is not available.

  2. Look out for the server { block and replace the server’s hostname localhost with your domain name. In this tutorial we use

    server {
    listen 80;
    # replace 'localhost' with your fqdn if you want to use zammad from remote
    server_name localhost;

    Once edited, save the file by pressing CTRL+O, then leave the editor by pressing CTRL+X.

  3. Reload the Nginx configuration files to activate the new configuration:

    service nginx reload
  4. Install certbot, a tool requesting the TLS certificate for the Let’s Encrypt CA and doing all the required Nginx configuration for you:

    apt install certbot python3-certbot-nginx -y
  5. Run certbot:

    certbot --nginx

    Follow the prompts and provide the requested information to certbot. Certbot will automatically request the certificate and reconfigure Nginx for HTTPS connections. For more information refer to our dedicated documentation.

Setting up Zammad

  1. Open a web browser and point it to your Zammad installation (in our tutorial:
  2. The interactive setup wizard displays. Click Setup new system to start the configuration of the tool.
  3. Enter the required information for the administrator account and validate the form by clicking Create:
  4. Enter the required information about your organization. You can upload your company logo to customize the installation. Make sure the System URL corresponds with your domain name ( in our example):
  5. Choose how you want to deliver your emails. You can either use a local mail server, installed on your instance, or use an external mailing service by using SMTP:

Enter the SMTP details of either the local MTA or the information you received from your messaging service. 6. To configure the email channel, click the Email button and enter the account POP3/IMAP information for your incoming mails.

  1. You have completed the basic installation of Zammad. The agent dashboard displays:

    Your users and agents can now communicate efficiently by email and by logging into their helpdesk interface.

Creating additional users

Currently, your Zammad application has only the admin user. In the following step we create additional accounts for users and agents.

Zammad proposes three default roles of user accounts:

  • Customer: Users who create tickets and ask for help.
  • Agent: Your agents who deal with the requests made by your customers.
  • Admin: Admin accounts have full control over the Zammad instance and can manage the system.

If required, you can create more detailed roles by adding more and allowing or disallowing features on a more finely granulated level.

  1. From the Zammad dashboard click the cogwheel icon (1) to enter the management section of the system.
  2. In the users section (2) of the management panel, click New user (3) to create a new account.
  3. Enter the account information of the new user and tick the checkbox corresponding to its role on the application. Once all information is provided, click Submit to create the new user account.

    To create a large number of user accounts, you can also use the bulk upload feature to upload a file in the comma separated values (CSV) format. It must be saved as UTF-8.

Creating additional channels

For now, your Zammad instance allows you to communicate with your users by e-mail, but the application provides a wide range of connectors to interact with your customers. You can configure modules for:

  • Twitter
  • Facebook
  • Telegram
  • Chat
  • SMS (via twilio) And much more.
  1. Click the cogwheel icon (1) to enter the management section of Zammad.
  2. Scroll down to the Channels section (2) and choose the communication channel you want to configure (3).
  3. The configuration options vary depending on the channel you want to configure.


You have configured a Virtual Cloud Instance with the Zammad ticketing solution, linked it to an Elasticserarch database and configured a secure connection to the Instance using HTTPS. You also did a short walkthrough of some features of Zammad. For more information on all features of the solution, refer to the official documentation.

Docs APIScaleway consoleDedibox consoleScaleway LearningScaleway.comPricingBlogCarreer
© 2023-2024 – Scaleway