ProGet license injection in AKS Pod

[certificatemanager_4002]

I'm currently lauching Proget 25.0.18 in AKS the pod start correctly
with those ouputs:

 upgradedb ProGet version is 25.0.18.12.                                                                                                                
upgradedb Current DB schema version is 25.0.18.12.  
but logs show:
proget info: Microsoft.AspNetCore.Hosting.Diagnostics[1]                                                                                               │
│ proget       Request starting HTTP/1.1 GET http://10.200.0.194:80/health - - -                                                                         │
│ proget info: Microsoft.AspNetCore.Hosting.Diagnostics[2]                                                                                               │
│ proget       Request finished HTTP/1.1 GET http://10.200.0.194:80/health - 500 673 application/json 15.1132ms                                          │
│ proget Running Failover Detection...                                                                                                                   │
│ proget Failover Detection completed.                                                                                                                   │
│ proget info: Microsoft.AspNetCore.Hosting.Diagnostics[1]                                                                                               │
│ proget       Request starting HTTP/1.1 GET http://proget.apps.uat-internal.swisstiming.com/ - - -                                                      │
│ proget info: Microsoft.AspNetCore.Hosting.Diagnostics[2]                                                                                               │
│ proget       Request finished HTTP/1.1 GET http://proget.apps.uat-internal.XXXXXXX.com/ - 200 5691 text/html;+charset=UTF-8 1.6095ms               │
│ proget info: Microsoft.AspNetCore.Hosting.Diagnostics[1]                                       

When I start the command in the pod

curl http://localhost/health
{
  "applicationName": "ProGet",
  "databaseStatus": "OK",
  "databaseStatusDetails": null,
  "extensionsInstalled": {
    "ProGet": "25.0.18",
    "Inedo.SDK": "3.1.0",
    "InedoCore": "3.0.6",
    "Azure": "3.1.2",
    "Google Cloud": "3.1.0",
    "Amazon AWS": "3.1.3"
  },
  "licenseStatus": "Error",
  "licenseStatusDetail": "License key has expired.",
  "versionNumber": "2025.18 (Build 12)",
  "releaseNumber": "25.0.18",
  "startTime": 1770974767402,
  "serviceStatus": "OK",
  "serviceStatusDetail": null,
  "replicationStatus": {
  "serverStatus": null,
  "serverError": null,
  "clientStatus": null,
  "clienterror": null,
  "incoming": [],
  "outgoing": []
}

My point is coming from the fact that I don't have any idea to inject the license key in the pod

[atripp]

Hi @certificatemanager_4002 ,

The license key is set via the UI, so you can browse/access the service as per normal. Then, you will prompted to do that right away when there is no key or it expired: https://docs.inedo.com/docs/myinedo/activating-a-license-key

Thanks,
Alana

[certificatemanager_4002]

Hey,
I understand the license,
But regarding the error 500, I have no information, Proget do not provide enough logs to understand this point.
I think my blocking point is coming from that.
Regards

[atripp]

hi @certificatemanager_4002 ,

The 500 is occurring on /health because licenseStatus=Error and the software is basically unusable until you correct the license issue.

You would see a similar "blocking" error in the ProGet UI as well - so just check that, and once you correct the license error, the health check will return to normal..

Thanks,
Alana