@atripp Good news Thank you

@rhessinger Good news thank you

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

That's amazing! Thanks so much @rhessinger You guys rock!

@ludovic_2596 this sounds familiar, from an early version of 5.3, but I can't find a report for it. It seems to work fine in the latest version for me.. can you try the upgrade?

@scroak_6473 got it, thanks! Okay, I've requested to engineering about adding it to the upcoming ProGetCore container, and we'll update this with more details as we have i

hi @Adam1, I looked into this further, and this is by design, but it should really be clarified in the UI a little bit better (I updated the docs). A server can exist in multiple environments, but it's not recommended. Basically, when a server is in multiple environments, then there can be no single environment in context. This means that the variable function $EnvironmentName will return empty, and variables cannot be resolved against those environments. This is unlike a role (which is set when executing a configuration plan, or explicitly set with for role X). So, in this case, I recommend you to use multiple roles.

hi @Adam1; thank you for the detailed reproduction instructions. You are correct, this is indeed a bug, and it will be fixed in the next maintenance release (scheduled for Friday) as OT-381. If you'd like a pre-release, we can easily share one to you as well!

Hi @jyip_5228, That may be your issue. NuGet is currently on version 5.7. Could you please try upgrading your NuGet.exe and see if that fixes the issue? Thanks, Rich

Thanks for this detailed description Thats for sure a misleading search design decision...

Hi @gravufo, Thanks for following up. Glad to hear it is working! Thanks, Rich

Thanks for the information :)

Since there is no further update and no solution for my problem using nuget cli or dotnet cli I am closing this thread.

Hi @john-b_3261 , Can you please verify that your ProGet windows service is running and that the account the service is running under has access to those folders? Our nightly cleanup scheduled jobs typically clean up these folders./ Thanks, Rich

Hi @atripp, My fault... I'd referenced a user specific path that the service could not access. now it's working Thank's for the support :)

Hi @Joseph-Saladino_7499, What version of BuildMaster are you currently running? In BuildMaster 6.2 there is a history on pipeline changes. You would view it by clicking on Deploy -> Deployment Pipelines and then clicking on the last modified date for the pipeline you would like to see history for. Here is a screenshot of the UI: [image: 1597347945067-c1e389eb-2c01-41ab-be91-c5b4de31bf86-image.png] [image: 1597347983256-70acdd17-5c2d-4f36-9c05-f49dec1d00d1-image.png] Hope this helps! Thanks, Rich

Fantastic, looking forward to it! Sorry for the work, but i'm happy to contribute in some small way as well!

Hi @scroak_6473, I created a branch and a blank page on GitHub for Docker Swarm. You should be able to add your notes and examples there. Please let me know if you have any issues! Thanks, Rich