Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login
    1. Home
    2. felfert
    3. Posts

    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!

    felfertF Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 11
    • Posts 57
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: pgutil health fails after updating to proget 2026

      Thanks a lot @atripp for the quick fix. Problem solved 😊

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • pgutil health fails after updating to proget 2026

      Subject says it all:

      [root@gsg1repo ~]# pgutil health
Checking http://localhost:8080/...Server responded with OK (200): Unexpected server response ('O' is an invalid start of a value. Path: $ | LineNumber: 0 | BytePositionInLine: 0.)

      Looking into the source, it attempts to GET /health and expects some json, but proget just replies with OK. So apparently the api endpoint has changed. I could create a PR, but where is the API endpoint doc for 2026?

      Thanks
      -Fritz

      Later: Never mind my first question, found it. BUT apparently (according to the API doc) there is no global health api? I found only feed-related health?!

      posted in Support
      felfertF
      felfert
    • proget.inedo.com DDOSed?

      Visiting https://proget.inedo.com responds with a 500, saying

      (500) Server Error
The connection pool has been exhausted, either raise 'Max Pool Size' (currently 100) or 'Timeout' (currently 15 seconds) in your connection string.

For more information, visit the Error Log Page.

      At the bottom, it says:

      Inedo Edge 2 Download Center (Powered by ProGet ISV Edition)

      Just in case you haven't noticed yet.

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: Debian feed broken after upgrade to 2025.14

      @gdivis
      Too bad I already changed all my keys and updated a lot of Test-VM-Instances in an internal OpenStack. Would have been be MUCH less work. Oh well.
      Thanks anyway for the info 👍
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: Debian feed broken after upgrade to 2025.14

      @dean-houston

      I can confirm, that regenerating the signing keys of all debian feeds solved the problem.
      Thanks for your support.

      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: Debian feed broken after upgrade to 2025.14

      @dean-houston

      Hi Dean,
      Yes of course. I already expected that, so I'm currently creating a second sandbox instance of proget where I can play around freely. On that instance I will try to reproduce this and analyze it in depth. I will come back to you, when I have analyzed this issue.

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • Debian feed broken after upgrade to 2025.14

      FYI: Debian feed appears to be broken after upgrade to 2025.14. (host: Rocky9, podman, quadlets, postgres)

      Nothing has changed in the feed data and all packages appear to be present in the proget gui of the feed. Yet, an ubuntu client instance (Tested both jammy and noble) cannot find any packages when attempting to install packages from that feed. Client config (apt sources and keys) had been unchanged as well.

      After switching back to the previous image (2025.13), everything is back to normal.

      CU
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: Upgrade from 2025.13 to 2025.14 failed (Linux, PostGres)

      @rhessinger

      Well, after restarting with the 2025.14 image that I pulled this morning, now the warning is gone. Guess this was some outlier then ...

      Thanks
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: Upgrade from 2025.13 to 2025.14 failed (Linux, PostGres)

      @rhessinger said in Upgrade from 2025.13 to 2025.14 failed (Linux, PostGres):

      Next time you attempt to update to the new image and see this issue, could you provide us with the output from the start of your container?

      Luckily, as I use quadlets, those save any output in the system journal (prefixed by a timestamp hostname and process-name and PID), so here we go (output of the container start after upgrading):

      Nov 11 07:24:04 gsg1repo.graudatastorage.intern systemd-proget[2188]: Running Node Message Cleanup...
