I am new to uSync.Complete and I am trying to pull the changes from the production instance to my development instance. I believe I have successfully connected the Dev and Prod servers because they both say available. I have include more information below.
It might be that while pulling a large amount of info from the production site the request is timing out ? (e.g on azure the timeout is 240 seconds).
just try to pull a single item (untick include children). and see if that works.
We are trying to improve catching these timeouts , so we can at least tell people, and we are also working on splitting the big tasks up so we can get it all done in less time (and not hit them) .
It is failing almost immediately. If the icons appear, it is only for a split second, so if I had to pick a stage where it is failing I would have to guess the fetching stage.
If it helps, my site isn't large and the only difference in content is that there is a Textstring document type on production instance that is not on the development instance.
I tried unticking "include children" to no avail.
Maybe this will help also. I tried to push settings to the production instance by going to Settings -> uSync Publisher -> Sync -> Push Settings (Production). This also resulted in the same error as the original post.
I will have to take a deeper look to see what might cause that .
In the meantime a couple of generic trouble shooting things:
* Browser *
Can you see if the browser network tools/console return any more detailed info (they probably don't but lets see). that might help pinpoint it.
Javascript Cache
If you have upgraded usync /complete can you make sure you have incremented the ClientDependency version value (in config/clientDependency) sometimes the JavaScript gets cached by umbraco or your browser and it can have funny effects.
Setup
Can you confirm that both you and the server are on the same version of uSync ? (but this would usually mean the servers wouldn't return "available" in the dashboard)
Is the production server behind any sort of routing setup (sometime the server requests will be re-written between the two sites, we have some settings for this - but again not sure it 'available' would also break.
these are just in case checks really, i suspect there is something else happening we just don't know what it is yet
In order to monitor progress of the job, we use signalR between the client and the server and the source and target servers. and this is where the error is coming from.
SignalR isn't critical to the operation of uSync, we only use it to display progress, but in this case the error is getting back up to the client, so its stopping the actual sync.
we can (and will) fix this issue, so the syncs will work - but without a working signalR implementation you are not going to see the funky animations while things are deployed 😢.
Again we are going to see if there is anything we can contribute to the core to fix this.
uSync Complete Pull Content Error
Hello,
I am new to uSync.Complete and I am trying to pull the changes from the production instance to my development instance. I believe I have successfully connected the Dev and Prod servers because they both say available. I have include more information below.
Below is the error and stack trace:
StatusCode: 404, ReasonPhrase: 'Not Found', Version: 1.1, Content: System.Net.Http.StreamContent, Headers: { Date: Thu, 04 Jun 2020 17:00:42 GMT Server: Microsoft-IIS/10.0 Content-Length: 1245 Content-Type: text/html }
{ Date: Thu, 04 Jun 2020 17:00:42 GMT Server: Microsoft-IIS/10.0 Content-Length: 1245 Content-Type: text/html } at uSync.Publisher.Controllers.uSyncPublisherApiController.
Hi,
At what point in the process is it failing.
do you see the icons ? e.g
It might be that while pulling a large amount of info from the production site the request is timing out ? (e.g on azure the timeout is 240 seconds).
just try to pull a single item (untick include children). and see if that works.
We are trying to improve catching these timeouts , so we can at least tell people, and we are also working on splitting the big tasks up so we can get it all done in less time (and not hit them) .
It is failing almost immediately. If the icons appear, it is only for a split second, so if I had to pick a stage where it is failing I would have to guess the fetching stage.
If it helps, my site isn't large and the only difference in content is that there is a Textstring document type on production instance that is not on the development instance.
I tried unticking "include children" to no avail.
Maybe this will help also. I tried to push settings to the production instance by going to Settings -> uSync Publisher -> Sync -> Push Settings (Production). This also resulted in the same error as the original post.
Thank you for helping with this.
Well at least that rules out timeouts 😕
I will have to take a deeper look to see what might cause that .
In the meantime a couple of generic trouble shooting things:
* Browser *
Javascript Cache
Setup
these are just in case checks really, i suspect there is something else happening we just don't know what it is yet
I found a couple of errors in the browser console. The first image is before executing the pull and the second is after the executing the pull.
Hi
I think have located the bottom of this.
There appears to be an issue with Umbraco's SignalR implimentation when Umbraco is installed in a subfolder of a site (i've logged this see : https://github.com/umbraco/Umbraco-CMS/issues/8236)
In order to monitor progress of the job, we use signalR between the client and the server and the source and target servers. and this is where the error is coming from.
SignalR isn't critical to the operation of uSync, we only use it to display progress, but in this case the error is getting back up to the client, so its stopping the actual sync.
we can (and will) fix this issue, so the syncs will work - but without a working signalR implementation you are not going to see the funky animations while things are deployed 😢.
Again we are going to see if there is anything we can contribute to the core to fix this.
is working on a reply...