In uSync Publisher, where does it get the current server URL that is displayed in the backoffice from? It is using this URL to match which server you are currently on, but it always comes back as "Default" as the URL is wrong, so doesn't match any of the configured options (even though the configured options all work correctly as they have the right URLs).
The URL that it has found is a URL for the front end website, but for security reasons the /umbraco address isn't available on that URL, we have a separate subdomain for the back office which is restricted to access by internal users, which is why it can't be used.
Not really sure how to get it to detect the current URL as the "real" working one?
I think we are getting it from Umbraco's ApplicationMainUrl value on the IHostringEnvironment. I am not 100% sure in v9 but that might be the URL as set by ApplicationUrl value or the URL of the first request sent to the server after it boots up.
i am not sure if knowingthe above is enough to solve this 🤷.
We could probably look at having our own override of this value - we would have to take a look at how baked in the assumption of that being the URL is.
Thank you for your help earlier, knowing that it came from the Umbraco ApplicationMainUrl, I tracked down the problem, it was an Umbraco configuration issue on one of the live servers, someone had set the URL wrong when deploying it!
uSync Publisher Current Server URL
Hi,
In uSync Publisher, where does it get the current server URL that is displayed in the backoffice from? It is using this URL to match which server you are currently on, but it always comes back as "Default" as the URL is wrong, so doesn't match any of the configured options (even though the configured options all work correctly as they have the right URLs).
The URL that it has found is a URL for the front end website, but for security reasons the /umbraco address isn't available on that URL, we have a separate subdomain for the back office which is restricted to access by internal users, which is why it can't be used.
Not really sure how to get it to detect the current URL as the "real" working one?
Thanks in advance!
Hi,
I think we are getting it from Umbraco's
ApplicationMainUrlvalue on theIHostringEnvironment. I am not 100% sure in v9 but that might be the URL as set by ApplicationUrl value or the URL of the first request sent to the server after it boots up.i am not sure if knowingthe above is enough to solve this 🤷. We could probably look at having our own override of this value - we would have to take a look at how baked in the assumption of that being the URL is.
Thank you for the very quick reply!
That gives me some avenues to investigate, it might then be that something is set wrong in Umbraco. I'll look into it, thanks for your help.
Thank you for your help earlier, knowing that it came from the Umbraco ApplicationMainUrl, I tracked down the problem, it was an Umbraco configuration issue on one of the live servers, someone had set the URL wrong when deploying it!
👍
is working on a reply...