Nov 11 07:24:04 gsg1repo.graudatastorage.intern systemd-proget[2188]: Purging processed node messages and messages older than 11/11/2025 06:19:04...
Nov 11 07:24:04 gsg1repo.graudatastorage.intern systemd-proget[2188]: No messages to purge.
Nov 11 07:24:04 gsg1repo.graudatastorage.intern systemd-proget[2188]: Node Message Cleanup completed.
Nov 11 07:24:08 gsg1repo.graudatastorage.intern systemd-proget[2188]: Running Execution Dispatcher...
Nov 11 07:24:08 gsg1repo.graudatastorage.intern systemd-proget[2188]: Checking for executions to dispatch...
Nov 11 07:24:08 gsg1repo.graudatastorage.intern systemd-proget[2188]: Execution Dispatcher completed.
Nov 11 07:24:11 gsg1repo.graudatastorage.intern systemd-proget[2188]: Running Service Heartbeat...
Nov 11 07:24:11 gsg1repo.graudatastorage.intern systemd-proget[2188]: Service Heartbeat completed.
Nov 11 07:24:13 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:13 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/0x44/proget/Inedo.ProGet.WebApplication.Controls.Layout.NotificationBar/GetNotifications - - -
Nov 11 07:24:13 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:13 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/0x44/proget/Inedo.ProGet.WebApplication.Controls.Layout.NotificationBar/GetNotifications - 200 30 - 9.0162ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/ - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/ - 200 2396 text/html;+charset=UTF-8 20.9222ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/styles/nonmodal.css?982.0.14.1 - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/styles/nonmodal.css?982.0.14.1 - 200 287426 text/css 3.8453ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/jquery.min.js?982.0.14.1 - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.min.css?982.0.14.1 - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/AH/AH.js?982.0.14.1 - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.min.css?982.0.14.1 - 200 15009 text/css 3.3284ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.structure.min.css?982.0.14.1 - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.structure.min.css?982.0.14.1 - 200 14764 text/css 1.3230ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.theme.min.css?982.0.14.1 - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.theme.min.css?982.0.14.1 - 200 13273 text/css 1.2690ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/AH/AH.js?982.0.14.1 - 200 39298 text/javascript 6.4919ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/jquery.min.js?982.0.14.1 - 200 95931 text/javascript 9.4936ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.hacks.css?982.0.14.1 - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.hacks.css?982.0.14.1 - 200 1188 text/css 0.7342ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/inedojq/inedojq_frameddialog.js?982.0.14.1 - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/inedojq/inedojq_frameddialog.js?982.0.14.1 - 200 4060 text/javascript 0.7150ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.min.js?982.0.14.1 - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/pages/rootpage.cs.css - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/styles/darkmode.css?982.0.14.1 - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/pages/rootpage.cs.css - 200 859 text/css 1.5545ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/styles/darkmode.css?982.0.14.1 - 200 126182 text/css 3.2267ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/jquery-ui-1.11.4/jquery-ui.min.js?982.0.14.1 - 200 228776 text/javascript 7.7990ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/styles/proget.css - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/styles/darkmode.proget.css - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/styles/darkmode.proget.css - 200 100060 text/css 1.9657ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/styles/proget.css - 200 115024 text/css 3.2218ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/knockout/knockout-3.3.0.min.js?982.0.14.1 - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/knockout/knockout-3.3.0.min.js?982.0.14.1 - 200 55956 text/javascript 2.3553ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Scripts/chart.min.js - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Scripts/chart.min.js - 200 63686 text/javascript 1.2836ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Scripts/piechart.js - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Scripts/dp_pie-chart.js - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Scripts/piechart.js - 200 977 text/javascript 1.2846ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Scripts/dp_pie-chart.js - 200 1622 text/javascript 1.4509ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/images/layout/logo-white.svg - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/images/layout/logo-white.svg - 200 1374 image/svg+xml 0.8991ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 POST http://proget.graudatastorage.intern/ - application/x-www-form-urlencoded;+charset=UTF-8 16
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/InedoLib/Styles/icons2/white-settings.svg - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/InedoLib/Styles/icons2/white-settings.svg - 200 1810 image/svg+xml 0.4640ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/InedoLib/Styles/icons2/white-user.svg - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/InedoLib/Styles/icons2/white-user.svg - 200 873 image/svg+xml 0.3933ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/styles/icons2/blue-inprocess.svg - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/resources/InedoLib/styles/icons2/blue-inprocess.svg - 200 1143 image/svg+xml 0.4675ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/0x44/proget/Inedo.ProGet.WebApplication.Controls.Layout.NotificationBar/GetNotifications - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: System.Net.Http.HttpClient.Default.LogicalHandler[100]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Start processing HTTP request GET https://blog.inedo.com/rss.xml
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: System.Net.Http.HttpClient.Default.ClientHandler[100]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Sending HTTP request GET https://blog.inedo.com/rss.xml
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/0x44/proget/Inedo.ProGet.WebApplication.Controls.Layout.NotificationBar/GetNotifications - 200 30 - 14.2107ms
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/favicon.ico - - -
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:14 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/favicon.ico - 200 102182 image/x-icon 2.1118ms
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: System.Net.Http.HttpClient.Default.ClientHandler[101]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Received HTTP response headers after 232.8323ms - 200
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: System.Net.Http.HttpClient.Default.LogicalHandler[101]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       End processing HTTP request after 236.0294ms - 200
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 POST http://proget.graudatastorage.intern/ - 200 2924 text/html;+charset=UTF-8 269.8420ms
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/Icons/feed-chocolatey.svg - - -
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/Icons/feed-debian.svg - - -
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/Icons/feed-debian.svg - 200 6777 image/svg+xml 0.5647ms
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/Icons/feed-docker.svg - - -
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/Icons/feed-docker.svg - 200 5681 image/svg+xml 0.3956ms
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/Icons/feed-rpm.svg - - -
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/Icons/feed-rpm.svg - 200 3501 image/svg+xml 0.4399ms
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/Icons/feed-proget.svg - - -
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/Icons/feed-proget.svg - 200 2927 image/svg+xml 0.5359ms
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/Icons/feed-pypi.svg - - -
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/Icons/feed-pypi.svg - 200 2075 image/svg+xml 0.3556ms
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:15 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/Resources/Images/Icons/feed-chocolatey.svg - 200 2208 image/svg+xml 3.8633ms
Nov 11 07:24:19 gsg1repo.graudatastorage.intern systemd-proget[2188]: Running Drop Path Monitor...
Nov 11 07:24:19 gsg1repo.graudatastorage.intern systemd-proget[2188]: Getting list of feeds with a drop path...
Nov 11 07:24:19 gsg1repo.graudatastorage.intern systemd-proget[2188]: No feeds with a drop path.
Nov 11 07:24:19 gsg1repo.graudatastorage.intern systemd-proget[2188]: Drop Path Monitor completed.
Nov 11 07:24:23 gsg1repo.graudatastorage.intern systemd-proget[2188]: Running Execution Dispatcher...
Nov 11 07:24:23 gsg1repo.graudatastorage.intern systemd-proget[2188]: Checking for executions to dispatch...
Nov 11 07:24:23 gsg1repo.graudatastorage.intern systemd-proget[2188]: Execution Dispatcher completed.
Nov 11 07:24:24 gsg1repo.graudatastorage.intern systemd-proget[2188]: Running Connector Cache Check...
Nov 11 07:24:24 gsg1repo.graudatastorage.intern systemd-proget[2188]: Getting list of connector responses...
Nov 11 07:24:24 gsg1repo.graudatastorage.intern systemd-proget[2188]: Connector Cache Check completed.
Nov 11 07:24:24 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Nov 11 07:24:24 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request starting HTTP/1.1 GET http://proget.graudatastorage.intern/0x44/proget/Inedo.ProGet.WebApplication.Controls.Layout.NotificationBar/GetNotifications - - -
Nov 11 07:24:24 gsg1repo.graudatastorage.intern systemd-proget[2188]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Nov 11 07:24:24 gsg1repo.graudatastorage.intern systemd-proget[2188]:       Request finished HTTP/1.1 GET http://proget.graudatastorage.intern/0x44/proget/Inedo.ProGet.WebApplication.Controls.Layout.NotificationBar/GetNotifications - 200 30 - 7.1330ms

      Cheers
      -Fritz

      PS:
      Forgot to mention: If there were some output on stderr, that would be hilighted in red and there was nothing red, so: everything came from stdout)

      posted in Support
      felfertF
      felfert
    • Upgrade from 2025.13 to 2025.14 failed (Linux, PostGres)

      Hi,

      After upgrading, I get the following Message in the Proget HomePage:

      ProGet is running v25.0.14.12, but the SQL database being used is running schema v25.0.13.12. This may cause unpredictable errors; please reinstall ProGet or update the database schema manually to resolve this error. If you are unsure how to resolve this, contact Inedo Support.

      So: How do i do a "manual database schema update"? Looked in the "Database Overview", but the only thing there is the log of the initial DB Migration from MSSQL to Postgres.

      This is my Upgrade-Script, that I ran on the host (Rocky8, podman, quadlets):

      #!/bin/sh
