Sync Issues - Windows 10 Client - SiteGround Hosted OC server

Desktop
1

Expected behaviour

Normal sync operations.

Actual behaviour

Client app reports that sync is running. The app scans for changes and then it stalls when the transfer attempts to start. This occurred 3 days ago with no changes to either server or client's.

Steps to reproduce

  1. Alter any files that are to be sync'd.

Server configuration

Operating system: SiteGround Hosting Package

Web server:

Database:

PHP version: 5.6

ownCloud version: 10.0.2

Storage backend (external storage):

Client configuration

Client version: 2.3.2 (build 6928)

Operating system: Windows 10 (current build)

2

Without more details an error messages from the logs, it will be difficult to help you. I would try first with a native webdav client (e.g. cyberduck) if webdav works properly.
https://doc.owncloud.org/desktop/latest/troubleshooting.html

3

Ok. What can I provide and how do I go about getting that information for you? Sorry but I am far from an owncloud guru. It has been nice and simple and worked up until a few days ago. More than one of my client pc's is doing this too.

4

client log (F12)

is displaying this repeatedly (endless loop)

08-11 17:42:15:159 14268 OCC::ConnectionValidator::checkAuthentication: # Check whether authenticated propfind works.
08-11 17:42:15:163 14268 OCC::AbstractNetworkJob::start: !!! OCC::PropfindJob created for "http://cloud.vizztech.com.au" + "/" "OCC::ConnectionValidator"
08-11 17:42:15:550 14268 OCC::AbstractNetworkJob::slotFinished: Redirecting "PROPFIND" QUrl("http://cloud.vizztech.com.au/remote.php/dav/files/Dan/") QUrl("https://cloud.vizztech.com.au/remote.php/dav/files/Dan/")

5

I have followed checks to test webDAV as per https://doc.owncloud.org/desktop/latest/troubleshooting.html and that appears all OK.

7

client log - user Dan.txt (52.7 KB)

A snippet of my Client Log - User Dan also attached.

8

I believe I have this fixed. It was an incorrectly configured SSL cert for the sub-domain my OC server is running on. Weird that it took forever to cause a drama though.
My client is now working properly. I will check the other client pc shortly also.