Hi @philipp-cender_3322 , Looks like you're making good progress :) I ran the command .\inedoagentservice.exe run but the command only stated that it does: "Starting agent connector to the otter-host-fqdn on port 8630" That's okay to see; it means that its working as expected. I there was an error, you would see it. But for Source 10.67.0.17 something like a token exception is stated In the screenshot, it seems okay and doesn't report an error. So I think it's okay? The exception message is some kind of OS-level error, and I'm not sure what it means exactly. But it's a SSL/TLS issue. In this case, if you search for the text of the error ("Die Anmeldeinformationen, die dem Paket übergeben wurden, wurden nicht erkannt" -- but perhaps English is better), you can probably get some details on how to fix it. It could be some obscure operating system configuration. If i open otter at Port 8630 (Agent Listener) on Firefox webbrowser i get something like that: PR_CONNECT_RESET_ERROR It's not possible to "browse" such a connection; the Inedo Agent uses a proprietary, TCP-based binary protocol. So you will always get errors if you try to browse, telnet, etc. Cheers, Alana

Hi @Justinvolved , That error message is coming from here: https://github.com/Inedo/inedox-git/blob/master/Git/Git.InedoExtension/Operations/CanonicalGitOperation.cs#L73 Basically, it means that value you've specified for From is not a known Secure Resource. It's not a common error, and is likely the result of deleting/re-adding something. I would remove the From argument from your OtterScript altogether (just leave it as Git::Checkout-Code;). I don't think you need it. Your build should already associated with a repository, branch, and commit. Cheers, Alana

Hi @hashim-abu-gellban_3562, Happy to hear the config fixed your issue on the clair container. In ProGet v2022 we moved the feed vulnerability source to the Reporting & SCA > Vulnerabilities > Configure Vulnerability Download Blocking page. You should be able to wire it up from there. I'll make sure to update our documentation with these changes as well. Thanks, Rich

@e-rotteveel_1850 thanks for explaining that, that's great to know! Sometimes it's almost impossible to learn how these feed/package types are actually used, especially since we don't develop in those languages and really just focus mostly on API reverse-engineering ;) FYI We are targeting late April for 2023.0 release

Hi @jim-borden_4965 ! I think that the "delete old versions" option of Retention Rules might be what you're looking for; that will let you keep the last "X" versions of each package. That, in combination with "unused versions" (i.e. not recently downloaded) typically cover nearly all desired retentions. As far as a "feed independent" API, that's on our list as a "nice to have", and I don't know how much of an API we'll get in the first version of ProGet 2023. The "hard part" is usually specifications/docs, so if you have any ideas we'd be very open! Currently, our idea is base it off of the upack api: https://docs.inedo.com/docs/upack-feed-api-endpoints Some things will be more difficult (or impossible?) than others. Especially for multi-platform package types like ruby, python. But TBD. Cheers, Alana

Great thank you!

Hello @atripp Thanks for sharing the code segment. I believe that the issue could be somewhere else and not related to Proget at this point. I attempted to push to Amazon ECR using the same nerdcrl and found that I'm able to push it just fine. This leads me to believe the problem is not with nerdctl or docker cli for that matter. I came across this thread which I feel does not serve as a proper documentation (but relatable though). Bottomline, I wouldn't want to break anything that is working fine. I'm going to deploy Proget on AWS Lightsail and compare with what's going on the k8s deployment. Btw, I upgraded my Proget to 22.0.26 and the result was the same.

Hi @e-rotteveel_1850 , sorry I missed the notification on this b/c of how I categorized this. Yes.. Q2 (late April for now) is the current plan, though this is something we would likely do after the main release.

Hi @falk-winkler_2111 , I believe in this case, you'll just enter the access token as the password, and select "Bearer" as the authentication type. Cheers, Alana

I now changed to 2022.25, and CURL uploads are working again. Thanks!

@ade8s_7742 so glad to hear that! It's really rare, but glad it wasn't database corruption!!

Hi @darturow_6059 , I think the equivalent to a "Generic Repository" would be ProGet's asset directory: https://docs.inedo.com/docs/what-is-an-asset-directory However, there is no "connector" possible, except to another ProGet asset directory. Cheers, Alana

Thanks for this information. I will monitor ProGet through the /health endpoint and forget the logs monitoring. Thanks again and have a good day.

Hi @atripp Thanks, that looks easy enough, So I will get to it :-) Justin

Hi David, I came across your post and noticed that you're experiencing an issue with Git source providers in BuildMaster. I understand that you're trying to use the "Get Git Source" command but can only get the source from the master branch. Based on the command you provided, it looks like you have the syntax partially correct. However, it seems that the code is being picked up from the master branch instead of the production branch that you specified. Have you tried specifying the branch name with the "refs/heads/" prefix? For example: bash Copy code Branch: refs/heads/PRODUCTION This may help in correctly identifying the production branch. Additionally, you mentioned that you have deleted the repo details from C:\BuildMaster_WEBTMP\SrcRepos, but are still facing the same issue. Have you tried clearing your Git credentials and re-entering them? It's possible that the issue may be related to authentication. Plus I was researching on Elmedia Player for Mac, and As someone who's been using Elmedia Player for Mac for quite some time, I can definitely say that it's a great media player that offers a lot of useful features. One thing I particularly appreciate about Elmedia Player is its ability to play virtually any video or audio format that you throw at it.

Kindly consider this closed. I deleted my nginx ingress controller completely and redeployed it from scratch (including the ingress) and voila! I was able to push and pull images again. I suspect my ingress controller might have got wonky, but its logs didn't show anything out of the norm.

Hi @Bob_4018 , Thanks for the heads-up! We've resolved this, and the link should now work: http://cdn.inedo.com/downloads/otter/OtterInstaller22.0.9_Offline.exe Cheers, Alana

Hi @martin-helgesen_8100 , You can aggregate multiple feeds using connectors: https://docs.inedo.com/docs/proget-feeds-connector-overview If you want to put all the packages in one feed, then after adding the connector you can use a "feed downloader": https://docs.inedo.com/docs/proget-feed-importing Cheers, Alana

Thanks! Looking forward to that.

Hi @informatique_1359, Good catch! I updated the Docker-Compose docs to reflect that. Thanks, Rich