Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After the ASP.NET Core 5.0 WebApi project is published, the interface document cannot be displayed or requested on the page after being launched by the command line #27798

Closed
Dylan-Jinx opened this issue Nov 13, 2020 · 2 comments
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update.

Comments

@Dylan-Jinx
Copy link

#19570 # Describe the bug
The ASP.NET Core 5.0 WebAPI project that we wrote was ready to be launched in VS and used postman's request interface and see the interface document,but, when I release the release, launch it with the following command --"dotnet IAIOT_alpha_api_0_5.dll --urls="http://*:80" --ip 127.0.0.1 --port 80",When it started, the command line sent out a message indicating which port it was bound to, though I couldn't reach the page using a browser, and postman couldn't ask for the interface

Further technical details

-The version is :.ASP.NET Core 5.0

  • The IDE is VisualStudio 2019 and version is 16.8.1
@jkotalik
Copy link
Contributor

I think we need more info here. Are you running that command on commandline? Were you able to bind to another port besides 80?

Logs and a reproducable sample would help speed up this investigation as well.

@jkotalik jkotalik added the Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. label Nov 13, 2020
@Dylan-Jinx
Copy link
Author

I can bind to ports other than 80 and the console log output also has no exceptions or error messages.My first guess is that something went wrong when I was building the project.Can give me some advice on generating options

@ghost ghost added Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. and removed Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. labels Nov 14, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 14, 2020
@amcasey amcasey added area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions and removed area-runtime labels Aug 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update.
Projects
None yet
Development

No branches or pull requests

4 participants