Getting nothing for admin console

[simrin]

I had a successful installation after updating some packages. Everything seems to be running so I went to my server at port 7071 in firefox and it pops up saying do you wish to download application/octet-stream. Now I thought I might just not have a mime type set right in my browser but then I know I was able to use the demo just fine. Any thoughts?

[marcmac]

Which url? Does it start with https: //, or http: //

[simrin]

Oh damn I am stupid. I forgot that it was https protocol. Came up just fine

[Kirkaiya]

Hi -

I have tried searching the forums, and have not found the answer (though I am sure you have probably answered it before, sorry).

I have the 60 day trial, 3.0.1 Network Edition installed on RHEL ES (4 update 2). It is running on a LAN, with port-forwarding set up (in a broadband router) to send/receive mail, and for the normal user-web-interface.

All of that works fine.

But - even from my laptop, on the LAN, using the local IP address of the machine, I can't get to the admin console. So for remote admin, I've been using X over SSH, which is very annoying.

I have tried https://10.0.0.16:7071 (also have tried https://10.0.0.16:7071/zimbraAdmin) from both FireFox 1.5.x and IE 6.0. That is the correct internal IP.

The error message in FireFox is, "Unable to connect
Firefox can't establish a connection to the server at 10.0.0.16:7071."

I'm relatively inxperienced in trouble-shooting linux. So I'm not sure if I need to add 7071 as a port in an http config file, or if I'm just missing something painfully obvious. I can get to the console from the local Linux desktop fine, of course.

Any help would be greatly appreciated!!

[phoenix]

Have you disabled SELinux and opened the ports on the firewall on your Zimbra server?

[Kirkaiya]

Hey, thanks - I added the port to the firewall setting, and just set SELinux to "permissive" for now (I don't think that survives a reboot? But I saw that I can just disable from starting also), and anyway, I can now finally reach the admin panel.

Thanks for the help. Is this set-up considered 'safe' for a production, internet-facing box? (disabling SELinux/setting to permissive)

Again, thanks, that was the one single thing that was bugging me!

- Kirk

[phoenix]

I'm afraid I'm new to Linux but SELinux seems to cause more problems than it solves. I would think that if you have a firewall then your server should be OK but I would get some advice from a RHEL forum on policy/procedures for internet facing servers.