-
Notifications
You must be signed in to change notification settings - Fork 29
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
Unable to Create Public Share Link #610
Comments
Example of VerifierPlus link created from LCW that serves a 404: https://verifierplus.org/credentials/4d0e729f-460b-49bc-a93b-1136ca433509 This credentials data (verifies fine when uploaded directly to VerifierPlus): { |
This issue appears to be related to a connections max that we are hitting with mongodb atlas. But we shouldn't be hitting the max connections because the connections should only occur when the server using it starts. I believe we only have VerifierPlus and Demo Issuer using this service so there could be connections when we don't need them that are left open. |
Dmitri says: # connections can grow with refresh and is currently refactoring - WIP - looking into node |
Temp fix by restarting V+, but permanent fix is in: digitalcredentials/web-verifier-plus#127. Closing this issue to continue addressing digitalcredentials/web-verifier-plus#127 |
Describe the bug
When clicking on "Create Public Link" on the share, page, getting error popup: "Unable to create Public Link" AN error occurred while creating the Public Link for this credential". Clicking on details reveals this error: Error: Failed to post credential to Verifier Plus.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should be able to create a public link that is saved in the VerifierPlus MongoDB
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Additional context
Only tested on iphone. Possibly related: previously created links are serving 404. No issue for this yet.
The text was updated successfully, but these errors were encountered: