Apply license key inside container

[jlarionov_2030]

I'm testing out running ProGet via a container based on Docker Installation Guide - Inedo Documentation. I'm using the image proget.inedo.com/productimages/inedo/proget:25.

How do I programmatically apply the license key to the ProGet instance inside the container?

Usually we use Inedo Hub for this but that doesn't seem to be included inside the container image.

[stevedennis]

Hi @jlarionov_2030 ,

As of ProGet 2023 (or maybe earlier?), license keys are no longer requested / entered at installation time, but in the software itself now. This only matters on new instances.

You can use pgutil settings to set a license key if you'd like.

Thanks,
Steve

[jlarionov_2030]

@stevedennis Trying to use pgutil settings list with a fresh ProGet container gives me the following error:

[vagrant@localhost ~]$ pgutil settings list
'<' is an invalid start of a value. Path: $ | LineNumber: 0 | BytePositionInLine: 0.

Here's my pgutil config:

[vagrant@localhost ~]$ cat ~/pgutil/pgutil.config
{
  "sources": [
    {
      "name": "Default",
      "url": "http://localhost:8624"
    }
  ]
}

However once I enter the license key via the web UI, the pgutil settings list command successfully lists all the instance settings.

[stevedennis]

Hi @jlarionov_2030,

I haven't tested or tried it, but I can't help but wonder the API is responding with some kind of "license required" error, and blocking the seting.

I suppose we could investigate and try to resolve the error, but automated setup with a license key isn't so common of a requirement.... if tis is not really something you will do that often, perhaps it's not worth the effort.

Let us know your thoughts.

Thanks,
Steve

[jlarionov_2030]

@stevedennis We run a lot of automated tests against ephemeral instances of ProGet in CI environments, so we need a programmatic way to apply a license key.

[atripp]

Hi @jlarionov_2030 , easy change! We will not require a valid license for Settings API Endpoint going forward; PG-3133 will ship in next maintenance release, scheduled for Friday.

[jlarionov_2030]

@atripp That did the trick. I'm able to use pgutil now to set an API key and fully automate ProGet setup. Thank you!

[jlarionov_2030]

@atripp This issue has resurfaced. I confirmed it was fixed in 2024.39 but it's failing in the same way again in 2025.18.

When calling pgutil apikeys create system I get the following error:

Downloading InedoHub.
Gathering package information...
Installing MSVC runtime...
Downloading ProGet-25.0.18.upack...
Installing ProGet...
ProGet 25.0.18 installed.
Downloading pgutil v2.2.4.4
Creating API key.
'<' is an invalid start of a value. Path: $ | LineNumber: 0 | BytePositionInLine: 0.

[jlarionov_2030]

I have confirmed that the issue was reintroduced with version 2025.0 (it was last working in 2024.39).

[atripp]

Hi @jlarionov_2030 ,

PG-3133 (which allowed pgutil settings to run without a license key) was applied to ProGet 2025.12 so I don't think it could have worked in ProGet 2024.39.

There were also no changes from ProGet 2025.12 to 2025.18 that would have caused this, and it works fine for me.

Are you sure you're running the pgutil settings command first to apply a license key?

Just based on the logs, it doesn't say...

Thanks,
Alana

[jlarionov_2030]

@atripp I'm sorry, you're absolutely right. It does indeed work with version 2025.18. I simply forgot to apply the license key with pgutil before attempting to create the API key. Then I confused myself more when 2024.39 wasn't throwing the same error (because I was still setting the license with the --LicenseKey Inedo Hub option).

For anyone stumbling here in the future like me, here's what you need to do to apply the license key and create an API key with pgutil:

pgutil sources add --name=Default --url=http://localhost:8624
pgutil settings set --name=Licensing.Key --value=LICENSE-KEY-GOES-HERE
api_key=$(pgutil apikeys create system)