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 deployed panel.
If you're new to these names: Forge is Atlassian's platform for apps that run on Atlassian's cloud, and Custom UI is the Forge option where your own HTML and JavaScript run inside an iframe. Vite is the front-end build tool that turns your source into the files Forge serves. forge tunnel serves the app from your own machine while you develop, and forge deploy uploads it to Atlassian.
People keep running into this one. On 24 July 2025 a developer posted on the Atlassian developer community that their issue panel was not working without forge tunnel .…