uSync Publisher: Check connection yields Unauthorized

Questions
1

Hello everyone,

I have two environments: Demo and Test. I’m trying to set up a uSync Push-Server to push from Demo to Test. At the moment, it seems that Demo finds the Test backoffice, the AppId/AppKey is set on both environments, Incoming/Outgoing are both enabled for the moment. When checking the connection from Demo to Test, I get an Unauthorized. I’ve changed the logging level for uSync.Publisher to Verbose to see more details. I see that at the moment, I get something along the lines:

  • “http”://“TestAppUrl”“/umbraco/uSyncReceive/uSyncReceiveApi/Enabled”“” - this is a log inside the code to see where the request is coming from
  • Fail: Token doesn’t match “LUD1IHQvWsI+m1rxsGpl6QkqAUTnB9vDn5+xMmvKIro=” “0NrIynnchWXc7uHf4Mp+qEzQbFkrW7+k73BJlFMRG+4=” [“http://TestAppUrl/umbraco/usyncreceive/usyncreceiveapi/enabled”] - Verbose from uSync.Publisher.Security.HMACAuthenticationHandler

The logs are taken from the Test back office.

Are there some steps that I can take to fix the connection?

To be mentioned, there is some traefik in place.

3

Hi,

Most likely the host name that the requests are sent to and the one the receiving server is on don’t match

this can happen if the SSL cert is appiled in the middle somewhere (so the receiving site doesn’t think it’s on https://mysite.com) or something similar. it can be a bit complex with proxies etc.

Anyway answer is usually to apply a BaseUrl setting.

and if that doesn’t work you can remove the host requirement from the signing…

but the BaseUrl is preferred.

4

Hi Kevin,

I tried adding the BaseUrl already, no dice. I’ll give it a quick check without the host checking to see if it at least connects to the server.

But in reality, it most likely looks like a routing issue, I’m assuming.

Edit: Forgot to mention, at the moment, I’m using Umbraco 13, not on the latest version.

5

In my case, it worked by removing the host from the requirement.

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.