Next.js SSR Site Times Out on First Visit After Inactivity, Then Loads Fine on Refresh

Hey everyone,

I'm running a Next.js SSR site on a self-hosted Appwrite server (v1.9.0), and I've noticed a strange behavior that I'm hoping someone can help me understand.

The site is deployed through Appwrite Sites and is currently pre-launch, so it gets very little traffic.

Whenever the site hasn't been visited for a while, the first request often ends up showing an Appwrite timeout/error page (as shown in the screenshot). However, if I refresh a few seconds later, the site loads normally and works perfectly.

This feels similar to a cold-start issue, but I'd expect the initial request to simply take longer rather than eventually timing out and showing an error page.

My concern is that most visitors won't refresh after seeing an error page - they'll assume the site is broken and leave.

Has anyone else experienced this with Next.js SSR deployments on self-hosted Appwrite?

A few questions:

• Is this expected behavior when an SSR site has been idle for some time?
• Is there a configuration that can prevent the first request from timing out?
• Are there recommended timeout, container, or scaling settings for self-hosted Appwrite Sites running Next.js SSR?

I'd appreciate any guidance or suggestions on what to check.

Thanks!