Uploading manually of your package should not result in a 405 error.
- how did you setup your tenant? (did you add the licenses to it?)
- Did you add your machine to the Tenant?
- Did you add a robot to your Folder and selected the machine?
- Which type did you use for the license of the robot?
There are several methods of publishing your package to Orchestrator. But make sure that the conditions are set correct!.
1. Publish locally.
Disconnect Uipath Assistant.
Start UiPath Studio. Open a project and click on publish
Check your Publish settings. “Assistant (Robot Defaults)” should be selected
This will publish your package in C:\ProgramData\UiPath\Packages
Then upload it manually to Orchestrator in https://cloud.uipath.com/TENANT/TENANT/orchestrator_/packages
2. Publish straight to Orchestrator.
Add your Studio machine as a machine to your Tenant.
Connect UiPath Assistant to Orchestrator based on the Machine key
This is not enough to being able to publish to Orchestrator. Because if you want to publish to orchestrator it will result in a 405 error.
You have to add a Robot for it.
For example i have a Classic Folder “Homelab”
In that folder i can add a Robot. So i called it DRAGON as you can see. Set the type to "Attended (RPA Developer Pro).
Reconnect your Uipath Assistant. It should be Connected and licensed and in your orchestrator it should be online in your Folder > Robots
Now open Studio again (close it when you had it still open). Open your project and click on the Publish button.
Now when you want to publish you can see a new setting as default: “Orchestrator Tenant Process Feed”. By default it should be set to that selection.
So now when you publish it will be published to Orchestrator.
Lets check in Orchestrator on Tenant level in packages
And there it is. You can check the detail info to see if it is the correct version of the package.
I hope this will help you a bit.
also check this page: About Publishing Automation Projects.
The only reason for using a custom Url is when i publish my package to a Nexus3 server. That is where i use the ApiKey for. I never used the ApiKey from Orchestrator.
But i think the 2nd option would apply to you.
Option 1 is most of the time used when a direct connection to Orchestator is not allowed or possible.
Option 2 gives more freedom and speed for deployments
Option 3 you will use when you use your own repository server (for example Nexus), so you don’t want orchestrator to be your primairy package server.
At others. If there are better options in the meantime feel free to correct me. I don’t use uiPath on a daily bases, so this is to the best of my knowledge