Nillion Testnet- nilDB Schema Restrictions

[kaustav1311]

Hi, I have developed a next js app, which basically tries to simply create a personalized dashboard for the user based on their transaction history.

I am utilising nilDB to store data (some plain text fields, some encrypted fields).

My back end connects to secretvault and has multiple custom api to store-selection, analyze-wallet, fetch-metrics etc as routes.

When I tested on localhost, I am able to smoothly run through the whole orchestration. I deployed backend on render and frontend on Vercel, still able to run the whole orchestration on my own device/ip.

The issue happens when anyone other than me tries to access these back end routes.

Store selection -> creates new record with plain text fields and placeholders for other fields (success both in my own ip and external too).

Analyze -wallet-> calculates the metrics and tries to update the data stored in the nodes for the record.

Works smooth in the local and Vercel app when I do it on my local, but the POST/updatedatatonodes function doesn't work even when calculations are going. Through in the back end.

Is this some ip configuration/restriction issue with the Nillion Test Organizations that get created by the documentation procedure on Nillion builder docs?

//docs.nillion.com/build/secretVault-secretDataAnalytics/acces
I followed it through.

[tim-hm]

Hi @kaustav1311, can you confirm if your nextjs app is calling the nildb api directly? I ask because the current version does not support CORS and so that seems the most likely culprit here.

If you have any logs you can share or the codebase happy to take a look?