[SOLVED] A network service error has occurred

[jablan]

Hi all. Got my installation up and running and having an odd problem.

This only happens in Advanced mode (on IE7 and FF3).

Whenever an AJAX call occurs (which is alot) I get the following error:

A network service error has occurred.
msg: system failure: Request not allowed on port 7072
code: service.FAILURE
method: GetContactsRequest
detail: soap:Receiver
trace: btpool0-7:1226701350166:ea1d1c0902f1d1c8

Obviously, the method is different for the different errors.

I've checked my Zimbra logs and just see this:

com.zimbra.common.service.ServiceException: system failure: Request not allowed on port 7072
ExceptionId:btpool0-9:1226699941809:ea1d1c0902f1d1c8
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:350)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)


I guess my question is why is this happening? Can it be fixed? Did I screw something up?

This does not happen in STANDARD mode.

Thanks!!!

P.S. I searched and searched for this error and help before I posted.

P.S.S. Running the latest Zimbra, CentOS v5.2. iptables and selinux are disabled.

[jablan]

Of course, it's always when you post that you figure it out.

I'm completely retarded and *thought* you had to access the client/user site of Zimbra at port 7072 versus port 80. Duh, well, that fixed it.

Take away: Don't access zimbra on port 7072, it doesn't work well.