Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Desktop > Error Reports

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-30-2011, 08:10 AM
Loyal Member
 
Posts: 88
Default unable to connect to my zimbra server

regular secured imap works fine. I do NOT allow any unsecured communications so everything is ssl. Here's the error:

My Accounts

Add New Account
"https://mail.faithsbc.org:993/service/soap/" communication error. Please check port number.
Display error details
com.zimbra.common.soap.SoapFaultException: https://mail.faithsbc.org:993/service/soap/ ExceptionId:com.zimbra.common.service.RemoteServic eException: https://mail.faithsbc.org:993/service/soap/ ExceptionId:btpool0-2:1301497756449:c3e71bfe5fcae729 Code:remote.PROTOCOL_EXCEPTION at com.zimbra.common.service.RemoteServiceException.P ROTOCOL_EXCEPTION(RemoteServiceException.java:76) at com.zimbra.common.service.RemoteServiceException.d oConnectionFailures(RemoteServiceException.java:16 1) at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:567) at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:555) at com.zimbra.cs.zclient.ZMailbox.invokeJaxb(ZMailbox .java:550) at com.zimbra.cs.zclient.ZMailbox.authByPassword(ZMai lbox.java:496) at com.zimbra.cs.zclient.ZMailbox.(ZMailbox.java:411) at com.zimbra.cs.zclient.ZMailbox.getMailbox(ZMailbox .java:348) at com.zimbra.cs.account.offline.OfflineProvisioning. newZMailbox(OfflineProvisioning.java:224) at com.zimbra.cs.account.offline.OfflineProvisioning. newZMailbox(OfflineProvisioning.java:216) at com.zimbra.cs.account.offline.OfflineProvisioning. createSyncAccount(OfflineProvisioning.java:540) at com.zimbra.cs.account.offline.OfflineProvisioning. createAccount(OfflineProvisioning.java:513) at com.zimbra.cs.service.admin.CreateAccount.handle(C reateAccount.java:64) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:412) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:287) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:294) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:215) at javax.servlet.http.HttpServlet.service(HttpServlet .java:725) at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:208) at javax.servlet.http.HttpServlet.service(HttpServlet .java:814) at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:390) at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218) at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422) at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:946) at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:410) at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451) Caused by: org.apache.commons.httpclient.ProtocolException: The server mail.faithsbc.org failed to respond with a valid HTTP response at org.apache.commons.httpclient.HttpMethodBase.readS tatusLine(HttpMethodBase.java:1987) at org.apache.commons.httpclient.HttpMethodBase.readR esponse(HttpMethodBase.java:1735) at org.apache.commons.httpclient.HttpMethodBase.execu te(HttpMethodBase.java:1098) at org.apache.commons.httpclient.HttpMethodDirector.e xecuteWithRetry(HttpMethodDirector.java:398) at org.apache.commons.httpclient.HttpMethodDirector.e xecuteMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMe thod(HttpClient.java:397) at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:243) at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:164) at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:397) at com.zimbra.cs.zclient.ZMailbox.invoke(ZMailbox.jav a:561) ... 37 more Code:remote.PROTOCOL_EXCEPTION at com.zimbra.common.soap.Soap12Protocol.soapFault(So ap12Protocol.java:88) at com.zimbra.common.soap.SoapTransport.extractBodyEl ement(SoapTransport.java:344) at com.zimbra.common.soap.SoapTransport.parseSoapResp onse(SoapTransport.java:303) at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:260) at com.zimbra.common.soap.SoapHttpTransport.invoke(So apHttpTransport.java:164) at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:397) at com.zimbra.common.soap.SoapTransport.invoke(SoapTr ansport.java:360) at com.zimbra.cs.account.soap.SoapProvisioning.invoke (SoapProvisioning.java:321) at com.zimbra.cs.account.soap.SoapProvisioning.create Account(SoapProvisioning.java:464) at com.zimbra.cs.offline.jsp.JspProvStub.createOfflin eAccount(JspProvStub.java:94) at com.zimbra.cs.offline.jsp.ZmailBean.doRequest(Zmai lBean.java:102) at com.zimbra.cs.offline.jsp.FormBean.doRequest(FormB ean.java:150) at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknow n Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Un known Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.el.parser.AstFunction.getValue(AstFunction .java:127) at com.sun.el.ValueExpressionImpl.getValue(ValueExpre ssionImpl.java:206) at org.apache.jasper.runtime.PageContextImpl.evaluate Expression(PageContextImpl.java:1001) at org.apache.jsp.desktop.accsetup_jsp._jspx_meth_c_w hen_6(Unknown Source) at org.apache.jsp.desktop.accsetup_jsp._jspx_meth_c_c hoose_0(Unknown Source) at org.apache.jsp.desktop.accsetup_jsp._jspService(Un known Source) at org.apache.jasper.runtime.HttpJspBase.service(Http JspBase.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet .java:814) at org.apache.jasper.servlet.JspServletWrapper.servic e(JspServletWrapper.java:389) at org.apache.jasper.servlet.JspServlet.serviceJspFil e(JspServlet.java:486) at org.apache.jasper.servlet.JspServlet.service(JspSe rvlet.java:380) at javax.servlet.http.HttpServlet.service(HttpServlet .java:814) at com.zimbra.webClient.servlet.JspServlet.service(Js pServlet.java:64) at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166) at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(Set HeaderFilter.java:79) at com.zimbra.webClient.filters.SetHeaderFilter.doFil ter(SetHeaderFilter.java:239) at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:218) at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:422) at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543) at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:946) at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405) at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:410) at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
Account Type:


Zimbra Collaboration Suite Network Edition and Open Source Edition servers release 5.0 and later are supported. Verify server compatibility with your system administrator. To learn more about Zimbra Collaboration Suite, visit Zimbra offers Open Source email server software and shared calendar for Linux and the Mac.
Account Name:

Email Address:

Password:

Edit
Incoming Server:


Port:
Edit
Security:

None SSL
Synchronization Settings
Check Messages:

Validate and Save

Cancel
home • online help • release notes • faq • support forums • open in web browser
__________________
Running Zimbra on:
Dell PE1800
CentOS 5.x x86_64
1 x p-4 3.0 ghz xeon w/HT
6 gigs ram
8 users
250 gig MDRAID 1
Release 7.1.4_GA_2555.RHEL5_64_20120105094627 CentOS5_64 FOSS edition.
Reply With Quote
  #2 (permalink)  
Old 03-31-2011, 01:59 PM
Elite Member
 
Posts: 305
Default

Quote:
Originally Posted by hescominsoon View Post
Add New Account
"https://mail.faithsbc.org:993/service/soap/" communication error. Please check port number.
Firewall?

Doug
__________________
Ben Franklin quote:

"Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety."
Reply With Quote
  #3 (permalink)  
Old 03-31-2011, 02:47 PM
Loyal Member
 
Posts: 88
Default

nopers. Nothing on the firewall has changed. Was working fine. Also Thunderbird can connect just fine using imap. Same for my Driod phone. Only ZD is unable to connect.
__________________
Running Zimbra on:
Dell PE1800
CentOS 5.x x86_64
1 x p-4 3.0 ghz xeon w/HT
6 gigs ram
8 users
250 gig MDRAID 1
Release 7.1.4_GA_2555.RHEL5_64_20120105094627 CentOS5_64 FOSS edition.
Reply With Quote
  #4 (permalink)  
Old 04-01-2011, 06:36 AM
Zimbra Employee
 
Posts: 98
Default

It looks like you have selected account type = Zimbra, which causes ZD to use SOAP via HTTP instead of IMAP. Therefore, you'll need to use the HTTPS port (443 by default) instead of port 993.
Reply With Quote
  #5 (permalink)  
Old 04-01-2011, 10:46 AM
Loyal Member
 
Posts: 88
Default

https is also wide open. I can use the web interface just fine under ie, ff, and chrome. the only thing that doesn't work is ZD.
__________________
Running Zimbra on:
Dell PE1800
CentOS 5.x x86_64
1 x p-4 3.0 ghz xeon w/HT
6 gigs ram
8 users
250 gig MDRAID 1
Release 7.1.4_GA_2555.RHEL5_64_20120105094627 CentOS5_64 FOSS edition.
Reply With Quote
  #6 (permalink)  
Old 04-01-2011, 11:03 AM
Loyal Member
 
Posts: 88
Default

what's strange is why is it trying for 993? it should go to 443 by default.
__________________
Running Zimbra on:
Dell PE1800
CentOS 5.x x86_64
1 x p-4 3.0 ghz xeon w/HT
6 gigs ram
8 users
250 gig MDRAID 1
Release 7.1.4_GA_2555.RHEL5_64_20120105094627 CentOS5_64 FOSS edition.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.