---
title: "Discussion on \"Upgrading to .NET 8\" | Hashnode"
description: "Discussion on \"Upgrading to .NET 8\". dotnet 8 upstream connect error or disconnect/reset before headers .net 8"
url: "https://hashnode.com/posts/upgrading-to-net-8/65556d8d53d370b35005dc87"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Upgrading to .NET 8](https://bogdanbujdea.dev/upgrading-to-net-8?utm_source=hashnode&utm_medium=feed)

dotnet 8 upstream connect error or disconnect/reset before headers .net 8

Nov 16, 2023 · 1 min read · bogdanbujdea.dev  
Read the article

-   [#net](https://hashnode.com/tag/net)
-   [#dotnet8](https://hashnode.com/tag/dotnet8)
-   [#dotnet](https://hashnode.com/tag/dotnet)
-   [#programming](https://hashnode.com/tag/programming)

## Written by

[Bogdan Bujdea](https://hashnode.com/@bogdan)

@bogdan · Iasi, Romania

  
[View profile](https://hashnode.com/@bogdan)

.NET Developer

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.

## Responses 2

Markdown supported · ⌘↵ to post

[Bart Coppens](https://hashnode.com/@xhle)

[Jan 9, 2024](https://hashnode.com/posts/upgrading-to-net-8/65556d8d53d370b35005dc87/comment/659ca3c9b80581bc195bd21f)

Hi again [Bogdan Bujdea](https://hashnode.com/@bogdan). Have you made any progress on this? I've noticed that a standard ACA deployment will fail if no startup/liveness probes are defined since the default ([learn.microsoft.com/en-us/azure/container-apps/he…](https://learn.microsoft.com/en-us/azure/container-apps/health-probes?tabs=arm-template#default-configuration)) startup probe uses port 80. Explicitly configuring probes with port 8080 resolves this. However, I'm still running into the same issue you reported when using HTTPS port 443 to access the API deployed on ACA.

[Bart Coppens](https://hashnode.com/@xhle)

[Dec 5, 2023](https://hashnode.com/posts/upgrading-to-net-8/65556d8d53d370b35005dc87/comment/656f0cdeae37c1e95a374139)

Hi Bogdan. I ran into the same issue. Have you found a way to resolve this? I tried adding the ASPNETCORE\_HTTP\_PORTS, but it doesn't resolve the issue.