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 2022.6: The hostname could not be parsed



  • After Upgrading from version 5.3.27 to Proget 2022.6 I noticed that in Event Viewer on our Proget Server I am seeing this error output with the source being .NET Runtime

    Category: Microsoft.AspNetCore.Server.IIS.Core.IISHttpServer
    EventId: 2
    SpanId: d6542f2f0ddee4b5
    TraceId: 5209a8d0edc029b1608257cd9b0a499f
    ParentId: 0000000000000011
    RequestId: 8000009a-0000-fa00-b65f-84610c7967bb
    RequestPath: /
    
    Connection ID "18014398511084596889", Request ID "8000009a-0000-fa00-b65f-84610c7967bb": An unhandled exception was thrown by the application.
    
    Exception: 
    System.UriFormatException: Invalid URI: The hostname could not be parsed.
       at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind, UriCreationOptions& creationOptions)
       at System.Uri..ctor(String uriString)
       at System.Web.HttpRequest.<.ctor>b__6_0()
       at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)
    --- End of stack trace from previous location ---
       at System.Lazy`1.CreateValue()
       at Inedo.ProGet.WebApplication.ProGetHttpModule.LogHttpException(MessageLevel level, HttpApplication app, Exception ex)
       at Inedo.ProGet.WebApplication.ProGetHttpModule.ErrorAsync(HttpApplication app)
       at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
       at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
       at Inedo.Web.AhWebHost.<>c.<<Configure>b__13_0>d.MoveNext()
    --- End of stack trace from previous location ---
       at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContextOfT`1.ProcessRequestAsync()
    
    

    As an attempt to fix I installed .NET 6 on the server but still seeing error. Our Proget Server is on Windows Server 2012 so Not sure if this is causing an issue or not?
    Our proget site is still up and running so wondering what exactly is causing this issue?

    Thanks


  • inedo-engineer

    Hi @tcochran_0018,

    This looks to be related to a known bug, PG-2193, that is expected to be released this week in version 2022.7. These errors shouldn't affect the operation of anything, but please let us know if it does.

    Thanks,
    Dan



  • @Dan_Woolf Sounds good, thanks for the response.



Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation