{
  "id": 20387120,
  "title": "Forge Custom UI blank page after deploy: Vite asset paths",
  "url": "https://urgent.news/2026/11/17/forge-custom-ui-blank-page-after-deploy-vite-asset-paths",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-17T05:59:43.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/mihai_leanzero/forge-custom-ui-blank-page-after-deploy-vite-asset-paths-49ia"
  },
  "original_language": "en",
  "account": "A Forge Custom UI app built with Vite can render correctly on forge tunnel, but may show a blank page after deployment. The issue stems from Vite's default behavior of generating absolute asset paths in the index.html file. On November 17, 2026, a Forge Custom UI test site on Jira experienced this problem, with HTTP 422 responses from the assets. Adding base: \"./\" to the vite.config.js file resolved the issue.\n\nForge is Atlassian's platform for apps that run on their cloud, and Custom UI is the option where your own HTML and JavaScript run inside an iframe. Vite is the front-end build tool that transforms your source code into the files Forge serves. forge tunnel serves the app from your local machine during development, while forge deploy uploads it to Atlassian's servers.\n\nThe problem arises because forge tunnel and forge deploy serve the app from different locations. When using forge tunnel, the Forge CLI serves the folder specified in the manifest's resources entry from your local machine. When deploying, the same folder is hosted on Atlassian's CDN. The iframe's URL points to a resource outside your app, causing the browser to request the assets from the top-level of the host, rather than within your app's folder.\n\nThis issue is similar to the one mentioned in Atlassian's access to static assets documentation, which advises using \"./assets/image.png\" instead of \"/assets/image.png\" for relative paths. The provided steps outline how to confirm the issue, inspect the index.html file for absolute paths, set the base configuration in Vite, rebuild the app, fix any remaining relative paths in the JavaScript, deploy again, and verify that the assets load correctly within the app's folder.",
  "summary": "A Forge Custom UI app built with Vite can render under forge tunnel and then show a blank page after forge deploy . The cause is Vite's default build, which writes absolute asset paths such as /assets/index-xxx.js into index.html . We reproduced it on our Jira test site on 17 November 2026, and both assets returned HTTP 422 with the body Invalid URL . Adding base: './' to vite.config.js fixed the…",
  "key_points": [
    "Forge Custom UI blank page after deployment",
    "Vite generates absolute asset paths in index.html",
    "Adding base: ./ to vite.config.js resolves issue"
  ],
  "editors_take": "Misconfigured asset paths in Vite force developers to shift from absolute to relative addressing to ensure Forge Custom UI applications function correctly once moved from local tunnels to Atlassian servers.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}