I'm using Umbraco 8 with uSync Complete (8.11.0) and am getting the error message 'Invalid response - server didn't respond with a version number' when trying to connect to my test server from a local environment.
I can see the site seems to be making a request to the base URL of the site is this correct? How is the version number determined? We stop anybody viewing the front end on our test/staging servers - is there any unique value in a field which I could to determine if the request is from uSync (User Agent, etc)
What that probibly means is a firewall or proxy is getting in the way of the response. the version is the internal API version that uSync uses (so at the moment its either a 1 or a 2 - and v2 started at v8.9 of uSync)
if you got the wrong version (eg. a 1 when you where expecting a 2) then the error would be a version mismatch. but your error is we can't tell.
if you look in the logs you might be able to see the actual response, which is likely to be a bit of html, because usually what happens is a firewall or proxy returns some form of custom error page back, and that is then what uSync struggles to see as a version number.
You're correct the logs show the response as HTML and that HTML is coming from my site lock code. I believe all URLs below Umbraco should be open can you confirm which URL you should be hitting?
now all sites need to share the APIKey/Secret in the usync.publisher.config(although the UI should offer you the option of setting that up remotely with v8)
Connection Check
Hi,
I'm using Umbraco 8 with uSync Complete (8.11.0) and am getting the error message 'Invalid response - server didn't respond with a version number' when trying to connect to my test server from a local environment.
I can see the site seems to be making a request to the base URL of the site is this correct? How is the version number determined? We stop anybody viewing the front end on our test/staging servers - is there any unique value in a field which I could to determine if the request is from uSync (User Agent, etc)
Thanks Andy
Hi Andy,
What that probibly means is a firewall or proxy is getting in the way of the response. the version is the internal API version that uSync uses (so at the moment its either a 1 or a 2 - and v2 started at v8.9 of uSync)
if you got the wrong version (eg. a 1 when you where expecting a 2) then the error would be a version mismatch. but your error is we can't tell.
if you look in the logs you might be able to see the actual response, which is likely to be a bit of html, because usually what happens is a firewall or proxy returns some form of custom error page back, and that is then what uSync struggles to see as a version number.
Kevin
Hi Kevin,
You're correct the logs show the response as HTML and that HTML is coming from my site lock code. I believe all URLs below Umbraco should be open can you confirm which URL you should be hitting?
Thanks Andy
Hi Kevin,
Ignore that configuration mistake on my behalf - missed the /umbraco of the URL, now getting an The ApiKey/Secret cannot be authorized.
Thanks Andy
Ah ok,
that's some progress
now all sites need to share the APIKey/Secret in the
usync.publisher.config(although the UI should offer you the option of setting that up remotely with v8)Hi Kevin,
That's all setup and configured and the UI seems to think it's setup.
One issue might be that from the outside of the loadbalancer we send requests to the URL https://opencollegenetwork.test.equatedigital.com/umbraco but on the compute nodes it'll see a hostname of http://opencollegenetwork.test.equatedigital.com:91/umbraco IE switched to HTTP and port modified - could this cause issues?
Thanks Andy
Hi Kevin,
Fixed this issue now just needed to set the baseUrl in the config to the address http://opencollegenetwork.test.equatedigital.com:91
As usual great support - thanks Kevin!
Regards Andy
is working on a reply...