Hi @arose_5538 , Looks like this was indeed a regression in 2024.23 as a result of upgrading the JSON library we were using... I guess it's a lot more strict. Of course, upack is also wrong, but for whatever reason it worked before. anyway it's an easy fix, and will be fixed in the next maintenance release (scheduled Feb 7) of ProGet via PG-2884. In the meantime, you can just downgrade to 2024.22. And I checked pgutil 2.1.0 will be released soon :) Cheers, Alana

@steviecoaster great news, glad you got it all working

Hi @kc_2466, Looks like download uses an API we haven't implemented. Didn't expect that it would use a different mechanism from install! I don't think we'll get a fix for this in tomorrow's release, but I'll schedule it for the following on Feb. 7 (should be v2024.26). Thanks!

@jimbobmcgee that's too bad it didn't work :( That's probably why we didn't update the page in Otter 2024 to work with those types from BuildMaster... and as you saw from the code, it's probably not trivial. I know that some of the other platform modernization efforts (especially with HTTP/S support) took a lot longer. I guess the only option for now is to just add a list of server names. This is still on our roadmap, but rewriting the page is more than we can do in a scope of a fix like this.

Hi @atripp , Thank you for your quick reply. We will try your suggested approach and migrate from OSS Index to ProGet's Vulnerability Database. We will also update our server installation. There are other libraries with the same issue, so your statement regarding the reliability of OSS Index as a data source seems to be accurate. Best regards

after upgrading to the latest version , we ran into the same problem and had to revert back to an earlier version . we are looking forward for the fix aswell

@lisama7982_5385 this would require using the Docker API, which is kind off a pain, but if you search for things like "how to tag an image with a digest usng Docker API" or something you should find it eventually You can also use the Docker CLI by doing something like docker pull using the digest, then docker tag, then docker push. If this is a one-time clean-up you may also wish to query the database tables, like Docker* tables will allow you to eventually find what images you need to tag. Just don't delete from the database, since that can cause a headache and it won't delete files from disk Hope that helps :)

I don't agree with you. Sorry. Configuration is very simple and we are 100% sure that everything is ok with connection string. It was tested. So ok, we will buy a payment version and we will send a request to support. Thanks for help.

@jimbobmcgee thank you again for the very detailed analysis; we will get this fixed via OT-515, it's most an easy encoding to add

Hi @MY_9476 , Thanks for the heads up! We will fix this via OT-514 in the next maintenance release. As an FYI, this is the code that should have been run at the end of the database upgrade, to ensure that all procs and table-value params have appropriate permission: DECLARE @SQL NVARCHAR(MAX) SET @SQL = '' SELECT @SQL = @SQL + 'GRANT EXECUTE ON TYPE::' + QUOTENAME(name) + ' TO [OtterUser_Role] ' FROM sys.table_types SELECT @SQL = @SQL + 'GRANT EXECUTE ON ' + QUOTENAME(name) + ' TO [OtterUser_Role] ' FROM sys.procedures EXEC sp_executesql @SQL The script you ran works too :)

hi @hammel_7023 , Thanks for letting us know, you are correct... this is indeed a regression from PG-2859. What's happening is the upload stream is getting prematurely closed during the POM validation logic, which is what's causing this error to occur. I've just patched it now via PG-2868, and it'll get in the next maintenance release. Cheers, Alana

@jimbobmcgee excellent thanks!! Release has been published then :)

Hi @nachtmahr , It sounds like your Windows Integrated Authentication is broken. This is an operating-system level feature, and the only thing you can do in ProGet is turn it on, or turn it off. WIA is pretty buggy these days, and sometimes it just breaks. Here is more information: https://docs.inedo.com/docs/installation/security-ldap-active-directory/various-ldap-integrated-authentication Hopefully just doing a reboot of the server will fix the problem. If not, then you'll have to troubleshoot it, which kind of sucks: https://docs.inedo.com/docs/installation/security-ldap-active-directory/various-ldap-troubleshooting#integrated-authentication-not-working Note that you can disable WIA by using the Locked Out protocol: https://docs.inedo.com/docs/installation/security-ldap-active-directory/various-ldap-troubleshooting#locked-out-restoring-default-admin-account Hope that helps, Alana

Thanks @steviecoaster! All that sounds great, especially since it won't require changing anything on our end :) Much appreciateD!!

Hi @dean-houston , Thanks for your response, at the end, we come to the same conclusion that something went wrong during the upgrade and some of the configuration blobs got deleted from the disk and also from the database table. Luckily, we have the backup, but we need to figure out which images are corrupted and need to be recovered. Gabor

Hi @monika-sadlok_5031, That error means that the ProGet application container cannot make a network connection to the the SQL Server container. I would try to restart the containers, start with SQL Server. Make sure it's running. If it's running, you can try connecting to it with another tool like SSMS if you'd like to verify.' Otherwise, on the ProGet side, you can only configure the connection string; upgrading or changing the license key has zero impact on this. If it worked in the past, then it means that the SSQL Server container is not running or your network/container configuration changed. This can be hard to discover exacgtly what changed, so I would recommend "starting from scratch" on a new server/environment, then compare/contrasting what changed. Sometimes it's as simple as a typo or an errant - (dash character) in the wrong place/script. Cheers, Alana

Hi @forbzie22_0253 , Similar to the UI, packages are still returned in the API - they just have a flag set to indicate they are unlisted/deprecated. It's up to the client to determine what to do about that. I don't believe the Find-Package cmdlet works with these properties; I think only Visual Studio will hide/warn about them. Thanks, Alana

Dear @dean-houston , Thanks for your guidance. Following the steps in the provided Docker guide, I was able to successfully build a multi-platform image, and the “Fat Manifest Image” information now appears correctly in ProGet. This resolves my question, and I really appreciate your help in clarifying the process.

hi @jaehyung-shin_8059 , If you click on the latest tag, do you see any information about the packages in the container? Container images are scanned on upload if they are small or queued to be scanned in the background if they are large. There are sometimes errors scanning containers, and if so, these errors will be logged... typically under Admin > Executions. -- Dean

@parthu-reddy yes, but we do recommend migrating... There are some known bugs/quirks with Maven (Classic) feeds and we will not fix them. We will likely not migrate them to PostgresSQL, which means you won't be able to migrate to PostgreSQL in ProGet 2025+. So it's likely that ProGet 2027 will not support them.