Live demo link is broken about swapi-graphql

[acao]

@RussianCow some folks from the GraphQL Foundation are looking into the https://graphql.org/swapi-graphql/ URL issue itself, I'll keep you posted and close this once it's resolved

[orta]

I'm also getting the same error - looks like maybe a netlify 404 page?

[benjie]

I am also getting the error on my phone which I believe has not visited that page before. If it’s an ISP DNS cache issue I may have to wait 48 hours for it to resolve.

[idanlo]

Any updates?

[acao]

thanks @RussianCow . I'll try to track it down

[acao]

@RussianCow I was able to get it working after a redeploy, but only at the gh-pages domain:
https://graphql.github.io/swapi-graphql/

I'm not sure who controls the DNS or CDN config for graphql.org currently, as http://graphql.org/swapi-graphql/ still appears to be down, but I'll raise the issue, thanks for pointing it out!

[RussianCow]

Great, thanks for spinning that up so quickly!

[acao]

@RussianCow can you confirm that https://graphql.org/swapi-graphql/ works for you now?

[RussianCow]

No, I still get the same "Page Not Found" error.

[acao]

@RussianCow I think it might be your DNS cache as well, because some folks who didnt originally see this error . Have you tried visiting on, say, a smart phone or another device before, that's not connected to the same router?

[RussianCow]

I just tried on my phone with wifi off and got the same error. :/

[benjie]

Nope, connecting over 4G rather than wifi has same issue.

[acao]

I think Facebook is using Netlifly for managing DNS, and theres just a missing or broken DNS entry for swapi-graphql since dig doesn't show any A records for it

[acao]

The FB folks were saying it looked fine at first when I reported this, but they confirmed it isn't working for them on external networks, so I think its close to what you are suggesting @benjie but essentially the opposite, where facebook's ISP DNS cache is giving them a false positive and it's definately down

[acao]

We are still looking into it, very actively. In the meanwhile the github.io link above is working!

[idanlo]

@acao there is a CORS and err: BLOCKED BY CLIENT issue trying to access the github.io link for some reason

[acao]

@idanlo this one? https://graphql.github.io/swapi-graphql/

[acao]

@idanlo I have very limited access to anything, I don't have access to DNS or settings for any of the github repositories. Only write access to graphiql :( So its been very difficult trying to solve this issue.

[idanlo]

@acao yes

[acao]

given the nature of the error, it must be that your browser itself is blocking it. potentially an issue with browser plugins? do you have any more verbose console output? this might be a different bug entirely.

[idanlo]

@acao after cancelling my adblocker the err: BLOCKED BY CLIENT changed to a CORS error

[acao]

huh! i have UBlockOrigin, privacy badger, https everywhere etc in firefox and it seems fine. Are you using Chrome or another browser?

[idanlo]

Chrome

[acao]

@idanlo alas, i cannot reproduce, nor other maintainers at the moment. Would you care to create a seperate issue for this repository?

[acao]

This will be a temporary fix until we can track down the issue at the GraphQL Foundation level:
graphql/graphql.github.io#714

[acao]

thanks everyone for helping us to track this down. just another hiccup in the tranfer of ownership, still transitioning access/etc. If I had the access I needed I would have fixed this a while ago

[acao]

@idanlo do you still see the issue?

[idanlo]

yes.
before disabling adblock:
OPTIONS https://graphql.github.io/swapi-graphql/ net::ERR_BLOCKED_BY_CLIENT
after disabling adblock:
Access to fetch at 'https://graphql.github.io/swapi-graphql/' from origin '______' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled

[acao]

@idanlo please create a new issue then, as this is unrelated. the CORS headers are not set by this project, but by github.io itself. this gh pages site (as with all gh-pages sites) is entirely client side.

[acao]

@RussianCow this should be fixed as of ~1hr ago, are you able to confirm?

[acao]

the issue was, in the transition of graphql.org to netlify from gh-pages, we had left a few things like this hanging that just transparently resolved before because of github.io paths. It ended up in the ISP DNS cache for a few organizations, so it was hard to track down at first. thanks to everyone who helped solve this issue!

[RussianCow]

Yep, works for me! Thanks so much for looking into this!

[acao]

@RussianCow no problem! was a good opportunity to pick up a few loose ends from the transition to netlify. sorry for any issues it might have caused. again, thanks for helping us to track this down everyone. @idanlo don't forget to make that issue so we can try and reproduce your issue