When I try to access staging server (https://staging.mydomain.com/umbraco) from local I get the following error:
Connection Test : ApiMismatch
Here is the configuration in webconfig.
<location path="umbraco/uSyncReceive">
<!-- Up the file upload limit to 500mb, this is for moving media around -->
<system.web>
<httpRuntime maxRequestLength="512000" />
</system.web>
<system.webServer>
<security>
<!-- Restrict API access by IP - you can here restrict so only servers can talk to each other -->
<!--
<ipSecurity allowUnlisted="false">
<add allowed="true" ipAddress="192.168.0.1" subnetMask="255.255.255.0" />
<add allowed="true" ipAddress="127.0.0.1" subnetMask="255.255.255.0" />
</ipSecurity>
-->
<requestFiltering>
<requestLimits maxAllowedContentLength="524288000" />
</requestFiltering>
</security>
</system.webServer>
we've seen this a couple of times recently and it is almost certainly not an API mismatch like reported 😔.
things to check are firewall/proxy settings, authentication settings or URL rewrites - anything that might be hijacking requests to /umbraco/uSyncReceive.
It is usually on of these things, something that means the request isn't getting through to uSync on the other server and the return isn't as expected.
If you look in the Umbraco logs you might be able to see that the actually error is logged and shows a load of html being returned by the request.
Normally this request would return a number (the API version) - but when it returns something else and doesn't also return a error code - this check is getting confused and thinking its the API version that is wrong.
yeah the ports are the standard (80/443) all traffic is via http/https - just sometimes there is request rewriting or restrictions as well and they worth checking for.
uSync.Publisher throws ApiMismatch error
Hi,
When I try to access staging server (https://staging.mydomain.com/umbraco) from local I get the following error:
Here is the configuration in webconfig.
and this is the response I get:
Hi Vahid,
we've seen this a couple of times recently and it is almost certainly not an API mismatch like reported 😔.
things to check are firewall/proxy settings, authentication settings or URL rewrites - anything that might be hijacking requests to
/umbraco/uSyncReceive
.It is usually on of these things, something that means the request isn't getting through to uSync on the other server and the return isn't as expected.
If you look in the Umbraco logs you might be able to see that the actually error is logged and shows a load of html being returned by the request.
Normally this request would return a number (the API version) - but when it returns something else and doesn't also return a error code - this check is getting confused and thinking its the API version that is wrong.
Hi Kevin,
Thanks for the feedback, is there any additional ports to check the firewall if it blocks those ports?
or the only ports should be 80 and 443?
Kind regards, Vahid
Hi,
yeah the ports are the standard (80/443) all traffic is via http/https - just sometimes there is request rewriting or restrictions as well and they worth checking for.
Hi Kevin,
I used uSyncDiag and realized that we use additional authentication in our Umbraco, so that would the cause and it redirects to another page.
Is there any config to setup and handle it?
After struggling with this issue, I deployed it in another server that has a valid license and it works now. I realized that could be a license issue.
is working on a reply...