Received an unexpected EOF or 0 bytes from the transport stream
- Dominant language
- C#
- Stars
- 38.4k
- Forks
- 10.9k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 281
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Describe the bug
I have a web api project .NET 8. All the sudden when i try to debug it in visual studio 2026, the service does not listen on port. All i have is exception in SslStream.
```
System.IO.IOException
HResult=0x80131620
Message=Received an unexpected EOF or 0 bytes from the transport stream.
Source=System.Net.Security
StackTrace:
at System.Net.Security.SslStream.d__151`1.MoveNext() in System.Net.Security\SslStream.cs:line 1484
```
Other coworkers can normally run and debug same project.
I also have installed dotnet 10 in parallel.
### Expected Behavior
Run project in VS
### Steps To Reproduce
Only on my machine.
### Exceptions (if any)
System.IO.IOException
HResult=0x80131620
Message=Received an unexpected EOF or 0 bytes from the transport stream.
Source=System.Net.Security
StackTrace:
at System.Net.Security.SslStream.d__151`1.MoveNext() in System.Net.Security\SslStream.cs:line 1484
### .NET Version
8.0.407
### Anything else?
_No response_
Contributor guide
Research direction
Start by examining System.Net.Security\SslStream.cs at line 1484 and reproduce the failure with the reported .NET 8.0.407 web API under Visual Studio 2026. Compare the behavior with the separately installed .NET 10 environment and gather enough machine-specific details to identify why the TLS handshake ends at EOF. Done means a reproducible cause and a confirmed resolution or clear evidence that the problem is environmental.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100