Support
Cannot connect to service from mongo shell
I have installed mongosh-1.5.1-win32-x64
When trying to connect to my service from mongosh shell, i'm getting the error
MongoServerSelectionError: connect ETIMEDOUT 52.155.36.122:27017
Posted by Parmeet over 1 year ago
Can't create service
I got error in creating a new service. Even delete it and create again and found no luck. Please help and thanks.
Posted by Sunny So over 1 year ago
DragonGlass Transaction Links in Proof Certificate not working
I can see transaction links (via dragonglass) on the proof certificate do not show any results on dragonglass. Am i missing something? The transaction id is however searchable on other explorers.
Posted by GB almost 2 years ago
submitProof command not working sometimes
tried using both collection level and database level proofs but same thing happen. Also purchased the developer plan but no luck. Here is the service(for a document level proof) & the error:
dbObject.command(
{
submitProof: currentVersion,
collections: ["provenDiamonds"],
filter: newDocument, },
(error, res) => {
if (error) {
console.error(error);
reject("Could not submitproof for version.");
} else {
console.log(res);
resolve("New proof created.", res);
}
}
);
ERROR =>
MongoServerError: UNAVAILABLE: io exception
at MessageStream.messageHandler (F:\Builds\test\node_modules\mongodb\lib\cmap\connection.js:467:30)
at MessageStream.emit (events.js:315:20)
at processIncomingData (F:\Builds\test\node_modules\mongodb\lib\cmap\message_stream.js:108:16)
at MessageStream._write (F:\Builds\test\node_modules\mongodb\lib\cmap\message_stream.js:28:9)
at writeOrBuffer (internal/streams/writable.js:358:12)
at MessageStream.Writable.write (internal/streams/writable.js:303:10)
at TLSSocket.ondata (internal/streams/readable.js:719:22)
at TLSSocket.emit (events.js:315:20)
at addChunk (internal/streams/readable.js:309:12)
at readableAddChunk (internal/streams/readable.js:284:9) {
ok: 0,
code: 125,
codeName: 'CommandFailed'
}
the thing is those documents stored in the database without a proof and the request not get resolved or rejected either. Here I attached the output when I try to get the proof of such documents using getDocumentProof.
{
"collection": "provenDiamonds",
"version": 25,
"documentId": "61de71ac00c5985c343f70e3",
"errmsg": "There is no proof for this version of the document"
}
Posted by Himasha Weerasinghe almost 2 years ago
MongoDB Atlas: Username already exists.
MongoDB Atlas: 409 A user with username "Test" already exists.
{
"message": "MongoDB Atlas: 409 A user with username "Test" already exists.",
"code": "ATLAS_USER_ALREADY_EXISTS",
"deletable": false,
"humanInterventionNeeded": true
}
How to fix this issue?
Delete functionality not available!
Posted by Bhavin Kareliya about 2 years ago
error occur when connecting with MongoDB Compass
BSON field 'OperationSessionInfo.$clusterTime' is a duplicate field
Posted by Mahesh about 2 years ago
I get this error everytime I try to create a new service.
{"message":"(Location51002) Role \"superadmin@elderlyhealthappdb\" already exists","code":"UNKNOWN","deletable":false,"humanInterventionNeeded":true}
All the time I get this error when I am trying to create a new service
Posted by Archi over 2 years ago
Update billing not working
Update billing not working
Posted by Baptiste HEDIARD over 2 years ago
How can I access my billing details?
I can't find in my dashboard where can i set my billing and credit card information, can you guide me please?
Posted by Fer Martin over 2 years ago
Add comment button was not working
Hi, sorry for writing here but the add comment button was not working on my previous post. This is the answer to this post: https://provendb.readme.io/discuss/601dd3a16d2388007def3f93
Yes, you are right, I meant submitProof.
So I created now again two documents in the database "xf1" in the collection "col_uploadedFiles" with the ids:
601e5125cf2db37b71deff4a, 601e5125cf2db37b71deff4b
Then I submit this command:
"{submitProof:45, collections:'col_uploadedFiles', filter: {_id: ObjectId('601e5125cf2db37b71deff4b')}, anchorType: 'ETH_MAINNET'}"
Now just 601e5125cf2db37b71deff4b should be verified by the blockchain.
But when I fo a getProof for 601e5125cf2db37b71deff4a,
I get this response:
"{ \"ok\" : 1, \"proofs\" : [{ \"collection\" : \"col_uploadedFiles\", \"scope\" : \"collection\", \"version\" : 45, \"documentId\" : { \"$oid\" : \"601e5125cf2db37b71deff4a\" }, \"versionProofId\" : \"9b4ce6f3-9955-4076-86ba-4763ef71b07f\", \"status\" : \"Pending\", \"documentHash\" : \"38a6d2b0bf681e43fb0186901a009955854a3af02c680223e3333a48cea9c80b\", \"versionHash\" : \"a3a27437f28b3c47a0c574f45d02dbc84cc1670c74c8ddedb7cca07e67c35d4b\", \"errmsg\" : \"The proof is not yet valid\" }] }"
It would be nice if you can check.
Posted by Sascha almost 3 years ago