Cannot connect to packages feed, the Deployment Settings may be invalid (#1651)

[akkapolk]

I try to remove my packages on my custom Orchestrator and then show message as below.
Could you help to suggest me, please?

Cannot connect to packages feed, the Deployment Settings may be invalid (#1651)

[satheeshkumar.a1]

Please check this link. Same error already raised in forum

Orchestrator error: "Cannot connect to package feed, the URL may be invalid."

I’m also facing the same error. Any suggestions ? Weird part is, when i’m publishing the package from UIPath Studio, the publishing is successful. It is only at the Orchestrator that i face this error EDIT: Found the solution If you are a Community Edition Orchestrator user, you also need to create your own feed in MyGet, and provide the URL feed and its API key in the Deployment tab, in the Settings tab. If you use a private MyGet feed, please use the URL provided under Your pre-authentica…

[codemonkee]

Can you share more information about how your Orchestrator is configured

User > Settings > Deployment tab

As well if you’ve made any custom changes to your Web.Config file?

Some additional resolutions:

• Check your Application Logs in the Event Viewer
• Validate your Deployment URL (alluded to above in your Deployment Tab)
• Ensure that File System Permissions on the configured NuGetPackage location are set correctly.

Cannot connect to the packages feed, the URL may be invalid - Troubleshoot Steps

Issue Description Already setup orchestrator and already connect the robot. When we publish the test project. This is successfully published based on the robot prompt but we cannot see the published package name at the Orchestrator. Troubleshooting steps (Solution could be either of the two described below) In the Event Viewer, one can see the error stating that access is denied for the folder in Orchestrator. Resolution 1#: The deployment URL needs to be empty by default. Please remove the …

[Heldroid]

Check that the ‘New Version’ default number is higher than the one you have in Orchestrator and manually type the new version for example 2.0