Set the Elasticsearch server address

[thomas2139]

@Phillip

I installed an SSL certificate after the installation and now I get the following message:

{"error": "Unable to process GET request to elasticsearch URL 'http: // localhost: 9200 / zammad_production_ticket / _doc / _search'. Elasticsearch is not reachable, probably because it's not running or even

In case it helps anyone: That error also occurs when there is not enough RAM available (and Elasticsearch didn’t start because of this).

I installed Zammad on a virtual server with 2 GB RAM (here they mention that as a min., and why not try it: How to Install and Configure Zammad Ticketing System on Ubuntu |).

After letting Certbot change my Apache configuration I thought that may have messed up the http connection to Elasticsearch.
This helped to think about the RAM:

Unable to process GET request to elasticsearch URL 'http://localhost:9200'

Found and Fixed my Issue. Turns out my VM while set to Dynamic RAM was not upping the available RAM for Elasticsearch to work properly. After I changed the minimum ram to 4GB I know have the ticket system up and running with reporting working.

After rescaling the Server to 4 GB RAM it worked to start and connect Elasticsearch.

@MrGeneration
It may sound stupid, but maybe you could add a warning to the documentation (Set up Elasticsearch — Zammad System Documentation documentation) that Elasticsearch really needs 4 GB RAM to even start. Cause the error messages don’t mention the RAM problem. And people who just want to set up a test machine may try it with the smallest/cheapest virtual server.