Port-Redirecting leads to unknown error...

[MFriese]

Hello,

I'm new and searched the forums for this error but haven't found a solution yet.

First I wanna thank you for this wonderful product, we all love it here

But now here's my problem:
I installed the latest release onto my SuSE-Server which is currently running Plesk for Hosting etc. To leave Plesks Webserver alone, I installed Zimbra with all ports + 1000, e.g. port 1443 is the SSL-Port for the normal Zimbra login. This is working fine so far.
Now I got a second IP-Address which I want to use for Zimbra, so I redirected port 443 for this new ip-address to my mentioned 1443 port. This is working so far that it loads the login page via https://myserver.tld but when I try to login it gives me an unknown error (service.FAILURE). On port 1443 everything is working fine.

So my question is of course if anybody knows how to solve this
Many thanks in advance!

[KevinH]

You've got some sort of problem in you port/ip mapping and the Zimbra client can't get to your server.

[MFriese]

Hmmm... I have nothing else in my iptables, just this one forward:

iptables -t nat -A PREROUTING -p tcp -d 1.2.3.4 --dport 443 -j REDIRECT --to-ports 1443

And as I said this is working fine for loading the html / js part including graphics from zimbra but I'm not able to log in. Do I have to change anything else?

[KevinH]

Originally Posted by MFriese

Hmmm... I have nothing else in my iptables, just this one forward:

iptables -t nat -A PREROUTING -p tcp -d 1.2.3.4 --dport 443 -j REDIRECT --to-ports 1443

And as I said this is working fine for loading the html / js part including graphics from zimbra but I'm not able to log in. Do I have to change anything else?

Well our jsp's and servlets do some redirects on login so it's very likely that it's redirecting to the 443 port and your rule is then preventing it from working.

Not really a *standard* config and our services at the moment don't play well trying to be forced to a single IP/interface. So not sure what else we can do. I'd recommend you trace the browser network traffic and try to see where it gets stuck.

[MFriese]

Okay, I'll try that. Thanks for your quick response

[MFriese]

If anyone else ran into this problem -- I solved it with another post which I have not found before :/

You have to edit the allowedPorts within the configuration to let Zimbra login on another port. This was it --- but the error message didn't tell me that directly...