-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Failed to load API definition (Internal Server Error) #4680
Comments
Hi! |
This is currently working on develop branch. |
Yes, this was fixed by #4733 |
Are issues getting closed once the fixes are released / in master? |
This should have been closed. They are usually closed when merged |
Just to let you guys know, this error is still happening on version 4.22.5. Failed to load API definition. |
yeah same thing .. |
Swagger Endpoint Conflict Issue Solution: To resolve the conflict, unique paths were assigned to the methods. For example, using HttpPost("Register"). This improved the API's functionality and clarified the Swagger documentation. Outcome: Assigning unique paths eliminated the conflict and made the API easier to use. |
Describe the bug
When I try to view the API documentation provided by Swagger, I get an internal server error.
To Reproduce
Steps to reproduce the behavior:
Alternatively, when I navigate directly 'http://ombi.ip:5000/swagger/v1/swagger.json', I get the following JSON error:
{"error":"Failed to generate schema for type - Ombi.Models.External.PlexLibrariesResponse. See inner exception"}
Expected behavior
I expect to see the API documentation when I navigate to the aforementioned URL.
Screenshots

Logs (Logs directory where Ombi is located)
Desktop (please complete the following information):
Ombi Version (please complete the following information):
The text was updated successfully, but these errors were encountered: