Page 1 of 1

WSASYSNOTREADY

PostPosted: Fri Aug 26, 2016 4:07 pm
by Blindfish
SyncoveryCL worked fine with my Ubuntu 14.04 LTS (64 Bit). After upgrading to Ubuntu 16.04 it can't connect to my owncloud server anymore:
    can't access Right path
The log shows many of the following error messages:
    SSL Connection error 336236740 in SSLDoConnect, returning WSASYSNOTREADY. error:140A90C4:SSL routines:SSL_CTX_new:null ssl method passed
Seems to be a socket problem, but I've no faint idea how to solve it. Any suggestions?

Re: WSASYSNOTREADY

PostPosted: Sun Aug 28, 2016 6:05 am
by Blindfish
I made a fresh installation with Ubuntu 16.04 LTS (32 Bit) and got exactly the same problem. There seems to be a general incompatibility with this version of Ubuntu.

Re: WSASYSNOTREADY

PostPosted: Wed Aug 31, 2016 4:31 am
by superflexible
It is related to OpenSSL. Maybe an incompatibility with a newer OpenSSL version. I will analyze it and fix it, but it can take a few days.

Re: WSASYSNOTREADY

PostPosted: Tue Sep 06, 2016 4:01 am
by superflexible
I cannot confirm any problems on Ubuntu 16.04. I can connect to cloud services as well as WebDAV servers with https. Are you using the WebDAV protocol?

Re: WSASYSNOTREADY

PostPosted: Mon Sep 12, 2016 1:01 pm
by Blindfish
I'm trying to sync with my owncloud server using WebDAV. It works great with Windows. I transferred the xml file from Windows to Ubuntu and adapted the way to introduce the credentials. After importing the xml file, Syncovery worked as desired with Ubuntu 14.04 - until I upgraded to Ubuntu 16.04.

I can connect to my server with Nautilus, but Syncovery delivers the WSASYSNOTREADY error. If you can't confirm the problem, there must be something wrong with my xml file. I tried to analyse it without success. The documentation available is not sufficient for my limited programming knowledge.I'm stuck. Do you have any suggestions how I could proceed finding the cause of this problem?

Re: WSASYSNOTREADY

PostPosted: Tue Sep 13, 2016 1:32 pm
by superflexible
Can you send a log file? It contains your settings, so I can check. The log files are inside .Syncovery/Logs. You can post it here or send it to support@syncovery.com. You can edit the IP or URL of your server in the log if necessary, but please keep all other lines unchanged. The URL will appear several times in the log.

Re: WSASYSNOTREADY

PostPosted: Tue Sep 13, 2016 11:16 pm
by Blindfish
Thank you for taking your time to explore this problem. I attached the log file with the modified URL as you suggested. Hopefully, it will deliver the information you need.

Re: WSASYSNOTREADY

PostPosted: Thu Sep 15, 2016 9:47 am
by superflexible
I think that it should be using TLS and not SSLv23.

You should be able to change it with a command line such as this:

Code: Select all
SyncoveryCL CHANGE Notizen /RightFTPSettings="WebDAV1:Auth=Basic,Flags=UTF8+UTC+DetectTimezone,"Proxy=no",Cmd=0,TimStmpMode=0,AuthRetries=2,TLS=TLS,RecursLst=N"

Re: WSASYSNOTREADY

PostPosted: Fri Sep 16, 2016 2:09 am
by Blindfish
Using the command you provided, I got the following messages:
Code: Select all
Unknown Internet Protocol Setting: auth=Basic
Unknown Internet Protocol Setting: cmd=0

Nevertheless the profile does work now. Thank you very much for your support!

The according line in my xml file was:
Code: Select all
<RightFTPSettings>YNNN/0/4/0/1/1537/80/0/8080/0/0/,:/1/1/0/0/0/0/keine:/N/2</RightFTPSettings>

I suspected already that something might have been wrong in this line, but I was not able to decrypt the meaning. Your new command is a bit more literal, but it's still close to Chinese for me. Is there any documentation available that could help, coding the xml file properly? The Syncovery Settings Dictionary PDF Document is just a list without providing any explanations.

I'm looking forward very much to the web front end you are working on. That could make things much easier.

Thanks again and please keep on with your excellent work!

Re: WSASYSNOTREADY

PostPosted: Mon Sep 19, 2016 12:47 pm
by superflexible
Hello,
there is no more detailed documentation. I will release the web interface ASAP, hopefully next week.