After upgrading to 2026 https no longer works

Valentijn

Hi,

I upgraded from 2025.27 to 2026 but was no longer able to access proget through https

Our internal address: https://packages.vicrea.nl/
The local http address still worked: http://localhost:8624/

I reverted back to 2025.27 and that works again.

Could not find much more info then this in the event viewer

Category: Microsoft.AspNetCore.Server.Kestrel
EventId: 0

Overriding address(es) 'http://*:8624, https://packages.vicrea.nl:443'. Binding to endpoints defined via IConfiguration and/or UseKestrel() instead.

Kind regards,

Valentijn

atripp

Hi @Valentijn ,

This looks like some consequence of a platform change (we went from .NET8 to .NET10), but it's hard to say.... I wonder if there's some kind of issue with the mixed bindings (i.e. using port sharing for https, but not for http).

What does your <WebServer> node look like in your configuration file?
https://docs.inedo.com/docs/installation/configuration-files

Can you try it without port sharing? So basically just http://*:8624, https://*:443

Thanks,
Alana

Valentijn

I tried http://:8624, https://:443 before upgrading but that does not work and gives the same event viewer warning:

Overriding address(es) 'http://:8624, https://:443'. Binding to endpoints defined via IConfiguration and/or UseKestrel() instead.

atripp

Hi @Valentijn ,

I just checked and that's an expected message.

Can you stop the ProGet service, then navigate to a commandline and run proget.exe run?

That will give detailed console output; in there you may see some messages about HTTP bindings, such as this:

The URL was configured to use HTTPS, but a certificate was not specified.
info: Inedo.Web.BackgroundTaskQueueService[0]
      Background Task Queue is starting.
warn: Microsoft.AspNetCore.Server.Kestrel[0]
      Overriding address(es) 'http://*:8624, https://*:8625'. Binding to endpoints defined via IConfiguration and/or UseKestrel() instead.
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://[::]:8624
info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://[::]:8625

Hopefully that will give us a clue.

Thanks,
Alana

Valentijn

Hi,

I was on a short vacation but today I upgraded to 2026.3 (build 14) without any problems.

This probably fixed it:
PG-3299 2026.3 FIX: Hostname based binding fails when hosting on Windows with HTTP.SYS

Kind regards,

Valentijn