Please note that “just” because you’re using a package manager to update Zammad, that doesn’t mean that the update went through without any errors.
We strongly recommend to check the output after updating Zammad.
Sorry, but with the current set of information it’s impossible to help you.
Add your fully qualified domain name or public IP to servername directive of
nginx, if this installation is done on a remote server. You have to change:
/etc/nginx/conf.d/zammad.conf and restart nginx process.
Otherwise just open http://localhost/ in your browser to start using Zammad.
Remember to enable selinux and firewall rules!
Use the following commands:
setsebool httpd_can_network_connect on -P
firewall-cmd --zone=public --add-service=http --permanent
firewall-cmd --zone=public --add-service=https --permanent
That’s odd, I can’t reproduce this issue.
Could you please verify if this also affects hosted instances for you? (in my case it doesn’t): https://zammad.com/getting-started
Also ensure that your server can be reached by the telegram subnets 126.96.36.199/20 and 188.8.131.52/22.
While the above should be no problem, also ensure that you’re using Ports 443, 80, 88 or 8443 for Zammad, as other wise the Telegram webhooks will not work.
You can find more information on the Telegram webhooks here: