[GH-ISSUE #4585] [bug]: OpenAPI import fails with error "format not recognized" #1691

Open
opened 2026-03-16 21:26:03 +03:00 by kerem · 6 comments
Owner

Originally created by @schanjan on GitHub (Dec 3, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4585

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

When I try to import an OpenAPI specification JSON, I get the following error:
image
The file is about 2MB in size. The import of the same works fine on Postman:
image
I don't have any details on why it is failing on Hoppscotch as the only thing I have is the error message above. No logs in the console as well.
OpenAPI version: 3.0.2

Steps to reproduce

Import the OpenAPI JSON file via file upload as proposed in the wizard.

I am not able to share the OpenAPI publicly here, but would definitely offer it for recreation purpose. Please contact me in that case.

Environment

Production

Version

Cloud

Originally created by @schanjan on GitHub (Dec 3, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4585 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When I try to import an OpenAPI specification JSON, I get the following error: ![image](https://github.com/user-attachments/assets/21eebbbe-d66c-40e0-8795-ba6b90464ecf) The file is about 2MB in size. The import of the same works fine on Postman: ![image](https://github.com/user-attachments/assets/613d208e-cd3b-44e0-b145-1b826e7af56b) I don't have any details on why it is failing on Hoppscotch as the only thing I have is the error message above. No logs in the console as well. OpenAPI version: 3.0.2 ### Steps to reproduce Import the OpenAPI JSON file via file upload as proposed in the wizard. I am not able to share the OpenAPI publicly here, but would definitely offer it for recreation purpose. Please contact me in that case. ### Environment Production ### Version Cloud
Author
Owner

@amk-dev commented on GitHub (Dec 3, 2024):

@schanjan do you have a sample spec that can reproduce this issue ?

<!-- gh-comment-id:2514013327 --> @amk-dev commented on GitHub (Dec 3, 2024): @schanjan do you have a sample spec that can reproduce this issue ?
Author
Owner

@schanjan commented on GitHub (Dec 3, 2024):

Please find the somewhat anonymized OpenAPI attached.
metadata.openapi3.json

<!-- gh-comment-id:2514221143 --> @schanjan commented on GitHub (Dec 3, 2024): Please find the somewhat anonymized OpenAPI attached. [metadata.openapi3.json](https://github.com/user-attachments/files/17991697/metadata.openapi3.json)
Author
Owner

@amk-dev commented on GitHub (Dec 4, 2024):

@schanjan thank you! looking in to this. will keep you posted

<!-- gh-comment-id:2518496076 --> @amk-dev commented on GitHub (Dec 4, 2024): @schanjan thank you! looking in to this. will keep you posted
Author
Owner

@anwarulislam commented on GitHub (May 18, 2025):

Hi @schanjan,
I attempted to import the JSON, and it's working perfectly! Could you please confirm?

<!-- gh-comment-id:2889022756 --> @anwarulislam commented on GitHub (May 18, 2025): Hi @schanjan, I attempted to import the JSON, and it's working perfectly! Could you please confirm?
Author
Owner

@schanjan commented on GitHub (May 20, 2025):

Hi @anwarulislam
I was able to import the json successfully in a private window / new hoppscotch account.
However, in my existing account, I still receive the above mentioned error.
Not sure you want to follow this, I am working with individually copying the requests I need. It is not of such high priority.

<!-- gh-comment-id:2895459046 --> @schanjan commented on GitHub (May 20, 2025): Hi @anwarulislam I was able to import the json successfully in a private window / new hoppscotch account. However, in my existing account, I still receive the above mentioned error. Not sure you want to follow this, I am working with individually copying the requests I need. It is not of such high priority.
Author
Owner

@MSP-Stev commented on GitHub (Jun 20, 2025):

For self-hosted user

I had the same issue with AIO installation + reverse proxy (nginx)

Console showed:

backend/graphql net::ERR_FAILED 413 (Request Entity Too Large)" ERR_FAILED 413 (Request Entity Too Large)

Fix:
Increase client max body size and reload/restart nginx

client_max_body_size 10M;
<!-- gh-comment-id:2990420487 --> @MSP-Stev commented on GitHub (Jun 20, 2025): **For self-hosted user** I had the same issue with AIO installation + reverse proxy (nginx) Console showed: ``` backend/graphql net::ERR_FAILED 413 (Request Entity Too Large)" ERR_FAILED 413 (Request Entity Too Large) ``` Fix: Increase client max body size and reload/restart nginx ``` client_max_body_size 10M; ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#1691
No description provided.