Check Bolt’s status
Before troubleshooting, check the Bolt status page for any active incidents. If Bolt is experiencing a known issue, check your project again after the issue resolves to see if that also resolves your problem.”Project is too large to deploy” error
To publish successfully, Bolt projects must be under 100MB. This is the combined size of your project files. If your project is larger than 100MB, you’ll see the following error when publishing:Project is too large to deploy. The maximum allowed size is 100MB.
Your overall project size is different from your project context window. If you see a message about your context being too large, see Manage project context.
- Check how large your project is.
- Try deleting any images you aren’t using and check your project size again.
- If the project is still too large, move your media to an external storage service.
- Then, prompt Bolt to retrieve the images from the URL rather than from a file path in your project.
- Finally, delete the files from your project.
Check your project size
- Download your project.
- Find the project folder on your computer.
- Right-click the folder and view its information. This should include the project’s size.
Delete unused images and videos
- If you didn’t already, download your project as a backup before deleting any files.
- Prompt Bolt to find and remove media that isn’t being used in your project, such as multiple versions of an image you uploaded. You can use a prompt like:
Find any images or videos that aren't being used in this project and delete them. - Download a new copy of your project and check its size again.
Move media files to an external storage service
Instead of storing images and videos in your project, you can host them with an external storage service and prompt Bolt to reference the external URL instead of the local file. Here are a few options to consider for external media storage. Except for Cloudflare Images, each provider has a free plan available.
After choosing a storage provider, download your media files from Bolt, then upload them to the external service.
Prompt Bolt to reference your files from the external storage provider
When you move the media files outside your project, Bolt doesn’t automatically know where to find them. After moving each file:- Prompt Bolt to update the location where it gets the image or video from. You can use a prompt like:
Update references to the [file name] to use this URL instead: [URL] - When Bolt finishes replacing the reference, delete the media file from your project. You can prompt Bolt to do this, or do it yourself from Code view.
”This site can’t be reached” error
If you see this error when you open your published.bolt.host site, your device or network DNS settings may not be able to open the site’s address:
This site can’t be reached.<your-site>'s server IP address could not be found.DNS_PROBE_FINISHED_NXDOMAIN or DNS_PROBE_FINISHED_BAD_CONFIG
This error doesn’t mean your site failed to publish, only that you can’t open it on the device or network you’re using. Republishing your site won’t fix the error; you need to troubleshoot your DNS or network settings.
To check whether your device or network is the problem:
- Open your site using your phone’s mobile data instead of WiFi, with any VPN or DNS-changing app turned off. If it loads, your site is working, and your original network or device DNS is the problem.
- If you don’t have mobile data, try a different WiFi network or your phone’s hotspot.
- On Android, open Settings and search for Private DNS. If it’s set to Private DNS provider hostname, choose Automatic, then tap Save.
.bolt.host address. Continue to the next section and follow the provider and router steps in “Site can’t provide a secure connection” error.
If the error appears on every network you try, contact support and include your site’s URL.
”Site can’t provide a secure connection” error
If you see this error when you open your published site, your network or internet provider may be blocking.bolt.host addresses:
This site can’t provide a secure connection.<your-site>.bolt.host sent an invalid response.ERR_SSL_PROTOCOL_ERROR
This error doesn’t mean your site failed to publish or that it’s unsafe to view. Some network security filters block sites on uncommon domains, like .bolt.host, even when the site itself is safe.
To find out whether your network is blocking your site:
- Open your site using your phone’s mobile data instead of WiFi, with any VPN turned off. If it loads, your site is working, and your original network is blocking it.
- If you don’t have mobile data, try a different WiFi network or your phone’s hotspot.
- Check your internet provider’s settings for a security or web-protection feature, and allow your site’s address there. On a work or school network, ask your IT team to allow it.
- Check your WiFi or router settings for an option to manage trusted or allowed domains, and add
.bolt.hostto that list.
”Could not find a build output directory” error
When you publish, Bolt does the following:- First, it builds your project, which means that it turns your code into the finished files that make up your website.
- Then, Bolt looks for the folder where those finished files were saved. Often, this folder is called
distorbuild.
Could not find a build output directory to publish.
Usually, this error means that the finished files ended up somewhere Bolt didn’t expect, or they weren’t created at all.
It doesn’t mean your project or code is lost, only that Bolt needs to fix where the files are located or how they’re built before it can publish your site.
If your project is a server-rendered app, like a TanStack Start app, follow the steps in “Contains no HTML file” error instead.
To fix the error:
-
In the chat, paste the error message and ask Bolt to fix it. For example:
Publishing fails with "Could not find a build output directory." Check how this project builds and fix it so it can be published. - Wait for Bolt to finish making changes.
- Click Publish again.
”Contains no HTML file” error
This error appears when you publish a project that builds as a server-rendered app:The build finished, but "<folder>" contains no HTML file, so the published site would show only 404 pages.
A server-rendered app builds its pages on a server each time someone opens them. Bolt hosting publishes pages that are already built as HTML files, so an app built this way with a framework like TanStack Start, SvelteKit, Remix, or Astro needs to change how it builds before you can publish it. Next.js apps don’t need this change, because Bolt hosting supports server rendering for Next.js.
To fix the error:
-
In the chat, paste the error message and ask Bolt to build the app as a static site. For example:
Publishing fails with "contains no HTML file." Change this project so the build outputs static HTML files, using SPA mode or prerendering, so it can be published to Bolt hosting. - (Optional) If your app has code that needs to run on a server, like code that uses secret API keys, ask Bolt to move that code into server functions.
- Wait for Bolt to finish making changes.
- In the top-right corner of the screen, click Publish again.
Pages other than the home page show “Page not found”
If your home page loads but other pages on your published site show a “Page not found” error, your site can’t find those pages when you open them directly. This happens when you refresh a page, open a link to it, or type its address in your browser. Single-page apps, like many React, Vue, and Svelte apps, load every page from one file,index.html. When a visitor opens a page like /login directly, the site looks for a file at that address and doesn’t find one. A redirect rule sends those visitors to index.html, so your app can show the right page.
To add a redirect rule to your project:
-
In the chat, ask Bolt to add the rule. For example:
On my published site, refreshing or opening any page except the home page shows "Page not found." Add a _redirects file with the rule "/* /index.html 200" so it's included in the published files. If this project has a netlify.toml file, add the same rule to it as a redirect instead. - Wait for Bolt to finish making changes.
- In the top-right corner of the screen, click Publish, then click Update.
- Open your published site, go to a page other than the home page, and refresh the page to check that it loads.
Bolt failed to publish to Netlify
If Bolt fails to publish, you have the option of publishing manually to Netlify:- Run the project build command (usually
npm run build). - Click Download to download the project.
- Follow Netlify’s Manual deploy instructions.
Bolt calls this feature Publish, whereas Netlify calls it Deploy.
Bolt loses connection to Netlify when duplicating projects
If you fork or duplicate your project, you’ll need to reconnect to Netlify. To do so, follow the steps in the Netlify integration guide. Doing this will create a new Netlify site, so you’ll need to make sure your custom domains are pointed to the new site:- If you bought your domain through Netlify and you’re using Netlify DNS, you can remove the domain from the old site and add it to the new one, all in Netlify. This Netlify support answer provides more information.
- If you use another domain provider, look for their guide to updating domains.