Rank 2: Process
now no one replies
Votes
0
Replies
24
Participants
Unknown
Messages
25
Rank 2: Process
now no one replies
Please wait
Rank 4: Virtual Machine
You should definitely get some more patience, if you don't, no one will be able to help you.
Rank 2: Process
huh
Rank 2: Process
Am currently working on it
Seems like connection is bleing blocked. I would try disabling ssr
Rank 2: Process
if am building a web app obviously i would use SEO
Rank 4: Virtual Machine
Honestly, I recommend using Rest API if you use NextJS.
The SDK support is mainly only Client-sided, so for me the SDK was also completely useless. 😄
Not precisely. Discord is a web app and doesn't needs SEO in user-generated content
Rank 4: Virtual Machine
A normal website would want SEO, if you like it or not, it's something a user wants. My personal opinion is that the SDK is obviously not made for frameworks like NextJS
Rank 4: Virtual Machine
NextJS has too many references towards Server-Side, unless you make literally every page use the client, it's not recommended to use the SDK
Yes, but not for user generated content. It's being improved to have better support for SSR
Rank 4: Virtual Machine
It might be improved, but as said, as the current state I recommend just using the RestAPI
Rank 2: Process
am just thinking that
Rank 4: Virtual Machine
it can do everything anyway, it might just need a little bit more code that the sdk normally does for you, but it's less time consuming in the long run.
Rank 2: Process
how to off it
Rank 2: Process
but how to use the REST
Hey 👋 If you provide me with your project ID, I can check if there are any server errros on our end.
Other than that, I would recommend trying it client-side, just to see if that solves the problem. Also comparing development and production might reveal some information. I know basics about Next.js, but I think they do some changes to fetch - that possible doesnt play well with Appwrite. Do you know how that could be checked with Next.js? If that's the case, it would be great if you reproduced it in a simple demo app, so we can easily investigate it and write a fix in our SDKs.
Rank 2: Process
projectId: moneytube
I dont see any internal errors regarding document creation from your project, so the socket timeout is likely happening from the client-side.
Next.js is very robust framework, and this could be due to configuration, setup, build or compatiblity with SDK. Since I am not expert with Next.js, I cant give exact answers. Trying to turn features on/off is a great step towards figuring out what exactly it's that Next doesnt like about Appwrite. I have seen projects built with Next.js both using server-side rendering and client-side rendering, so I am sure there is some solution.
I would recommend trying what D5 suggested, and seeing if not using SSR makes it work properly.
Rank 2: Process
ohky thnkx for your time
Rank 4: Virtual Machine
Heyo. Check the references in the docs and change web to rest
Rank 4: Virtual Machine
You can find specific info in the Docs -> Rest API about certain endpoints
Rank 4: Virtual Machine
I recommend reading through the docs and get a better understanding of how to properly use the Appwrite REST. If you don't know how make fetch requests, please read the nextjs docs:
https://nextjs.org/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating
https://nextjs.org/docs/app/building-your-application/routing/route-handlers