@atripp Can I add a +1 for adding support for proxying Debian/APT repositories please.

We're also having to use another product for that functionality, when it would be nice to be able to have all of our artifacts available in one place.

Thanks,
Rob

Hi @atripp

That's great - I look forward to testing this out.

Cheers,
Rob

Are there any updates on this please?
Just wondering if a Connector for Debian/APT repositories has made it onto the roadmap yet?

Thanks,
Rob

Thanks Alana,

I had tried giving myself sysadmin rights previously, but was still getting permission errors.
The trick from that article, to put the database in single user mode first, got things working.

Cheers,
Rob

Hi,

I'm trying to upgrade an instance of ProGet Free from 2022.14 to 2022.17.
This is a default installation using the bundled SQL database.

The initial installation was done by UserA. I'm trying to perform the upgrade as UserB.

When UserB starts Inedo Hub, rather than seeing an Upgrade button, there's a View Error button, which indicates:

System.Data.SqlClient.SqlException (0x80131904): Cannot open database "ProGet" requested by the login. The login failed.
Login failed for user 'DOMAIN\UserB'

Clearly UserB doesn't have access to the database, as (presumably) it's running with the Integrated Security enabled.

Data Source=localhost\INEDO;Initial Catalog=ProGet;Integrated Security=True

As a complete novice to MS SQL server, what steps need to be taken to give UserB the right permissions?

Cheers,
Rob

Hi,

I'm trying to upload a large (bigger than 4GiB) Universal Package to a feed using curl, which is failing with the following error.

> PUT /upack/test-feed HTTP/1.1
> Host: proget.internal:8624
> Authorization: Basic xxxxx
> User-Agent: curl/7.74.0
> Accept: */*
> Content-Length: 4404364110
> Expect: 100-continue
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 413 Request Entity Too Large
< Content-Type: text/html
< Server: Microsoft-IIS/10.0
< X-Powered-By: ASP.NET
< Date: Tue, 22 Nov 2022 10:48:04 GMT
< Connection: close
< Content-Length: 67
<
* Closing connection 0
The page was not displayed because the request entity is too large.

From previous forum posts, this looks like it could be down to an IIS configuration setting, but nothing I've changed seems to have had any effect. I'm assuming a value of 0 should remove the limit.

system.web/httpRuntime/maxRequestLength = 0
system.webServer/serverRuntime/maxRequestEntityAllowed = 0

• ProGet version 2022.14
• IIS v10

I can see that the asset directory API has a multipart upload feature. Is there an equivalent for uploading to feeds?

Cheers,
Rob

@atripp Can I add a +1 for adding support for proxying Debian/APT repositories please.

We're also having to use another product for that functionality, when it would be nice to be able to have all of our artifacts available in one place.

Thanks,
Rob