Welcome to the ProvenDB developer hub. You'll find comprehensive guides and documentation to help you start working with readme-test as quickly as possible, as well as support if you get stuck. Let's jump right in!
When I try to connect I have this error: connecting to: mongodb://34.94.247.74/rjurado-test-db 2019-10-28T11:25:28.669+0100 E QUERY [js] Error: couldn't connect to server 34.94.247.74:27017, connection attempt failed: SocketException: sslv3 alert unexpected message : [email protected]/mongo/shell/mongo.js:257:13 @(connect):1:6 exception: connect failed
Posted by rjurado_nss about a year ago
Hey, Just trying to connect to the mongodb instance using the standard mongo-driver package in go, however I am unable to establish a connection this way. I can log in perfectly fine using the latest version of the MongoDB shell on Windows. My code for connecting is this: ~~~~ package main import ( "context" "log" "go.mongodb.org/mongo-driver/mongo" "go.mongodb.org/mongo-driver/mongo/options" "go.mongodb.org/mongo-driver/mongo/readpref" ) func GetClient() *mongo.Client { clientOptions := options.Client().ApplyURI("mongodb://testuser:********@test-server.provendb.io/test-server?ssl=true") client, err := mongo.NewClient(clientOptions) if err != nil { log.Fatal(err) } err = client.Connect(context.Background()) if err != nil { log.Fatal(err) } return client } func main() { c := GetClient() err := c.Ping(context.Background(), readpref.Primary()) if err != nil { log.Fatal("Couldn't connect to the database - ", err) } else { log.Println("Connected!") } } ~~~~ Any help would be awesome.
Posted by Nathaniel Peiffer about a year ago
If you are running your mongo client from within a docker container, and that mongo client is version 4.2, then you may get a "SocketException: sslv3 alert" when connecting. If this occurs, you can add the `--tls --tlsDisabledProtocols TLS1_3` flags to your connection string and you should be able to connect normally.
Posted by Guy Harrison about a year ago
I was going to sign up for service, but I am not slightly concerned, I would love to test your service vs the soon to be launched AWS Quantum Ledger DB offering. Honestly though having options for Github and Facebook and then having them unable to OAuth makes me a bit nervous. Was there an issue with this Auth client when I tried or are you using a third party OAuth agent and never initialized these social links? I'd like to hear back and I'm not trying to be a pest, I honestly would like to try your service out.
Posted by Charles LaPress 2 years ago
{"message":"MongoDB Atlas: 409 A user with username provenblock already exists.","code":"ATLAS_USER_ALREADY_EXISTS","deletable":false,"humanInterventionNeeded":true}
Posted by Stefanos Kokkalis about a year ago
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 7 months ago
When I create two documents in a collection in the mongo provendb these documents are at first not proofed in the blockchain. So far so good. When I now make the getProof request and use a filter for a single document (the second one) this document gets approved. Also fine. But when I check now the proof status of the first document it says that this document is also approved with the version number from the second document. The version number of this prove is the version of the second document. This is the first strange thing. When I then check the history of the first document I see that the newest version number is the one which it was created and not the one which will be shown in getProof. So I now have a document in the database which is approved but with a version number which is not existing for this document. When I use the verification command I see that the VersionHash and DocumentHash are the same for the second document. But for the fist document they differ. Nevertheless the command says that the document status is valid. Can you please explain me why the first document is valid even if I make a filter for just the second document. And I want to know also why the versionId which is shown in the getProof process does not exist in the history of the first document?
Posted by Sascha 7 months ago