While working with the nhost sdk with Nextjs, and using @apollo/client, I get this error, how do I rewrite the URL so that it follows the nhost naming?\

using javascript sdk... auth sessions arent sticking through page refreshes. I cant find any info on this. do I need to call something to re-init the session or something?

Does anyone use nhost with nextjs SSR? I can't really find any examples on how to fetch on SSR so just curious if anyone could give me some feedback on my approach, or if they can suggest an alternative way of doing it

Popping this to top again ... to React Native devs - has anyone else had a problem with refresh tokens getting updated but the JWT being expired on the next query? I'm likely doing something wrong... This thread: https://discord.com/channels/552499021260914688/615892613081333794/1004633806122262559

Has anyone seen this before? Wondering why it won't detect docker compose

On next.js I'm using a protected route like in this example: https://github.com/nhost/nhost/blob/main/examples/nextjs/pages/guarded-ssr.tsx However, "nhostSession" is always null. This is strange since on the client-side React, "useAccessToken()" does return a value, which confirms that I'm indeed logged in. How do I get access to the authenticated state and user inside getServerSideProps?

Hey everyone! I am using Nhost serverless functions to connect to the Hasura Events. I have an event set up for a specific function but when I trigger the function from the hasura console (or by an INSERT, UPDATE, or DELETE operation) I get this as the response... ```{ "data": { "message": "{\"type\":\"http_exception\",\"message\":\"Connection failure\",\"request\":{\"secure\":false,\"path\":\"/v1/functions/workspace-event-insert-workspace-log\",\"responseTimeout\":\"ResponseTimeoutMicro 60000000\",\"queryString\":\"\",\"method\":\"POST\",\"requestHeaders\":{\"Content-Type\":\"application/json\",\"X-B3-ParentSpanId\":\"aa2c937007b3b668\",\"X-B3-TraceId\":\"b9b1698b8f23b8e2\",\"X-B3-SpanId\":\"6b2baa2b62719f2e\",\"User-Agent\":\"hasura-graphql-engine/v2.8.1\",\"nhost-webhook-secret\":\"nhost-webhook-secret\"},\"host\":\"localhost\",\"port\":1337}}" }, "version": "2", "type": "client_error" } ``` As you can see I am doing this with the CLI on my local machine. I would say that I have the url wrong or the serverless function wrong but when I enter the url into a browser I get the response "OK" so I know it is hitting the serverless function and it returns OK. Any ideas why Hasura can't seem to connect to my serverless function?

Using nhost and Hasura, has anyone been able to create schemas apart from "public" and get them to work properly in a local Hasura console? It seems that adding any additional schemas causes the GraphQL Engine metadata to be inconsistent with the database.

where should I write if I need a dump from my cloud db?

All of a sudden, I’m getting some weird errors when I try to deploy a function