When deploying a Next.js standalone build to cPanel, data changes after revalidation might not be reflected due to caching or how the server handles file updates. Here's how to address this:
-
Verify Standalone Output:Ensure your
next.config.jsfile hasoutput: 'standalone'. After building, confirm that the.next/standalonefolder containsserver.js, necessary dependencies, and thepublicand.next/staticfolders. If these folders are missing, manually copy them to thestandalonedirectory. -
Check cPanel Setup:In cPanel, when setting up the Node.js application, ensure the "Application root" is correctly pointing to the directory containing your
server.jsfile (usually withinpublic_html). The "Application startup file" should beserver.js. -
Restart Node App:After deploying or making changes, restart the Node.js application in cPanel. This ensures the server picks up the latest build and data. Sometimes, you may need to stop the application, run
npm installagain, and then restart it. -
Bypass Cache:If data is still not updating, it could be due to server-side caching. In your
next.config.js, you can add headers to prevent caching:if u uploaded it in cpanel with ISR then must addexport const dynamic = 'force-dynamic'; in the page.tsx
