Posts made by mattworley_6429

That's awesome, thanks!

Hi

I just upgraded from 4.1.17 to 4.1.20 and found that npm installs no longer work.

npm install logs show that npm first calls the registry with

https://myregistry.com/npm/<feedname>/<packagename>

This returns the package details data with no issues.

ProGet tells npm to get the package file at

https://myregistry.com/npm/<feedname>/<packagename>/-/<packagename>-<version>.tgz

This returns an HTTP 400 Bad Request.

Rolling back to 4.1.17 resolved the issue, even though the .tgz link was exactly the same.

Thanks

Product: ProGet
Version: 5.1.20

Actually - setting the WebUrl was advised by Ben above! Not sure what changed between then and now, but it works for me now.
Cheers,
Matt

Hey, weirdly I just revisited this last week. I had the same issues on trying to upgrade but found the fix.

Go to Settings > Advanced Settings and set Web.BaseUrl to your Proget URL e.g https://registry.example.com

Worked for me. Good luck.

Cheers
Matt

Hi, just tested with Proget 5.0.8 and the issue persists.

Hi Ben, thanks for your reply and sorry for the delay in getting back to you.

I just spun up a new docker instance of Proget 5.0.6 and tested again.

Web.BaseUrl was empty, but updating it to contain the full host did not fix docker login.

There is an nginx proxy in front of Proget in my setup. The following proxy settings are in the nginx config:

location / {
    proxy_pass http://127.0.0.1:5080;
    proxy_redirect off;
    proxy_set_header Host $http_host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Forwarded-Protocol $scheme;
    proxy_set_header X-Url-Scheme https;
    proxy_set_header X-Forwarded-Host $host:443;
    proxy_set_header X-Forwarded-Server $host;
    proxy_set_header X-Forwarded-Ssl on;
    proxy_set_header X-Forwarded-Port 443;
}

I can confirm that the WWW-authenticate header is returned and correct when browsing /v2/.

As mentioned above, I have no problems when falling back as far as 4.7.14 so this appears to be a regression?

Many thanks,
Matt

OK, if I roll back to 4.7.14 the Docker client will login with no issues.

Sorry to spam, but further to this, if I deliberately use an incorrect password with docker login I get this message:

Error response from daemon: Get https://myhost.net/v2/: denied: requested access to the resource is denied

If I use the correct password I get:

Error response from daemon: login attempt to https://myhost.net/v2/ failed with status: 401 Unauthorized

So I must have some screwed up permissions somewhere, but as mentioned this is just a vanilla deployment of the proget docker image. I had this working before with no issues (though likely with an earlier version if that could be making the difference).

I have NPM and NuGet feeds running and connecting with no issues on the same instance.

Please help me! :)

Thanks
Matt

Actually the base64 token creation and editing config.json doesn't work locally either - please ignore that part.

Hi there

I've just run a fresh install of proget and I'm having real problems with "docker login". I've tried a whole load of configurations with both Proget 5.0.4 and Proget 4.8.8 but nothing works. Here are steps to replicate with a fresh install of Proget 5.0.4 (running in Docker) without any permissions or accounts being played with:

1. Activate Proget
2. Create a new container feed.
3. From your terminal run "docker login -u Admin -p Admin host.name.net"

The result is always:

Error response from daemon: login attempt to https://host.name.net/v2/ failed with status: 401 Unauthorized

Browsing to https://host.name.net/v2/ (while logged in via the browser as Admin) returns:

code "UNAUTHORIZED"
message "Anonymous is not permitted to perform the Feeds_ViewFeed task for the current scope."

As a temporary work around I've found that I can create an auth token with:

echo -n 'Admin:Admin' | base64

And add that to my local docker instance's config.json, but that only works locally and is no use in CI environments etc.

Many thanks
Matt

Product: ProGet
Version: 5.0.4

That's great news. Thanks!

Hi there, do you plan to update your ProGet Docker image with the latest releases? https://hub.docker.com/r/inedo/proget/

Many thanks
Matt

Product: ProGet
Version: 4.8.2

By the way, some further information:

• If I view the package within the ProGet web app, there is no mention of symbols at all (being available or not)
• The nuget package definitely contains the .pdb and /src
• I'm testing with a .NET core package created with dotnet nugget pack, including symbols and source
• I'm only uploading the .symbols.nupkg file to ProGet as per the documentation.
• The Debug > Modules > Symbol Load Information dialog shows "Symbols not found on symbol server."

Thanks!

Hi there, I'm currently trialling ProGet but cannot seem to get package symbols working with Visual Studio with the Dockerized version of Proget. I understand from the documentation that full source serving won't work due to the indexer not being available. Is this indexer issue also the reason for symbols serving not working?

If that's the case, is it likely that the indexer will ever work with Docker and do you have any kind of time scale if so?

Many thanks!
Matt

Product: ProGet
Version: 4.7.13