Hello everyone,
I'm encountering a persistent issue with deployment on Appwrite Sites that manifests in two distinct but likely related failure modes. The problem is centered on the rendering mode configuration (Static vs. SSR) and how the platform serves the built files.
Here is a detailed breakdown of the problem:
Server-Side Rendering (SSR) Build Failure: When the project is configured for Server-Side Rendering (SSR) in the Appwrite Console's Build Settings, the deployment build process consistently fails. The logs indicate an error during this phase, preventing the build from completing successfully.
Static Site Deployment & 404 Error: If I bypass the SSR issue by selecting the "Static site" option, the build process completes successfully and the deployment is marked as active. However, accessing the deployed site results in a "404 Page Not Found" error. This suggests that while the build artifacts are created, they are either not being placed in the expected output directory or the web server is not correctly configured to serve them, particularly for client-side routing common in Single Page Applications (SPAs) #sites-hackathon
Recommended threads
- Usage of the new Client() and dealing wi...
Hey guys, just a quick one - we had some web traffic the other day and it ended up bombing out - To put in perspective of how the app works, we have a Nuxt Ap...
- Cloud function deploy stucks in processi...
Been trying for the last hours to deploy my function but for whatever reason, alwasy stuck on processing!
- One-time Cloud migration blocked by data...
Hi, I’m blocked on a one-time migration from Appwrite Cloud to my self-hosted Appwrite instance. We already fixed the region issue, and the migration now corre...