I have recently upgraded to Umbraco 17. Unable to Restore to Local and Transfer Content from one environment to another

Questions
1

Hi everyone, I have recently upgraded to Umbraco 17. I am able to run the project Locally but my other colleagues are not able to restore to Local from our Dev Environment and we also cannot transfer content from once environment to another. Below is the error we get in both occurrences (Restore or Content Queue for Transfer).

[17:34:49 ERR] Exception!
Umbraco.Deploy.Infrastructure.Exceptions.RemoteApiException: The remote API is not accessible, getting a 403 error connecting to ``https://dev-psg-content-hub.euwest01.umbraco.io/umbraco/backoffice/deploy/environment/BeginSession
at Umbraco.Deploy.Infrastructure.Http.DeployHttpClient.SucceedOrThrow(HttpResponseMessage result, JsonSerializerOptions jsonSerializerOptions, CancellationToken cancellationToken)
at Umbraco.Deploy.Infrastructure.Http.DeployHttpClient.SendAsync(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationToken cancellationToken)
at Umbraco.Deploy.Infrastructure.Environments.RemoteUmbracoEnvironment.BeginSessionAsync(Guid sessionId, CancellationToken cancellationToken)
at Umbraco.Deploy.Infrastructure.Work.WorkItems.DeployRestoreWorkItemBase.GetSessionOn(IUmbracoEnvironment env, Nullable1 batchIndex, Nullable1 numberOfBatches)
at Umbraco.Deploy.Infrastructure.Work.WorkItems.TargetRestoreWorkItem.ExecuteAsyncSub(IWorkContext context, List1 resume, CancellationToken cancellationToken) [17:34:49 INF] Abort remote session [17:34:50 DBG] UnShadow '4aspepfg' abort [17:34:50 INF] Restore caches and indexes [17:34:50 INF] Resume scheduled publishing. [17:34:50 INF] Resume database. [17:34:50 ERR] Work 72edf8aa-3323-4c81-b6a0-03a23dffcc06 has failed. Umbraco.Deploy.Infrastructure.Exceptions.RemoteApiException: The remote API is not accessible, getting a 403 error connecting to ``https://dev-psg-content-hub.euwest01.umbraco.io/umbraco/backoffice/deploy/environment/BeginSession`` at Umbraco.Deploy.Infrastructure.Http.DeployHttpClient.SucceedOrThrow(HttpResponseMessage result, JsonSerializerOptions jsonSerializerOptions, CancellationToken cancellationToken) at Umbraco.Deploy.Infrastructure.Http.DeployHttpClient.SendAsync(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationToken cancellationToken) at Umbraco.Deploy.Infrastructure.Environments.RemoteUmbracoEnvironment.BeginSessionAsync(Guid sessionId, CancellationToken cancellationToken) at Umbraco.Deploy.Infrastructure.Work.WorkItems.DeployRestoreWorkItemBase.GetSessionOn(IUmbracoEnvironment env, Nullable1 batchIndex, Nullable1 numberOfBatches) at Umbraco.Deploy.Infrastructure.Work.WorkItems.TargetRestoreWorkItem.ExecuteAsyncSub(IWorkContext context, List1 resume, CancellationToken cancellationToken)
at Umbraco.Deploy.Infrastructure.Work.WorkItems.TargetRestoreWorkItem.ExecuteAsyncSub(IWorkContext context, List1 resume, CancellationToken cancellationToken) at Umbraco.Deploy.Infrastructure.Work.WorkItems.TargetRestoreWorkItem.ExecuteAsync(IWorkContext context, CancellationToken cancellationToken) [17:34:50 DBG] [Umbraco.Deploy.Infrastructure.Work.WorkTask] OnEvent TaskCompleted [17:34:50 INF] Deployment 72edf8aa-3323-4c81-b6a0-03a23dffcc06 completed. [17:34:50 ERR] Deployment failed. Umbraco.Deploy.Infrastructure.Exceptions.RemoteApiException: The remote API is not accessible, getting a 403 error connecting to ``https://dev-psg-content-hub.euwest01.umbraco.io/umbraco/backoffice/deploy/environment/BeginSession`` at Umbraco.Deploy.Infrastructure.Http.DeployHttpClient.SucceedOrThrow(HttpResponseMessage result, JsonSerializerOptions jsonSerializerOptions, CancellationToken cancellationToken) at Umbraco.Deploy.Infrastructure.Http.DeployHttpClient.SendAsync(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationToken cancellationToken) at Umbraco.Deploy.Infrastructure.Environments.RemoteUmbracoEnvironment.BeginSessionAsync(Guid sessionId, CancellationToken cancellationToken) at Umbraco.Deploy.Infrastructure.Work.WorkItems.DeployRestoreWorkItemBase.GetSessionOn(IUmbracoEnvironment env, Nullable1 batchIndex, Nullable1 numberOfBatches) at Umbraco.Deploy.Infrastructure.Work.WorkItems.TargetRestoreWorkItem.ExecuteAsyncSub(IWorkContext context, List1 resume, CancellationToken cancellationToken)
at Umbraco.Deploy.Infrastructure.Work.WorkItems.TargetRestoreWorkItem.ExecuteAsyncSub(IWorkContext context, List`1 resume, CancellationToken cancellationToken)
at Umbraco.Deploy.Infrastructure.Work.WorkItems.TargetRestoreWorkItem.ExecuteAsync(IWorkContext context, CancellationToken cancellationToken)

2

Hi,

A 403 on /umbraco/backoffice/deploy/environment/BeginSession usually means the Deploy endpoint is reachable but the request is not authorized.

I’d start by verifying that all environments run the same Umbraco and Deploy versions and that the API keys match

3

My team is running into the same error. We thought it was related to the Umbraco.Workflow package. When disabled in Dev, content transfers/restores work as expected both ways. When workflow is enabled in Dev, we get the 403.

We ruled out permissions, because the users using it are devs with full admin rights in the env. And we’ve double checked that API keys and Cms/Deploy versions are matching.

4

Hi

A few things worth trying:

  1. Check for schema mismatches first after an upgrade these are common and can block Deploy sessions. The official docs recommend clearing cached signatures on both environments via Settings > Deploy dashboard: Troubleshooting | Deploy | Umbraco Documentation

  2. Since Workflow seems to be the trigger, check whether the Umbraco.Workflow package version is compatible with v17 and the current Deploy version. It’s possible it’s intercepting or blocking the Deploy API request.

  3. Try running a schema export/import manually to rule out any stale signatures after the upgrade.

Also worth raising this directly with Umbraco HQ support since it looks like a potential compatibility issue between Workflow and Deploy on v17 they’d want to know about it? or maybe @tthatho already figured it out :wink:

/Bishal

1 Like