Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
ProGet Free license violations detected
-
Hi,
We've upgaded ProGet Free from 5.2 to 5.3.28 the other day, and I noticed the "Error: ProGet license violations detected." message today.
When I go to the licence violation list, there's nothing useful telling me what are the violations.
How do I resolve them?
Thank you,
Marko -
Hello,
This typically comes from having one ProGet Free instance connect to another ProGet instance.
You can clear the license violations here: https://docs.inedo.com/docs/proget/administration/license
Cheers,
Alana -
Hi,
We are running a single ProGet instance, but we do have connectors which connect to it.
The reason for that is that we host a pair of PowerShell and a pair of Chocolatey feeds (test and production for each). The feeds host a mix of public and our own modules and packages.
We publish our own modules/packages to test feeds, and we pull in modules and packages from PS Gallery and Chocolatey. We only attach PS Gallery/Chocolatey connectors to test feeds when pulling modules/packages.
We have connectors to our test feeds, which we then attach to our production feeds, and use them to pull "vetted" modules/packages from our test feeds.
Is that ok? v5.2 never complained about this approach.
Cheers,
Marko -
Hi @bozho_2851,
Does your ProGet instance sit behind a proxy, like nginx? We have seen this issue with self connectors when connecting to itself via the proxy address. If so, you can try to use the hostname of the server or
127.0.0.1in your URL in place of the FQDN.Thanks,
Rich -
Ah, that did it. Thank you!
I did manage to clear the violations list by reactivating the licence, but I still get the "Error: ProGet license violations detected." banner, even though the violations list is empty now.
Cheers,
Marko -
Hi @bozho_2851,
You may have to restart your ProGet webserver (IIS or Integrated Web Server) to clear this message. You shouldn't need to but the violation may still be cached and restarting the webserver may correct this for you.
Thanks,
Rich -
It cleared up on its own.
Thank you very much for your help,
Marko
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login