Navigation

    Inedo Community Forums

    Forums
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. viceice
    3. Topics
    V
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by viceice

    • V

      [ProGet] Manual database upgrade (docker, kubernetes)
      Support • • viceice  

      21
      0
      Votes
      21
      Posts
      76
      Views

      stevedennis

      @saml_4392 in theory it's fixed, but we didn't test it Could you open a new thread about a creating a Helm chart for ProGet itself? That'd be a great place to start that discussion, and get community direction and feedback from users - and provide nice opportunities to partner with organizations like bitnami, who could help
    • V

      NullReferenceException at Inedo.ProGet.Feeds.NuGet.NuGetConnector.FindPackagesByIdAsync
      Support • • viceice  

      7
      0
      Votes
      7
      Posts
      40
      Views

      atripp

      Hi @RobIII , Thanks for sending that over; we've reviewed it, but nothing is jumping out as a problem. I'm thinking it's something else... Can we do this? At first, let's move this to a new topic. I'm going to lock this thread, can you reply as a new topic? The reason for this is so that we can track much easier. Is it possible to share access to your GitLab repository? That's the easiest thing of course, but you say "on-prem" so maybe not so easy. As an alternative, can you create a simple reproduction case using a public GitLab repository? This way, we can plug ProGet into it, attach a debugger, and figure out what's going on. The most likely scenario is that GitLab doing something wrong/weird against the spec, but it just happens to work in Visual Studio. That was the sitaution of GitHub. Thanks, Alana
    • V

      docker login failed via https reverse proxy
      Support • • viceice  

      18
      0
      Votes
      18
      Posts
      78
      Views

      rhessinger

      Hi @viceice, I did a few searches and have you tried setting the hostsProxyHeaders> Maybe something like this: traefik.frontend.headers.hostsProxyHeaders=www-authenticate? The docs make it sound like it will look in those headers for URLs that are proxied. You could give that a shot. Thanks, Rich
    • V

      A 500 error occurred in d: Could not find a part of the path '/var/proget/packages/.docker/F1
      Support • • viceice  

      13
      0
      Votes
      13
      Posts
      33
      Views

      H

      @rhessinger great :)
    • V

      Docker: 5.3.12 (dotnet core) hung
      Support • • viceice  

      17
      0
      Votes
      17
      Posts
      51
      Views

      rhessinger

      Hi @viceice, That error is safe to ignore. It is currently a known bug and we are looking to fix that in an upcoming version of ProGet. The ticket tracking the fix for the log message is PG-1841. Long story short, the ProGet service correctly detected that the product wasn't activated, and then logged that message. But it was doing it every time it accessed license information, which is on every connector health check, replication run, etc. Activation happens automatically as soon as someone visits the Web application, and re-activation is required after upgrading certain versions. Thanks, Rich
    • V

      How to configure the proget free with self-connector
      Support • • viceice  

      13
      0
      Votes
      13
      Posts
      42
      Views

      rhessinger

      Hi @viceice, Thanks for the clarification on your environment! I see what is going on now. I have created a ticket, PG-1809, to track the fix for this. We expect this to be released in ProGet 5.3.11 which we are expecting to be released in September 11, 2020. Basically in that instance, we are not respecting the values within the X-Forwarded-* headers. I'll let you know if anything changes on the timeline. Thanks, Rich
    • 1 / 1