microsoft / microsoft/aspire

No error message on proxy failure (e.g. because of Windows excluded port ranges)

Open
#20,066 3 comments 0 reactions 1 assignee Claimed by @danegsta View on GitHub
area-orchestrator needs-area-label triage:bot-seen
Dominant language
C#
Stars
6.3k
Forks
991
Avg merge
2d 15h
Merged PRs (30d)
196

Description

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

I have the same situation as https://github.com/microsoft/aspire/issues/9634
The issue was closed with a claim that the error message is logged somewhere, but I cannot see any error:
* The Dashboard shows that the service is running, even though the proxy wasn't started.
* The AppHost logs doesn't show any warning or error - there are just the typical info messages and everything seems OK.
* I cannot find any other place where I could see any information that the proxy cannot start because the port is occupied or is in excluded port ranges.

### Expected Behavior

I would expect to see some warning either in AppHost logs or in the Aspire dashboard.

### Steps To Reproduce

1. Use any template with a single web app.
2. Run `netsh interface ipv4 show excludedportrange protocol=tcp` to list the excluded port ranges.
3. Pick any port from that range and use it in `launchSettings.json`:
```
{
"profiles": {
"https": {
"commandName": "Project",
"launchBrowser": true,
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development"
},
"applicationUrl": "https://localhost:50500"
}
}
}
```

### Exceptions (if any)

_No response_

### Aspire doctor output

```plain

```

### Anything else?

* .NET 10.0
* Aspire 13.5.3
* Windows 11 (latest updates installed)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.