Zimbra and apache2 on same host: problem although different ports

[sterua]

Hello everyone.
First at all, excuse for my bad english.
I configured my home mail server under Zimbra (open source edition) and I want to be able to host an Apache server.
My concern is that I can not seem to hold together and i don't understand why :
- I want to do a simple html site that will be on port 80 (I'm not planning for the time https).
- I configured when installing Zimbra for:
+ Using only https both the administration interface and the webmail
+ Port of the administration interface is 7071
+ Port of the webmail is 8044
(I do not see where is the problem because normally there is the problem that when the webmail and apache listening on the same port.)
- if Apache2 is started, when I do a service Zimbra status it returns me all ok except zmmailboxdctl
- When apache2 is stopped, everything is going.
- I did like http://wiki.zimbra.com/wiki/ZimbraApache in "Apache over http (port 80) and Zimbra over https (port 443)" say, (well, at least, i did the zmtlsctl https and not tomcat restart because of there is not tomcat)
- I tried to do zmprov ms but it returns me an error
- There is an ubuntu 13.10 and Zimbra 8.0.7
Do you have any clarifications to me? Any help please ?
Thanking you in advance.

[SrnokeyMcPot]

Hi sterua,



not going in to the problem but what about you start up a second IP address, since it's a LAN Network Setup and let Zimbra have the socket on the first and apache on the second IP.



cheers,

Johannes

[AndresTarallo]

Could you please provide the output of zmrpov? I used to have that setup on a customer, no problems

[jorgedlcruz]

Hi sterua,

Mix both environments is always a bad idea. When you have the http server shutdown, does zimbra uses the port 80? Check it, and also Zimbra doesn't support Ubuntu 13.10, just Ubuntu Server 12.04 or 14.04.



Best regards!

[LeonSandcastle]

Recall that zimbra has to be on a server by itself and nothing else running on it.

So I hope you are not trying to have zimbra and then Apache running on same server, that won't fly.

Seems obvious but sometimes overlooked.