Upgrading to .NET 8

Bogdan BujdeaBogdan Bujdea
1 min read

I am currently working on several projects, and I plan to migrate all of them to .NET 8. That's why I thought it would be helpful to write an article detailing the various challenges I encountered during this process.

  1. Port 80 is no longer the default

This project is an ASP.NET Web API on .NET 7 and it's really fresh, a few days old, but I still had issues upgrading to .NET 8. When I deployed the project to Azure Container Apps I got this error:

upstream connect error or disconnect/reset before headers. retried and the latest reset reason: remote connection failure, transport failure reason: delayed connect error: 111

After ~30 minutes I figured out that .NET 8 is listening on port 8080 instead of 80, and when I googled this I immediately found out that this is a breaking change. Here's the link with more details:

https://learn.microsoft.com/en-us/dotnet/core/compatibility/containers/8.0/aspnet-port

I'll update this blog post when I have more stuff.

0
Subscribe to my newsletter

Read articles from Bogdan Bujdea directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Bogdan Bujdea
Bogdan Bujdea

Expert generalist • Independent Contractor • Microsoft MVP • Home Assistant enthusiast Hi there! I'm Bogdan Bujdea, a software developer from Romania. I'm currently a .NET independent contractor, and in my free time I get involved in the local .NET community or I'm co-organizing the @dotnetdays conference. I consider myself an expert generalist, mostly because I enjoy trying out new stuff whenever I get the chance and I get bored pretty easily, so on this blog you'll see me posting content from programming tutorials to playing with my smart gadgets.