Skip to content
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

did:ethr driver error:500 Internal Server Error #414

Open
caict-develop-zhangbo opened this issue Apr 16, 2024 · 3 comments
Open

did:ethr driver error:500 Internal Server Error #414

caict-develop-zhangbo opened this issue Apr 16, 2024 · 3 comments

Comments

@caict-develop-zhangbo
Copy link
Contributor

caict-develop-zhangbo commented Apr 16, 2024

've recently deployed the DID Universal Resolver locally and encountered an error when trying to resolve did:ethr. The error message received is as follows:

{"@context":"https://w3id.org/did-resolution/v1","didDocument":null,"didResolutionMetadata":{"error":"internalError","errorMessage":"Driver cannot retrieve result for did:ethr:0x03fdd57adec3d438ea237fe46b33ee1e016eda6b585c3e27ea66686c2ea5358479: 500 Internal Server Error ()","contentType":"application/did+ld+json"},"didDocumentMetadata":{}}

I'm reaching out to inquire if anyone has insights into the possible reasons behind this error. Any assistance or guidance would be greatly appreciated.

@caict-develop-zhangbo caict-develop-zhangbo changed the title did:ether driver error:500 Internal Server Error did:ethr driver error:500 Internal Server Error Apr 16, 2024
@peacekeeper
Copy link
Member

Hello @caict-develop-zhangbo thanks for reporting this, but when I try it, it seems to work fine:
https://dev.uniresolver.io/#did:ethr:0x03fdd57adec3d438ea237fe46b33ee1e016eda6b585c3e27ea66686c2ea5358479

Could you try again and let us know if it still fails?

@caict-develop-zhangbo
Copy link
Contributor Author

Yes, the problem still exists. The scenario to reproduce it is when I deploy a universal-resolver locally and resolve did:ethr:0x03fdd57adec3d438ea237fe46b33ee1e016eda6b585c3e27ea66686c2ea5358479. It works fine when I directly call https://dev.uniresolver.io/#did:ethr:0x03fdd57adec3d438ea237fe46b33ee1e016eda6b585c3e27ea66686c2ea5358479, but it doesn't work with my local deployment, and I don't know where the problem lies."

@peacekeeper
Copy link
Member

I just tried it, and I can't reproduce this, for me it's working fine.

The Universal Resolver uses this driver for did:ethr:
https://github.com/uport-project/uport-did-driver

See configuration here:

Can you maybe check if the uport/uni-resolver-driver-did-uport:5.0.0 container is running locally, and what logs it shows? And any logs from the universalresolver/uni-resolver-web:latest container?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants