Client doesn't open. message about "allow NW.js " in firewall or anti virus settings?

General discussion about Zimbra Desktop.
Peacepilgrim
Posts: 2
Joined: Fri Mar 23, 2018 7:32 pm

Client doesn't open. message about "allow NW.js " in firewall or anti virus settings?

Postby Peacepilgrim » Fri Mar 23, 2018 8:33 pm

The program is not able to open. I get message about "allow NW.js " in firewall or anti virus settings.
But in Win7 firewall settings, when I search for that file, to allow it, I cannot find that file, anywhere?

How else or what is suggested to be able to get past this blocked access issue? I'm not having similar problems with other software, so not sure what's the problem. But it does give this message about NW.js. Just not sure where to go from here?


sestores
Posts: 26
Joined: Thu Feb 26, 2015 9:40 am

Re: Client doesn't open. message about "allow NW.js " in firewall or anti virus settings?

Postby sestores » Thu May 24, 2018 1:33 pm

Did you ever figure this out?
It seems I am having a similar issue. It started shortly after changing our AV software. I have tried completely disabling the firewall but that doesn't help.
Our issue is random, and rebooting the machine solves it temporarily but it eventually comes back after a while (days or weeks). I have about 20 machines running zimbra desktop and it happens randomly to different people at different times.
When they attempt to open zimbra, it flashes in the taskbar for a moment then goes away. Nothing they do will allow it to open except completely rebooting the machine. Even logging off of windows and logging back in doesn't work, but rebooting works every time.
Curious if this sounds similar to what you were facing.
Where would I find the message about allowing NW.js? Is this in a log file somewhere?
milo
Posts: 1
Joined: Thu Nov 15, 2018 10:13 am

Re: Client doesn't open. message about "allow NW.js " in firewall or anti virus settings?

Postby milo » Thu Nov 15, 2018 12:32 pm

I have the same error. Any solution so far?

I am on 7.3.1, it was OK initially. But I cant remember what I did to cause it behaving this way. Cant even open the client now and cannot read all the mail that I stored in Local Folders.
If there is another way of retrieving the Local Folders archieve mail, I wont use ZD anymore.

When I re-install older version 7.2.5, I can at least login to the mail screen but it will not sync (with below error) and I cannot see the Local Folders mail.

Please help.

Last sync 11/12/18 12:42 PM error
Failure communicating with remote server. Please try again later.
(debug info)
Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive) Exception:

com.zimbra.common.service.ServiceException: error while proxying request to target server: java.lang.RuntimeException: Could not generate DH keypair
ExceptionId:btpool0-2:1542206459781:337aefe4aa1f204d
Code:service.PROXY_ERROR Arg:(url, STR, "https://mail.mysecuresign.net/service/soap/")
at com.zimbra.common.service.ServiceException.PROXY_ERROR(ServiceException.java:317)
at com.zimbra.cs.mailbox.ZcsMailbox.sendRequest(ZcsMailbox.java:693)
at com.zimbra.cs.mailbox.ZcsMailbox.sendRequest(ZcsMailbox.java:640)
at com.zimbra.cs.mailbox.ZcsMailbox.sendRequest(ZcsMailbox.java:635)
at com.zimbra.cs.mailbox.ZcsMailbox.sendRequest(ZcsMailbox.java:628)
at com.zimbra.cs.mailbox.ZcsMailbox.sendRequest(ZcsMailbox.java:624)
at com.zimbra.cs.mailbox.ZcsMailbox.getAuthToken(ZcsMailbox.java:170)
at com.zimbra.cs.account.offline.OfflineProvisioning.getProxyAuthToken(OfflineProvisioning.java:2707)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:230)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:303)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:217)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:814)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.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(HandlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:585)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:988)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:415)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:429)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
Caused by: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at com.zimbra.common.net.CustomSSLSocket.startHandshake(CustomSSLSocket.java:90)
at com.zimbra.common.net.CustomSSLSocket.getInputStream(CustomSSLSocket.java:341)
at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:745)
at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:243)
at com.zimbra.common.soap.SoapHttpTransport.invoke(SoapHttpTransport.java:164)
at com.zimbra.common.soap.SoapTransport.invoke(SoapTransport.java:407)
at com.zimbra.common.soap.SoapTransport.invokeWithoutSession(SoapTransport.java:393)
at com.zimbra.cs.mailbox.ZcsMailbox.sendRequest(ZcsMailbox.java:678)
... 32 more
Caused by: java.lang.RuntimeException: Could not generate DH keypair
at com.sun.net.ssl.internal.ssl.DHCrypt.(Unknown Source)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverKeyExchange(Unknown Source)
at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source)
at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
... 46 more
Caused by: java.security.InvalidAlgorithmParameterException: Prime size must be multiple of 64, and can only range from 512 to 1024 (inclusive)
at com.sun.crypto.provider.DHKeyPairGenerator.initialize(DashoA13*..)
at java.security.KeyPairGenerator$Delegate.initialize(Unknown Source)
... 53 more

If issue persists please post description and debug information here.

Return to “General Questions”

Who is online

Users browsing this forum: No registered users and 6 guests