swagger-api / swagger-api/validator-badge
Can't read from file
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 227
- Forks
- 81
- Avg merge
- 2h 3m
- Merged PRs (30d)
- 1
Description
I get the following error on https://validator.swagger.io/validator/debug?url=https%3A%2F%2Fwww.openarchieven.nl%2Fapi%2Fopenapi.json
{
schemaValidationMessages: [
{
level: "error",
message: "Can't read from file https://www.openarchieven.nl/api/openapi.json"
}
]
}
The https://www.openarchieven.nl/api/openapi.json is accessible, but I suspect the swagger-api backend is blocked on the firewall to fend of AI robots. Are the IP-adresses of the swagger-api backend documented somewhere?
Are the two frontend IP adresses the same as the backend servers?
$ nslookup validator.swagger.io
Name: prod-swagger-oss-public-iac-616114540.us-east-1.elb.amazonaws.com
Address: 54.242.75.89
Name: prod-swagger-oss-public-iac-616114540.us-east-1.elb.amazonaws.com
Address: 100.49.133.160
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
Start with the validator.swagger.io/debug URL and the validator.swagger.io DNS records shown in the issue, then check the validator service's deployment or network documentation. Confirm whether the listed frontend addresses are also used by backend requests and document the supported addresses, or explain why they cannot be fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi
- Domain
- documentation, infrastructure, networking
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100