VirtualHost setup. 404 error messages

Take your Zimbra with you!
Post Reply
spartacus
Posts: 11
Joined: Fri Apr 24, 2015 10:18 am

VirtualHost setup. 404 error messages

Post by spartacus »

I have deployed the zextras suite (2.0.4) on Zimbra Collaboration 8.6 Patch 4 on Centos 7. I am afraid I may have the wrong setup of these 2 servers. The setup is as follow:
2 servers

Server one is my web server (192.168.1.12) with a
<VirtualHost *:443>
ServerAlias zimbra.domain.net
SSLProxyEngine ON
SSLEngine On
SSLCertificateFile /certificates/zimbra/zimbra.crt
SSLCertificateKeyFile /certificates/zimbra/zimbra.key
ProxyPass / https://mail.domain.net/
ProxyPassReverse / https://mail.domain.net/
ErrorLog /var/log/httpd/zimbra_ssl-error.log
</VirtualHost>
Server 2 is my actual Zimbra server (i.e. mail.domain.net with the external FQDN set to zimbra.domain.net).
Problem.
My daily logwatch from the web server (i.e. 192.168.1.12) shows the following:
Requests with error response codes
400 Bad Request
null: 1 Time(s)
401 Unauthorized
/dav/user1%40domain.net/: 9 Time(s)
/principals/users/user1%40domain.net/: 8 Time(s)
/dav/user2%40domain.net/: 5 Time(s)
/principals/users/: 2 Time(s)
/principals/users/user2%40domain.net/: 1 Time(s)
404 Not Found
/service/soap/NoOpRequest: 1311 Time(s)
/Microsoft-Server-ActiveSync?User=user1 ... iPhone&Cmd=Ping: 153 Time(s)
/Microsoft-Server-ActiveSync?User=user1 ... e=iPad&Cmd=Ping: 124 Time(s)
/Microsoft-Server-ActiveSync?User=user2 ... e=iPad&Cmd=Ping: 86 Time(s)
/Microsoft-Server-ActiveSync?User=user2 ... iPhone&Cmd=Ping: 77 Time(s)
/Microsoft-Server-ActiveSync?User=user3 ... iPhone&Cmd=Ping: 69 Time(s)
What is causing the 404 error messages? Is my VirtualHost properly setup?

Oddly enough, my smart devices are able to synch mail, contacts and calendars!

Renato
spartacus
Posts: 11
Joined: Fri Apr 24, 2015 10:18 am

VirtualHost setup. 404 error messages

Post by spartacus »

With help from the zextras support team, the problem was found to be due to the proxy from my virtualhost timing out.



The fix was to add the following command:

ProxyPass / https://mail.domain.net/ connectiontimeout=30000 timeout=30000



Renato
Post Reply