One site hosting + Zimbra

[zyxxyz]

I saw many posts about topic, but none of them help me.

To free 80 port, i made

zmtlsctl https

so zimbra is working via https, but while trying to get access

http://mydomain.com

i see
Connection refused

The remote host or network may be down. Please try the request again.

favicon of the error page is zimbra`s so come to a conclusion that zimbra is blocking http access

p.s. for the web server apache2 is used

[veronica]

Why dont you set zmtlsctl to redirect. In that case even http will also be redirected to https.

[zyxxyz]

Originally Posted by veronica

Why dont you set zmtlsctl to redirect. In that case even http will also be redirected to https.

i don`t need zimbra working in such a way.
instead of this i want to see on 1https://mydomain.com response from zimbra and on 1http://mydomain.com response from my apache2

but there any info neither in zimbra`s httpd nor in apache2 logs
so i decided that zimbra is blocking http access

[thorng]

Do you have the firewall running on the server that's blocking them.

[zyxxyz]

Originally Posted by thorng

Do you have the firewall running on the server that's blocking them.

i had already checked firewall. everything is clear
i even see response from the server in tcpdump, but it seems like server stops http packets

[zyxxyz]

here is wiki page Hosting other sites with Zimbra - Zimbra :: Wiki
where the title is Apache over http (port 80) and Zimbra over https (port 443). That is exactly what i need!
and if i`m not mistaken in my case everything that i have to do is

su - zimbra
zmtlsctl https
tomcat restart

and thats all.
but the wiki was writen for 4.5, and i`m using zimbra 5, may be some difference in processing of modes (http, https, both ...)

[ArcaneMagus]

The favicon you are seeing is probably cached in your browser from when Zimbra was operating on that port. My guess would be that Zimbra really isn't responding and your Apache isn't started or isn't binding to the port, thus making your browser unable to connect. Try verifying that Apache is actually started and binding to port 80.

[zyxxyz]

Originally Posted by ArcaneMagus

Try verifying that Apache is actually started and binding to port 80.

apache was listening 80 port

After rebuilding apache2 the problem disappeared.
Maybe some mistake in virtual host conf files

Thanks to all for trying to help me.