Publishing from Studio failure – Cannot connect to packages feed

When publishing from Studio an error is encountered that says, "Cannot connect to packages feed, the deployment settings may be invalid".

When publishing from the Studio the following error is encountered.

Error: System.ApplicationException: Publish of workflow project to Orchestrator failed. Cannot connect to packages feed, the Deployment Settings may be invalid. ---> UiPath.Ipc.RemoteException: Cannot connect to packages feed, the Deployment Settings may be invalid.
 
This error happens when Orchestrator is having issues with its Deployment URL. It can be caused by a variety of things (DB can be full, the URL is invalid, Orchestrator is missing permissions).

Troubleshooting the issue
  1. Try manually uploading a package from the Orchestrator URL. Most likely this test will fail, but the error message Orchestrator generates could help determine the issue.
    <ol style="list-style-type: lower-alpha;"><li><span style="font-size: 11pt;" uipath_custom_id="31"><span style="line-height: 107%;" uipath_custom_id="32"><span style="font-family: Calibri,sans-serif;" uipath_custom_id="33">If Orchestrator generates a 1651 error when uploading packages, search that error code in our KB articles. </span></span></span></li><li><span style="font-size: 11pt;" uipath_custom_id="34"><span style="line-height: 107%;" uipath_custom_id="35"><span style="font-family: Calibri,sans-serif;" uipath_custom_id="36">If an unknown error occurs, check the Orchestrator DB. The database could be full, or Orchestrator could be missing a database permission.</span></span></span></li></ol>
    </li><li><span style="font-size: 11pt;" uipath_custom_id="37"><span style="line-height: 107%;" uipath_custom_id="38"><span style="font-family: Calibri,sans-serif;" uipath_custom_id="39">The best solution is to check the event viewer logs on the Orchestrator server.</span></span></span>
    <ol style="list-style-type: lower-alpha;"><li><span style="font-size: 11pt;" uipath_custom_id="40"><span style="line-height: 107%;" uipath_custom_id="41"><span style="font-family: Calibri,sans-serif;" uipath_custom_id="42">Login to the Orchestrator Server as an Admin.</span></span></span></li><li><span style="font-size: 11pt;" uipath_custom_id="43"><span style="line-height: 107%;" uipath_custom_id="44"><span style="font-family: Calibri,sans-serif;" uipath_custom_id="45">Open a Run window and type “eventvwr” – This will open the Event Viewer.</span></span></span></li></ol>
    </li></ol>
    
      1. In the Event Viewer window, go to “Event Viewer (Local) -> Windows Logs->Application
      2. Click “Filter Current Log…” in the right “Actions” pane window.
      3. In the “Filter Current Log” dialog box, choose the Event Source: “Orchestrator”. Then select “OK”.
      1. Force the error to occur by trying to upload a package to Orchestrator.
      2. In “Event Viewer” click “Refresh” in the “Actions” pane in the left menu.
      3. See if there are any new error messages or warnings.
    1. Search or KB articles for any errors or warning found in the Event Viewer logs on the Orchestrator server.
    2. Consider opening a support request with UiPath.