Results 1 to 4 of 4

Thread: Upgraded to 5.0.9 from 4.5.10 - Now web client does not work ?

  1. #1
    Join Date
    Dec 2006
    Posts
    24
    Rep Power
    8

    Default Upgraded to 5.0.9 from 4.5.10 - Now web client does not work ?

    Hi all,

    I just upgraded to 5.0.9 (10.4 OS X platform) a couple of hours ago, and for some reason the web client does not work anymore. Restarted services and even rebooted the system, but it still does not work.

    I'm getting the "usual" "A network service error has occurred (zclient/io)" for both firefox 3 and for Apple Safari. Tried all "versions" (ajax, default, HTML).

    Admin pages work, and external imap clients work without any problems.

    when looking at the /opt/zimbra/log/mailbox.log i get the following error:

    2008-10-01 23:52:38,195 INFO [btpool0-10] [ip=127.0.0.1;] soap - GetDomainInfoRequest
    2008-10-01 23:52:49,432 WARN [btpool0-1] [] webclient - local exception
    com.zimbra.cs.zclient.ZClientException: invoke unable to parse response:

    404 Not Found

    Not Found


    The requested URL /service/soap was not found on this server.


    Additionally, a 404 Not Found
    error was encountered while trying to use an ErrorDocument to handle the request.



    Apache/1.3.41 Server at localhost Port 16080



    ExceptionId:btpool0-1:1222897969432:8c319a07d3eb1222
    Code:zclient.IO_ERROR
    at com.zimbra.cs.zclient.ZClientException.IO_ERROR(ZC lientException.java:47)
    at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:530)
    at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:520)
    at com.zimbra.cs.zclient.ZMailbox.authByPassword(ZMai lbox.java:465)
    at com.zimbra.cs.zclient.ZMailbox.(ZMailbox.java:375)
    at com.zimbra.cs.zclient.ZMailbox.getMailbox(ZMailbox .java:324)
    at com.zimbra.cs.taglib.tag.LoginTag.doTag(LoginTag.j ava:123)
    at org.apache.jsp.public_.login_jsp._jspService(login _jsp.java:277)
    at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:93)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:373)
    at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:477)
    at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:371)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
    at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:50)
    at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
    at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:362)
    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.servlet.Dispatcher.forward(Dispa tcher.java:268)
    at org.mortbay.jetty.servlet.Dispatcher.forward(Dispa tcher.java:126)
    at org.mortbay.jetty.servlet.DefaultServlet.doGet(Def aultServlet.java:465)
    at org.mortbay.jetty.servlet.DefaultServlet.doPost(De faultServlet.java:496)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
    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 com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:283)
    at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
    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)
    Caused by: com.zimbra.common.soap.SoapParseException: unable to parse response:

    404 Not Found

    Not Found


    The requested URL /service/soap was not found on this server.


    Additionally, a 404 Not Found
    error was encountered while trying to use an ErrorDocument to handle the request.



    Apache/1.3.41 Server at localhost Port 16080



    at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:216)
    at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:251)
    at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:297)
    at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:526)
    ... 50 more
    But have no idea what might be wrong !

    Any pointers ??

    Thanks in advance,

    Lasse,
    Last edited by lchrist; 10-01-2008 at 03:11 PM.

  2. #2
    Join Date
    Jul 2007
    Location
    San Jose, CA
    Posts
    1,027
    Rep Power
    10

    Default

    Have you tried logging in from a different computer (on your LAN)? You might find that you need to either (1) clear your browser cache, or (2) delete and re-import the SSL certificate for the page to show, since changes that happen during upgrade sometimes make a browser think it's seeing a hacked page. Unfortunately, browsers often give you a 404 rather than the honest answer that it thinks the server is hacked. . .
    Cheers,

    Dan

  3. #3
    Join Date
    Dec 2006
    Posts
    24
    Rep Power
    8

    Default Not the browser giving me the 404

    This is from the mailbox log. So it is definitely Zimbra who's giving me the error.

  4. #4
    Join Date
    Aug 2005
    Location
    San Mateo, CA
    Posts
    4,789
    Rep Power
    19

    Default

    looks like you've got some custom port setting to port 16080. You should verify you've got it set right or go back to the defaults to make it work again.
    Looking for new beta users -> Co-Founder of Acompli. Previously worked at Zimbra (and Yahoo! & VMware) since 2005.

Similar Threads

  1. users kicked out of web client, expires
    By nate.wheeler in forum Administrators
    Replies: 9
    Last Post: 03-11-2010, 12:43 AM
  2. Use Zimbra Web Client instead of Squirrelmail
    By Pieter in forum Migration
    Replies: 7
    Last Post: 04-03-2008, 02:14 PM
  3. Replies: 5
    Last Post: 02-29-2008, 08:09 AM
  4. ZCS Web Client over SSL does not work
    By vulcanman in forum Installation
    Replies: 2
    Last Post: 03-27-2007, 09:22 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •