{"id":21130,"date":"2026-10-21T02:59:42","date_gmt":"2026-10-21T02:59:42","guid":{"rendered":"https:\/\/www.hostinger.com\/support\/?p=21130"},"modified":"2026-10-21T03:32:59","modified_gmt":"2026-10-21T03:32:59","slug":"how-to-fix-changes-not-showing-after-a-node-js-deployment-at-hostinger","status":"publish","type":"post","link":"https:\/\/www.hostinger.com\/support\/how-to-fix-changes-not-showing-after-a-node-js-deployment-at-hostinger\/","title":{"rendered":"How to fix changes not showing after a Node.js deployment at Hostinger"},"content":{"rendered":"<p>When Node.js changes are not showing after a deployment at Hostinger, there are six common causes: the deployment didn&rsquo;t run or failed, the build settings point to the wrong place, a cache serves the old version, a build-time environment variable wasn&rsquo;t rebuilt, an old app process is still running, or only one of <code>domain.tld<\/code> and <code>www.domain.tld<\/code> is updated. Go through the steps below in order.<\/p><h2 id=\"h-fix-node-js-changes-not-showing-after-a-deployment\">Fix Node.js changes not showing after a deployment<\/h2><h3>Step 1 &ndash; Check that the new deployment ran<\/h3><p>Open the website dashboard of your Node.js app and go to <b>Deployments<\/b>. Look for a deployment of your latest change and check its status:<\/p><ul>\n<li><b>No new deployment:<\/b> the change didn&rsquo;t start a deployment. For GitHub deployments, follow the GitHub connection steps in the FAQ of <a data-click-id=\"hgr-post-content-link-how-to-add-a-node-js-web-app-in-hostinger\" href=\"https:\/\/www.hostinger.com\/support\/how-to-deploy-a-nodejs-website-in-hostinger\/\">how to add a Node.js web app in Hostinger<\/a>, and check that Hostinger can access the repository, as described in <a data-click-id=\"hgr-post-content-link-how-to-update-github-repository-permissions-for-node-js-host\" href=\"https:\/\/www.hostinger.com\/support\/how-to-update-github-repository-permissions-for-node-js-hosting\/\">how to update GitHub repository permissions for Node.js hosting<\/a>. For ZIP deployments, upload the new <code>.zip<\/code> file when you <a data-click-id=\"hgr-post-content-link-redeploy-the-node-js-application\" href=\"https:\/\/www.hostinger.com\/support\/how-to-redeploy-a-node-js-application\/\">redeploy the Node.js application<\/a>.<\/li>\n<li><b>Failed deployment:<\/b> the previous version stays live. Open the build logs to find the cause, as described in <a data-click-id=\"hgr-post-content-link-how-to-troubleshoot-node-js-deployment-build-errors-at-hosti\" href=\"https:\/\/www.hostinger.com\/support\/how-to-troubleshoot-a-failed-node-js-deployment-using-build-logs\/\">how to troubleshoot Node.js deployment build errors at Hostinger<\/a>.<\/li>\n<\/ul><p><b>NOTE<\/b><\/p><ul>\n<li>Use the <b>Deployments<\/b> page, not the File Manager&rsquo;s <b>Last modified<\/b> column, to confirm when a deployment went live. Files extracted from a <code>.zip<\/code> archive keep their original timestamps.<\/li>\n<\/ul><h3>Step 2 &ndash; Check the deployment settings<\/h3><p>Click <b>Settings and redeploy<\/b> and confirm that these settings match your project:<\/p><ul>\n<li>The branch you pushed your change to.<\/li>\n<li>The root directory, especially in a monorepo. See <a data-click-id=\"hgr-post-content-link-how-to-deploy-monorepos-with-npm-yarn-or-pnpm-on-hostinger\" href=\"https:\/\/www.hostinger.com\/support\/how-to-deploy-monorepos-with-npm-yarn-or-pnpm-on-hostinger\/\">how to deploy monorepos with npm, yarn or pnpm on Hostinger<\/a>.<\/li>\n<li>The build command, output directory and entry file.<\/li>\n<\/ul><h3>Step 3 &ndash; Clear the caches<\/h3><p>Caches can keep serving the previous version after a successful deployment. Clear them in this order:<\/p><ol>\n<li>Purge the CDN cache in the Hostinger dashboard, as described in <a data-click-id=\"hgr-post-content-link-hostinger-cdn-how-to-clear-the-cache\" href=\"https:\/\/www.hostinger.com\/support\/hostinger-cdn-how-to-clear-the-cache\/\">Hostinger CDN: How to clear the cache<\/a>.<\/li>\n<li>Open the website in an incognito or private browser window.<\/li>\n<li>Clear the site data in your browser if the website is a Progressive Web App (PWA) or uses a service worker, because the service worker can serve the old version.<\/li>\n<\/ol><h3>Step 4 &ndash; Redeploy after changing build-time environment variables<\/h3><p>Redeploy the app if you changed an environment variable that starts with <code>NEXT_PUBLIC_<\/code> or <code>VITE_<\/code>. These variables are added to the app during the build, so a restart doesn&rsquo;t apply them. See <a data-click-id=\"hgr-post-content-link-how-to-edit-or-add-environment-variables-after-deployment\" href=\"https:\/\/www.hostinger.com\/support\/how-to-edit-or-add-environment-variables-after-deployment\/\">how to edit or add environment variables after deployment<\/a>.<\/p><h3>Step 5 &ndash; Restart the app<\/h3><p>Restart the app from the website dashboard by clicking <b>Running<\/b> and selecting <b>Restart<\/b>. An old copy of the app can keep running in the background and serve the previous build. If the restart doesn&rsquo;t help, open the <a data-click-id=\"hgr-post-content-link-resource-usage\" href=\"https:\/\/www.hostinger.com\/support\/2436138-how-to-check-resource-usage-in-hostinger\/\">Resource Usage<\/a> page and click <b>Stop running processes<\/b>.<\/p><h3>Step 6 &ndash; Check both domain.tld and www.domain.tld<\/h3><p>Open both <code>domain.tld<\/code> and <code>www.domain.tld<\/code>. Each version of the domain runs a separate process, so one can show the new version while the other still shows the old one.<\/p><p>After these checks, your Node.js website shows the latest deployed version. If a deployment keeps failing, the build logs point to the exact step that needs fixing.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Find out why a deployed Node.js website still shows the old version, and fix it.<\/p>\n","protected":false},"author":594,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"include_on_kodee":true,"footnotes":""},"categories":[301],"tags":[],"class_list":["post-21130","post","type-post","status-publish","format-standard","hentry","category-node-js"],"hreflangs":[],"include_on_kodee":true,"_links":{"self":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/21130","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/users\/594"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/comments?post=21130"}],"version-history":[{"count":4,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/21130\/revisions"}],"predecessor-version":[{"id":21154,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/21130\/revisions\/21154"}],"wp:attachment":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/media?parent=21130"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/categories?post=21130"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/tags?post=21130"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}