swagger-api / swagger-api/swagger-ui
Swagger UI is not working
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
I am not able to open Swagger and getting this below error. If someone has anyidea about this error then please post
C:\Users\adm-e3029233>curl -vv localhost:8080/swagger/ui/index
- Trying 127.0.0.1:8080...
- Connected to localhost (127.0.0.1) port 8080 (#0)
GET /swagger/ui/index HTTP/1.1
Host: localhost:8080
User-Agent: curl/7.83.1
Accept: /
- Mark bundle as not supporting multiuse
< HTTP/1.1 500 Internal Server Error
< Cache-Control: no-cache
< Pragma: no-cache
< Content-Type: application/json; charset=utf-8
< Expires: -1
< Server: Microsoft-IIS/10.0
< X-AspNet-Version: 4.0.30319
< Date: Thu, 19 Jan 2023 19:32:56 GMT
< Content-Length: 212
<
{"uuId":"","userId":0,"Emulated":false,"msgLst":[{"incidenceNumber":"FA.2301191432562","key":"UNKNOWN_ERROR_EXCEPTION","code":"E.SYS.999.01","text":"An unhandled exception occurred.","type":"InternalException"}]}* Connection #0 to host localhost left intact
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are identified. Start by reproducing the request to localhost:8080/swagger/ui/index and inspect whether the 500 response originates in Swagger UI or the user's host application; done requires a repository-specific cause and an actionable fix or confirmed external configuration issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100