set -e
systemctl stop proget
sleep 5
itag=latest
if [ $# -eq 1 ] ; then
    itag=$1
fi
docker tag proget:current proget:previous
docker pull proget.inedo.com/productimages/inedo/proget:${itag}
docker tag proget.inedo.com/productimages/inedo/proget:${itag} proget:current
systemctl start proget
cat<<EOF
Upgrade finished and proget started.
Old image has benn tagged proget:previous
EOF

      These are the images after running the above script:

      [root@gsg1repo ~]# podman images 
REPOSITORY                                   TAG          IMAGE ID      CREATED       SIZE
proget.inedo.com/productimages/inedo/proget  latest       1ba4ccf7722e  3 days ago    608 MB
localhost/proget                             current      1ba4ccf7722e  3 days ago    608 MB
localhost/proget                             previous     a8d218757759  2 weeks ago   611 MB
<none>                                       <none>       3cb6439872be  4 weeks ago   610 MB
<none>                                       <none>       24f2a48c7d66  6 weeks ago   636 MB
<none>                                       <none>       52ec80bdba76  8 weeks ago   637 MB
<none>                                       <none>       b4aa6e4a264a  2 months ago  613 MB
proget.inedo.com/productimages/inedo/proget  25.0.9-ci.7  0e34c14e3c4c  2 months ago  613 MB
proget.inedo.com/productimages/inedo/proget  25.0.9-ci.6  eb96ab45bf33  2 months ago  613 MB
proget.inedo.com/productimages/inedo/proget  25.0.8       4137d38c97aa  2 months ago  613 MB
proget.inedo.com/productimages/inedo/proget  25.0.8-ci.3  04aa2ed9b732  3 months ago  613 MB
<none>                                       <none>       71481b471565  3 months ago  613 MB
mcr.microsoft.com/mssql/server               2019-latest  5d4c91b68891  2 years ago   1.48 GB

      FYI: For now, I simply switched back to the previous image.

      Thanks in advance
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: Support for gpg in rpm feed

      @Sigve-opedal_6476

      Sorry for the intrusion in this thread.
      Could you probably share more info (ideally: write a little HOWTO)?
      I have exactly the same issue and wondered how to solve that.

      Thanks in Advance
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: ProGet bug - Regression: RPM feed repodata broken since 25.0.8

      @gdivis That was the missing information (wait 30sec AND fetch repodata) - it works as described.

      To summarize what lead me to incorrectly assume that it was not fixed:

      • My initial expectation was, it would be fixed by merely updating proget
      • After that did not show progress, I found the repodata files in the feed storage path having an old timestamp
      • Then I deleted and re-uploaded the latest rpm and noticed no timestamps change
      • I never tried to actually fetch repodata, because I saw the old timestamps

      Thanks again for your clarification
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: Machine ID changes after restart

      As a reference and perhaps an example for how to run proget as quadlets, here are my config files for quadlets:

      1. /etc/containers/systemd/mssql.container
      [Unit]
Description=Microsoft SQL server

[Service]
Restart=always
# Extend Timeout to allow time to pull the image
TimeoutStartSec=900

[Container]
Image=mcr.microsoft.com/mssql/server:2019-latest
EnvironmentFile=/etc/mssql.env
Volume=/var/data/mssql:/var/opt/mssql:U,Z
Network=inedo.network
HostName=inedo-sql

[Install]
WantedBy=multi-user.target
      1. /etc/containers/systemd/proget.container
      [Unit]
Description=Inedo proget
After=mssql.service
Requires=mssql.service

[Service]
Restart=always
# Extend Timeout to allow time to pull the image
TimeoutStartSec=900

[Container]
Image=localhost/proget:current
EnvironmentFile=/etc/proget.env
Volume=/var/data/proget/backups:/var/proget/backups:z
Volume=/var/data/proget/database:/var/proget/database:z
Volume=/var/data/proget/extensions:/var/proget/extensions:z
Volume=/var/data/proget/packages:/var/proget/packages:z
Volume=/var/data/proget/ssl:/var/proget/ssl:z
Volume=/etc/localtime:/etc/localtime:ro
Network=inedo.network
PublishPort=80:80
HostName=proget

[Install]
WantedBy=multi-user.target
      1. /etc/containers/systemd/inedo.network
      [Network]

      Remarks:

      The Image in /etc/containers/systemd/proget.container is intentionally referencing a locally tagged image. This goes together with the following script for easily updating
      proget:

      #!/bin/bash
set -e
set -x
systemctl stop proget
sleep 5
itag=latest
if [ $# -eq 1 ] ; then
    itag=$1
fi
podman tag proget:current proget:previous
podman pull proget.inedo.com/productimages/inedo/proget:${itag}
podman tag proget.inedo.com/productimages/inedo/proget:${itag} proget:current
systemctl start proget
cat<<EOF
Upgrade finished and proget started.
Old image has benn tagged proget:previous
EOF

      and: Obviously, the hierarchy below /var/data/proget has to be manually created in advance. /var/data/proget is on a separate virtual disk.

      Forgot the env files referenced in the .container files:

      /etc/mssql.env:

      ACCEPT_EULA=Y
MSSQL_SA_PASSWORD=*****REDACTED*****
MSSQL_PID=Express

      /etc/proget.env:

      PROGET_SQL_CONNECTION_STRING=Data Source=inedo-sql; Initial Catalog=ProGet; User ID=sa; Password=*****REDACTED*****
TZ=Europe/Berlin

      Both are mode 0600, so that the passwords in there are a little bit more protected.

      And: Just after freshly setting it all up, I normally immediately migrate to embedded postgres and then remove the mssql container as well as the inedo network.

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: Machine ID changes after restart

      @jorgen-nilsson_1299

      I am running the docker container on Rocky 9 and here, the license keeps valid.

      Since rocky and alma are very similar, this must either be some difference of
      podman or related to how you exactly start the container.

      So:
      How exactly do you start your container(s)? I use quadlets - the recommended way on RHEL.

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: ProGet bug - Regression: RPM feed repodata broken since 25.0.8

      Ok, while I was testing on the sandbox (without being able to reproduce the error), the repodata files on my "production" proget got regenerated and since that happened, everything is working again. So this just leaves the question:

      Out of curiosity:
      How does one force the regeneration of those repodata files?

      Obviously not one of these (tried those before)

      • Delete a package from the feed
      • Upload that package again.
      • Delete an older package from the feed (not uploading again)
      • Clicking on "re-index" in "Storage and Retention" of the feed

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: ProGet bug - Regression: RPM feed repodata broken since 25.0.8

      Hi, thanks for the response..

      @gdivis said in ProGet bug - Regression: RPM feed repodata broken since 25.0.8:

      One thing to note is that those repodata files in storage only get updated on-demand - so something would have to actually make a request for the index to get ProGet to rebuild it

      For clarification, can you elaborate a little bit on that? I mean either deleting or uploading a package would count as "something", or does the content of the repodata files get completely held in memory by proget even if some update happens?

      Anyway, I will setup a proget sandbox instance and see if I can reproduce it there. Will report back and/or open a ticket when I got more details.

      posted in Support
      felfertF
      felfert
    • RE: ProGet bug - Regression: RPM feed repodata broken since 25.0.8

      @gdivis, @stevedennis

      Just a humble reminder - PG-3094 did not fix the problem in 25.0.9 for me.

      Thanks
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: ERROR while migrating maven repository from Jfrog Artifactory.

      @wechselberg-nisboerge_3629 said in ERROR while migrating maven repository from Jfrog Artifactory.:

      I am especially confused about the fact that it prints Windows paths, even though it is running as Linux Docker container.

      That one fooled me previously as well, but if you look carefully, those are source paths from their build-system
      e.g. C:\Users\builds\AppData\Local\Temp\InedoAgent\BuildMaster\...

      posted in Support
      felfertF
      felfert
    • RE: proget - Enhancement request: show value of X-Forwarded-For header

      @atripp I did write this from memory and I don't recall where exactly I saw the IP logged. But I usually look only in two places:

      1. Diagnostic center
      2. Stdout/Stderr of the docker container which the podmad quadlets conveniently log into the host's system journal.

      Unfortunately the system journal has just been rotated (1st of September) and I keep old logs only for the last month so I looked into the August logs, but the error (something reladed to an old Debian feed) wasn't in there either. Must have happened before.

      Anyway, it would be very useful if you log either the remote-ip or (if exists) the X-Forwarded-For header value.

      Something like this (pseudo code based on C):
      printf("some error from %s", (xForwardedValue && strlen(xForwardedValue)) ? xForwardedValue : remoteIp);

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • RE: proget 500 Internal server error when pushing to a proget docker feed

      @atripp I tested this one and it works.

      However:
      In the meantime, i have updated to the released 25.0.9 (aka latest) and now I cannot reproduce the error either - even if I explicitely revert the function to the old one where it produced the error before 😕

      So I'm afraid that i might not be a reliable tester for this specific error anymore.

      Cheers
      -Fritz

      posted in Support
      felfertF
      felfert
    • 1
    • 2
    • 3
    • 1 / 3