Skip to content
Sites Hackathon is live / Aug 29 - Sep 12
Back

Adapter Mismatch

  • 0
  • Web
  • Cloud
remy
29 Aug, 2025, 18:51

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

TL;DR
Developers are facing deployment issues on Appwrite Sites related to Adapter Mismatch in rendering modes (Static vs. SSR). When configured for SSR, build process fails, and with Static Site, 404 errors occur. To resolve, developers should ensure correct output directory for build artifacts and proper web server configuration for SPAs.
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more