Results 1 to 4 of 4
  1.    #1  
    As of today the Chapura Syncmanager gets certificate errors and their website says:
    "This site will shutdown on April 2, 2015. You will no longer be able to download purchased products or sync your webOS devices at that time."

    Obvoiusly the certificates has expired so, is their anyone out ther who is able to replace the certificates with homebrewed ones? I'm using it to sync with outlook.

    04-04-2015 08:34:42 - ERROR: Den underliggande anslutningen stängdes: Det gick inte att upprätta en förtroenderelation för den säkra SSL/TLS-kanalen.
    04-04-2015 08:34:42 - vid System.Net.HttpWebRequest.GetResponse()
    04-04-2015 08:34:42 - CcpHttpServer:rad 1975
    04-04-2015 08:34:42 - CcpHttpServer:rad 1425
    04-04-2015 08:34:42 - CcpHttpServer:rad 1698
    04-04-2015 08:34:42 - -->ERROR: Fjärrcertfikatet är ogiltigt enligt valideringsproceduren.
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
    04-04-2015 08:34:42 - vid System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
    04-04-2015 08:34:42 - vid System.Net.TlsStream.CallProcessAuthentication(Object state)
    04-04-2015 08:34:42 - vid System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
    04-04-2015 08:34:42 - vid System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
    04-04-2015 08:34:42 - vid System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
    04-04-2015 08:34:42 - vid System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
    04-04-2015 08:34:42 - vid System.Net.ConnectStream.WriteHeaders(Boolean async)

    //Dennis
  2. #2  
    I'm afraid you may have answered your own question with Chapura's site announcement. Clearly the site is still up, but they have announced the service has shutdown. The status of your certificate is likely irrelevant if there's nothing to connect to, though it's possible the shutdown was timed to coincide with the certificate expiry - maybe it was allowed to run until there was a cost to keep it going?

    Though there are no doubt ways to fake certificates (or at least for bad people to get legitimate certificates), the system is generally designed to prevent this - it's the whole point of the system. Even if you could 'homebrew' a certificate, you still have the 'nothing to connect to' problem.

    So, given this announcement, I'm going to add Chapura to the dead app list. (it seems it's already there, so updated)
    Edit: here is a list of possible alternatives: Chapura Closed 7/18/2012 :(

    I don't use Outlook, but I think it's possible to connect it to Google and connect webOS to Google so that becomes your bridge. Perhaps there are other services that can do this. Perhaps 'OwnCloud' or similar services will enable you to run your own solution - though maybe MS require license fees.

    Hopefully, someone more knowledgeable will comment, but I suspect this thread will be about alternatives rather than fixes. The only thing I can think of is that the app doesn't connect via the site, but simply authenticates itself. In that case, maybe the app can be hacked to work without checking in, but don't hold your breath for that to happen.
    Last edited by Preemptive; 04/08/2015 at 05:43 PM.
  3.    #3  
    Hi, Yes it seems as if is the PC-application itself that requires the web-site to be up.

    //Dennis

    Quote Originally Posted by Preemptive View Post
    I'm afraid you may have answered your own question with Chapura's site announcement. Clearly the site is still up, but they have announced the service has shutdown. The status of your certificate is likely irrelevant if there's nothing to connect to, though it's possible the shutdown was timed to coincide with the certificate expiry - maybe it was allowed to run until there was a cost to keep it going?

    Though there are no doubt ways to fake certificates (or at least for bad people to get legitimate certificates), the system is generally designed to prevent this - it's the whole point of the system. Even if you could 'homebrew' a certificate, you still have the 'nothing to connect to' problem.

    So, given this announcement, I'm going to add Chapura to the dead app list.

    I don't use Outlook, but I think it's possible to connect it to Google and connect webOS to Google so that becomes your bridge. Perhaps there are other services that can do this. Perhaps 'OwnCloud' or similar services will enable you to run your own solution - though maybe MS require license fees.

    Hopefully, someone more knowledgeable will comment, but I suspect this thread will be about alternatives rather than fixes. The only thing I can think of is that the app doesn't connect via the site, but simply authenticates itself. In that case, maybe the app can be hacked to work without checking in, but don't hold your breath for that to happen.
  4. #4  
    Solution:
    The Chapura "Service" is down:
    "http://www.chapura.com/

    This site will shutdown on April 2, 2015. You will no longer be able to download purchased products or sync your webOS devices at that time."

Similar Threads

  1. SSL Certificate error
    By pchrist in forum webOS Synergy and Synchronization
    Replies: 5
    Last Post: 10/12/2011, 11:17 AM
  2. gmail and ssl certificate error
    By palmpre06062009 in forum Palm Pre and Pre Plus
    Replies: 7
    Last Post: 09/26/2011, 05:17 PM
  3. SSL Certificate Error MSN Email
    By Empty_Pockets in forum Palm Pre and Pre Plus
    Replies: 1
    Last Post: 06/18/2010, 03:03 AM
  4. SSL Certificate Error with Exchange
    By DiGiTY in forum webOS Synergy and Synchronization
    Replies: 91
    Last Post: 04/09/2010, 12:38 PM
  5. Certificate Expiration Error!
    By ravic in forum Palm OS Devices & Apps
    Replies: 8
    Last Post: 08/01/2004, 11:23 PM

Posting Permissions