Could this be an alternative to OSTicket?
I hope so, I think this looks better and can do more. If you don’t want to install it yet you can create a free account at https://zammad.com/getting-started although saying that it’s easy enough to install.
You may have to open ports:
Maybe you want to test the apache virtualhost reverse proxy instead of nginx:
Looking forward to your results…
Thanks for that I tried using RewriteEngine On
ProxyPass / http://helpdesk.ibrokeit.me:5000/
ProxyPassReverse / http://helpdesk.ibrokeit.me:5000/ but I have an issue at the moment with elastic search breaking the setup
Thought this might help if you’re trying it https://github.com/zammad/zammad/blob/develop/contrib/apache2/zammad_ssl.conf
Ticket-system on NethServer?
I tested it and it seems to work basically.
Just use the docs but only the following paragraphs, you won’t need to disable selinux & firewalld, it’s done already on Nethserver.
Because zammad requires nginx I used my nginx module which sets up nginx without using port 80 by default which would conflict with apache:
yum -y install https://mrmarkuz.goip.de/mirror/mrmarkuz/7/noarch/nethserver-mrmarkuz-0.0.1-3.ns7.noarch.rpm yum -y install nethserver-nginx
Open the port (I chose 8099, you may change it as you like):
config set fw_zammad service status enabled TCPPort 8099 access green signal-event firewall-adjust
Edit /etc/nginx/conf.d/zammad.conf and change port 80 to 8099 at line 14.
Restart nginx to apply config:
systemctl restart nginx
Apply a virtualhost reverse proxy to use default HTTPS port, see Any plans for implementing Zammad on Nethserver
- disable nginx and use apache only
Ticket-system on NethServer?
How to implement Elasticsearch in Nexcloud
Fantastic, Bravo well done have you had any issues with elasticsearch? I have had major issues with it.
No, it just worked. What kind of issues did you have with elasticsearch?
I have 128GB of memory and it keeps saying elasticsearch out of memory
It may be too much memory used by elasticsearch, I tested on a VM with 8GB RAM. You could try to limit the memory usage:
Don’t cross the 32 GB limit — if you have servers with a lot of memory, it is generally better to run more Elasticsearch nodes than going over the 32 GB limit for maximal heap size. In short, using
-Xmx32gor higher results in the JVM using larger, 64-bit pointers that need more memory. If you don’t go over
-Xmx31g, the JVM will use smaller, 32-bit pointers by using compressed Ordinary Object Pointers (OOPs).
Yes thank you I was just reading that on the elastic website. This is would be an issue then for it running with Nethserver
That may be an issue with elk, it’s not a specific issue of Nethserver (or centos)
The issue is fixed thank you so much just change vm.max_map_count=map_count= and reload
I don’t think so, they use different nginx config files and IIRC they use different ports.
But I didn’t test it yet…
Yes, I am going to move on when I have more time.