search

perma-id / w3id.org

Website source code for w3id.org.
https://w3id.org/
279 stars 1.19k forks source link

Service Unavailable https://www.w3.org/2018/credentials/v1 #2197

Open Vishwas1 opened 3 years ago

Vishwas1 commented 3 years ago

Hi guys, we are testing verifiable credentials with more than 500 users. So far 300+ users have been able to get did and verifiable credential from our server. This test is basically to prove SSI systems can be used to productions and is stable. We started this test on Saturday and planned to continue till this weekend. The use case which we picked up is authentication and authorization. where a user receives did and vc from our server and uses those to authenticate to the service provider. But today we started to see a problem with issuing credentials, jsonld.InvalidUrl: Dereferencing a URL did not result in a valid JSON-LD object. After debugging we found that https://www.w3.org/2018/credentials/v1 this url which was previously working, is not accessible any more. Our users are stucked at this point and we are struggling to fix this issue. If any one here has any suggestion or solutions, kindly help. Or if you can just forward this message to right people, will also be helpful. Thank You!

TallTed commented 3 years ago

Are you using proper caching? You should not need to retrieve that static resource for every VC. You did not provide the error you were hitting, so it's not possible to tell whether you were throttled out (i.e., the server may not like being hit too quickly, or too many times in a day, etc.) or ran into some other issue.

Certainly, that URI is working fine right now --

$ curl -LI https://www.w3.org/2018/credentials/v1
HTTP/1.1 200 OK
date: Wed, 02 Jun 2021 15:38:46 GMT
content-length: 7687
content-type: application/ld+json
...
TallTed commented 3 years ago

Also note -- w3id.org is not affiliated with w3.org, so this isn't the right place to raise your issue.

davidlehn commented 3 years ago

Agree about caching and this is not a w3id.org issue. Note that w3.org was using an expired cert yesterday for a little while, maybe around the time you filed this, and that may have caused certificate validation errors to happen that would cause an error like above. There may have been an error cause chain that would make that low level issue more obvious. I imagine it's working now but in general remember that networks and servers can have downtime and you need to have error handling in place to handle such situations.

For help with caching, I'd suggest the credentials community, JSON-LD community, or library maintainers. If you'd like better error messages, raise an issue with the library maintainers. I'm guessing based on that error message you are using jsonld.js or pyld, so that probably involves me, but better to discuss in another forum.