- Used Zammad version: 6.0
- Used Zammad installation type: package
- Operating system: ubuntu 22.04
- Browser + version: chrome
Expected behavior:
Installed new setup
*
Actual behavior:
it show the below error after a fresh installation
1)Restart ur Server and see
2)Check zammad is enabled
Check server log and paste here
Error log:
[Wed Aug 02 06:44:07.352430 2023] [mpm_event:notice] [pid 101381:tid 139923968051072] AH00492: caught SIGWINCH, shutting down gracefully
[Wed Aug 02 06:44:08.130685 2023] [mpm_event:notice] [pid 103495:tid 139653947983744] AH00489: Apache/2.4.52 (Ubuntu) OpenSSL/3.0.2 configured – resuming normal operations
[Wed Aug 02 06:44:08.130844 2023] [core:notice] [pid 103495:tid 139653947983744] AH00094: Command line: ‘/usr/sbin/apache2’
[Wed Aug 02 06:44:11.372861 2023] [proxy:error] [pid 103496:tid 139653931361856] (111)Connection refused: AH00957: http: attempt to connect to 127.0.0.1:3000 (127.0.0.1) failed
[Wed Aug 02 06:44:11.372935 2023] [proxy_http:error] [pid 103496:tid 139653931361856] [client 172.69.65.2:60930] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Wed Aug 02 06:44:11.643361 2023] [proxy:error] [pid 103497:tid 139653848700480] (111)Connection refused: AH00957: http: attempt to connect to 127.0.0.1:3000 (127.0.0.1) failed
[Wed Aug 02 06:44:11.643420 2023] [proxy_http:error] [pid 103497:tid 139653848700480] [client 172.70.174.99:34362] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Wed Aug 02 06:44:30.992125 2023] [proxy:error] [pid 103496:tid 139653873878592] (111)Connection refused: AH00957: http: attempt to connect to 127.0.0.1:3000 (127.0.0.1) failed
[Wed Aug 02 06:44:30.992164 2023] [proxy_http:error] [pid 103496:tid 139653873878592] [client 172.70.243.163:34620] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Wed Aug 02 06:46:13.806513 2023] [proxy:error] [pid 103497:tid 139653831915072] (111)Connection refused: AH00957: http: attempt to connect to 127.0.0.1:3000 (127.0.0.1) failed
[Wed Aug 02 06:46:13.806557 2023] [proxy_http:error] [pid 103497:tid 139653831915072] [client 172.70.242.15:40304] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Wed Aug 02 06:57:25.479702 2023] [proxy:error] [pid 103497:tid 139653865485888] (111)Connection refused: AH00957: http: attempt to connect to 127.0.0.1:3000 (127.0.0.1) failed
[Wed Aug 02 06:57:25.488378 2023] [proxy_http:error] [pid 103497:tid 139653865485888] [client 172.70.134.45:55248] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Wed Aug 02 07:11:02.350972 2023] [proxy:error] [pid 103496:tid 139653738915392] (111)Connection refused: AH00957: http: attempt to connect to 127.0.0.1:3000 (127.0.0.1) failed
[Wed Aug 02 07:11:02.351015 2023] [proxy_http:error] [pid 103496:tid 139653738915392] [client 205.210.31.11:60038] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
[Wed Aug 02 07:13:48.513706 2023] [proxy:error] [pid 103496:tid 139653722129984] (111)Connection refused: AH00957: http: attempt to connect to 127.0.0.1:3000 (127.0.0.1) failed
[Wed Aug 02 07:13:48.513747 2023] [proxy_http:error] [pid 103496:tid 139653722129984] [client 167.248.133.49:42440] AH01114: HTTP: failed to make connection to backend: 127.0.0.1
Connection refused… are you using a firewall that blocks access to your Zammad instance?
yes but the ports are allowed
and one more thing, i tried to check the production.log in /opt/zammad/log but the file looks empty!
Could you please paste your apache config for Zammad?
#
# 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 support.ignithocloud.com
Redirect permanent / https://support.ignithocloud.com
</VirtualHost>
<VirtualHost *:443>
SSLEngine on
SSLProtocol all -SSLv2 -SSLv3
SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH
SSLCertificateFile /etc/letsencrypt/live/support.ignithocloud.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/support.ignithocloud.com/privkey.pem
SSLCertificateChainFile /etc/ssl/lets-encrypt-x3-cross-signed.pem
SSLOpenSSLConfCmd DHParameters /etc/ssl/dhparam.pem
# replace 'localhost' with your fqdn if you want to use zammad from remote
ServerName support.ignithocloud.com
## don't loose time with IP address lookups
HostnameLookups Off
## needed for named virtual hosts
UseCanonicalName Off
## configures the footer on server-generated documents
ServerSignature Off
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>
the file is from /etc/apache2/sites-available/zammad.conf
Please format it in a more readable way, thanks 
Edit: I did so myself.
Well, something is blocking the request and I guess this is why it’s not working.
Thanks 
Also /var/log/zammad/production.log looks empty
journalctl -u zammad?
yes i checked but it only shows something like this
Aug 02 08:40:19 IG-Support systemd[1]: Stopped zammad.service.
Aug 02 08:40:19 IG-Support systemd[1]: Started zammad.service.
Aug 02 08:44:10 IG-Support systemd[1]: Stopping zammad.service…
Aug 02 08:44:10 IG-Support systemd[1]: zammad.service: Deactivated successfully.
Aug 02 08:44:10 IG-Support systemd[1]: Stopped zammad.service.
Aug 02 08:44:10 IG-Support systemd[1]: Started zammad.service.
Are you using SELinux?
im using ubuntu 22.04 in azure
I have almost zero experience in Azure, I’m sorry. Something is blocking your requests, you need to figure out what.
Ok, thank you for your assistance !
Just(!) for testing purposes: Is it possible to disable ufw completely? If it’s working then, you know where to start deep diving.
Please remove open ports 3000 and 6042 as you’re allowing internet access directly to Zammad which is not the best idea.
Also, note that port 9200 (elasticsearch) is open which is a potential, serious data leak unless you’ve secured it with at least user authentication!
1 Like
Yes it is possible, right we are using zammad in AWS from marketplace image. but now we’re migrating it to azure as a new zammad. now i’m doing it for testing purpose and i deactivated the firewall it seems the issue is still exist.
No clue what image you’re talking about. If it comes with Zammad preinstalled, you may not want to trust it because it’s nothing official from Zammad GmbH.
Your ports still don’t fit, it is still an insecure installation.
So this is just for testing. doing things on my own
My doubt is that I have an apache configuration file, so should I call it zammad.conf or mydomain.com.conf?
every other service looks fine but im stuck while doing the apache configuration. so if you have command or documents more briefly it would be a great help