Current Server resolves itself as the default, rather than current server
Umbraco 8.18.7, uSync Complete 8.11.11. Issue relating to uSync Publisher.
I currently have this set up, and the configuration seems to correctly recognise all the servers correctly and flag them as available when on environments.
My issue is that the Current Server doesn't seem to be able to detect itself correctly, and flags itself as the default local / development server instead of staging or live when on those environments. This then affects which environments I can push / pull to and from in the CMS.
Url in the configuration matches my CMS Url, and I have also attempted to set BaseUrl in config without success. Just wondering if anyone has encountered similar and could shed some light or direction...
The server is attempted to be matched based on the request URL - so if that matches the server it should find itself....
but - quickly checking the code, this match only happens if the server is enabled (for incoming) - so if the server is disabled, it won't find itself.
I am not sure why we do this (there is a flag to include disabled servers when we search). so i will have a scan of the code to confirm its ok for us to include disabled servers when we are looking for the current server.
but for now i think the workaround is enable the server for incoming.
The flag for the server to accept incoming was already set.
I have since located the underlying issue.
On non-local / development environments, the url of the local environment was set to an empty string in our config when applying DevOps transforms. The current server was then detecting this and seeming to use it so all servers though they were local.
If we supply a value in that url for the local environment on each environment then the problem seems to be resolved.
Current Server resolves itself as the default, rather than current server
Umbraco 8.18.7, uSync Complete 8.11.11. Issue relating to uSync Publisher.
I currently have this set up, and the configuration seems to correctly recognise all the servers correctly and flag them as available when on environments.
My issue is that the Current Server doesn't seem to be able to detect itself correctly, and flags itself as the default local / development server instead of staging or live when on those environments. This then affects which environments I can push / pull to and from in the CMS.
Url in the configuration matches my CMS Url, and I have also attempted to set BaseUrl in config without success. Just wondering if anyone has encountered similar and could shed some light or direction...
Hi,
The server is attempted to be matched based on the request URL - so if that matches the server it should find itself....
but - quickly checking the code, this match only happens if the server is enabled (for incoming) - so if the server is disabled, it won't find itself.
I am not sure why we do this (there is a flag to include disabled servers when we search). so i will have a scan of the code to confirm its ok for us to include disabled servers when we are looking for the current server.
but for now i think the workaround is enable the server for incoming.
Kevin
Hi Kevin, thanks for your response.
The flag for the server to accept incoming was already set.
I have since located the underlying issue.
On non-local / development environments, the url of the local environment was set to an empty string in our config when applying DevOps transforms. The current server was then detecting this and seeming to use it so all servers though they were local.
If we supply a value in that url for the local environment on each environment then the problem seems to be resolved.
Thanks for reaching out to assist.
is working on a reply...