Thanks for reaching out Andres. I’m sorry that you are experiencing this issue.
So I can determine if this issue happened to the artifacts during the upgrade, or if it is a problem with all artifacts on the version 2022.2.6895, can you create a new artifact and check the Content link?
Did you move any folders during the upgrade or was everything left as it was?
Thanks for the extra information. We can definitely progress from here.
Because the new artifacts are still not accessible, there is definitely a chance that we may have a permissions issue on our hands.
Can you please provide the following information:
If you navigate to the artifacts folder, can you see new artifacts being created?
Generally Octopus will try to write to the artifacts folder using the Octopus Deploy Service user.
What is the user that Octopus Server runs under?
Is it System or is it a specific account?
Does that account have read/write permissions to the artifacts folder?
Would you be able to provide a HAR file when you attempt to download an artifact? Open up the Developer console, create the release and then click on the artifact, before exporting the HAR file. This should provide some good information for us to determine what the issue is.
There has been an investigation into some very slow artifact retrieval times (sometimes resulting in handing processes) in the latest versions of Octopus. I think this is likely the issue that you are running into.
A Pull Request with some code amendments that should vastly improve artifact retrieval times was raised earlier today. The Pull Request needs to go through testing and roll-out to the early adopters before it is available to everyone else. This means, unfortunately, we are likely a few weeks away from having that release made available to our GA release stream.
Here’s a screenshot of the results that one of the engineers achieved when testing this change:
If you subscribe to this issue you will be informed in the comments on what version of Octopus Deploy the issue will be fixed in. Once it appears in the comments it can still be a few days before the version is available on the downloads page.
In the meantime, you might have to access these artifacts directly via the artifacts folder.
As for a JFrog feed, this could potentially help, but I would say that if you can hold out for a couple of weeks, you would save the effort of changing your infrastructure and introducing another component like artifactory.
Please let me know if you have any more questions.