Used Zammad installation type: package (source, package, docker-compose, …)
Operating system: Ubuntu 24.10 x64
Browser + version: Chrome Latest
Expected behavior:
Going to my FQDN should lead to Zammad login page
*
Actual behavior:
Going to my FQDN leads to the apache2 default page
*
Steps to reproduce the behavior:
Above
*
Hey gang, I’m not a super experienced linux user or zammad user and we’d like to utilize zammad for our company, everything is working great and I decided to go ahead and set up the letsencrypt stuff for apache2 and got that up and running, following along the official documentation tutorial and googling endlessly I’m now at a loss on how I can get my FQDN to go land on Zammad rather than the default apache2 page.
I can reach the site just fine with the IP and work that way but it’s still telling me the connection is insecure etc and I’d like our team to simply type the domain rather than an IP for a more professional look.
Post your apache and/or nginx config which is located in /etc/apache2/sites-ensbled/ and /etc/nginx/sites-enabled please and we can Check your configuration
#
# this is an example Apache 2.4 config for Zammad
# Please visit https://docs.zammad.org for further input on how to configure
# your Apache to work with Zammad
#
# security - prevent information disclosure about server version
ServerTokens Prod
<VirtualHost *:80>
ServerName whistlehelpdesk.org
Redirect permanent / https://whistlehelpdesk.org/
</VirtualHost>
<VirtualHost *:443>
# enable HTTP/2, if available
Protocols h2 http/1.1
SSLEngine on
SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1
SSLCipherSuite ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305
SSLHonorCipherOrder off
SSLSessionTickets off
SSLCertificateFile /etc/letsencrypt/live/whistlehelpdesk.org/cert.pem
SSLCertificateKeyFile /etc/letsencrypt/live/whistlehelpdesk.org/privkey.pem
SSLCertificateChainFile /etc/letsencrypt/live/whistlehelpdesk.org/chain.pem
SSLOpenSSLConfCmd DHParameters /etc/letsencrypt/live/whistlehelpdesk.org/dhparam.pem
# replace 'localhost' with your fqdn if you want to use zammad from remote
ServerName whistlehelpdesk.org
HostnameLookups Off
UseCanonicalName Off
ServerSignature Off
Header always set Strict-Transport-Security "max-age=63072000"
ProxyRequests Off
ProxyPreserveHost On
<Proxy 127.0.0.1:3000>
Require local
</Proxy>
ProxyPass /assets !
ProxyPass /favicon.ico !
ProxyPass /apple-touch-icon.png !
ProxyPass /robots.txt !
# legacy web socket server
ProxyPass /ws ws://127.0.0.1:6042/
# action cable
ProxyPass /cable ws://127.0.0.1:3000/cable
ProxyPass / http://127.0.0.1:3000/
# change this line in an SSO setup
RequestHeader unset X-Forwarded-User
# Use settings below if proxying does not work and you receive HTTP-Errror 404
# if you use the settings below, make sure to comment out the above two options
# This may not apply to all systems, applies to openSuse
#ProxyPass /ws ws://127.0.0.1:6042/ "retry=1 acque=3000 timeout=600 keepalive=On"
#ProxyPass /cable ws://127.0.0.1:3000/cable "retry=1 acque=3000 timeout=600 keepalive=On"
#ProxyPass / http://127.0.0.1:3000/ "retry=1 acque=3000 timeout=600 keepalive=On"
DocumentRoot "/opt/zammad/public"
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
<Directory "/opt/zammad/public">
Options FollowSymLinks
Require all granted
</Directory>
</VirtualHost>
I don’t know where to go from here, I’ve followed most of the tutorials I could find and attempted to fix what I could fix
Please be patient. This is a free community forum without any guarantees.
You cannot expect commercial grade support here.
We also cannot replace missing knowledge in terms of administration. Please don’t get me wrong, but just installing Zammad is not the end. You also have to keep it updated etc.
fixing these issues