Publishing the project has failed.: Proxy error- (502) Bad Gateway

studio
publish
p_solved

#1

I am trying to get credentials from orchestrator, So trying to either publish or get credentials using an asset name is erroring out with 502 gateway error.

Publishing the project has failed.

Error: Failed to process request. ‘Proxy Error ( Forefront TMG denied the specified Uniform Resource Locator (URL). )’.
The remote server returned an error: (502) Bad Gateway…

System.Exception: Publishing the project has failed.

Error: Failed to process request. ‘Proxy Error ( Forefront TMG denied the specified Uniform Resource Locator (URL). )’.

The remote server returned an error: (502) Bad Gateway… —> System.InvalidOperationException: Failed to process request. ‘Proxy Error ( Forefront TMG denied the specified Uniform Resource Locator (URL). )’.

The remote server returned an error: (502) Bad Gateway… —> System.Net.WebException: The remote server returned an error: (502) Bad Gateway.
at System.Net.HttpWebRequest.GetResponse()
at NuGet.RequestHelper.GetResponse()
at NuGet.HttpClient.GetResponse()
at NuGet.PackageServer.EnsureSuccessfulResponse(HttpClient client, Nullable1 expectedStatusCode) --- End of inner exception stack trace --- at NuGet.PackageServer.EnsureSuccessfulResponse(HttpClient client, Nullable1 expectedStatusCode)
at NuGet.PackageServer.PushPackageToServer(String apiKey, Func`1 packageStreamFactory, Int64 packageSize, Int32 timeout, Boolean disableBuffering)
at NuGet.PackageServer.PushPackage(String apiKey, IPackage package, Int64 packageSize, Int32 timeout, Boolean disableBuffering)
at UiPath.Project.Deploy.ProjectPackageManager.Push(WorkflowProjectPackage pack, Int32 timeout)
at UiPath.Project.Deploy.ProjectPackageManager.PackAndPublish(WorkflowProject project, Int32 timeoutMS)
at UiPath.Project.ProjectManager.Publish(Int32 timeoutMS)
at UiPath.Workflow.ViewModels.MainViewModel.PackAndPush()
— End of inner exception stack trace —

Thanks!


#2

Hi kiran,

Are you able to login to Orchestrator? Your issue might be due to proxy.

Did you develop the workflow you are trying to publish with a different version than the current one (from where you are trying to publish)?


#3

Thanks ovi for the input.
The proxy server details helped to resolve the issue.

Thanks,
Kiran