The troubleshooting tips on this page assume some familiarity with the technologies used. For full guidance on using the integrations, check out the Integrations section. That section includes introductory information, so it’s a good starting point if you’re new to publishing, databases, and so on.

​
Bolt failed to publish to Netlify

Publish manually to Netlify:
  1. Run the project build command (usually npm run build).
  2. Click Download to download the project.
  3. Follow Netlify’s Manual deploy instructions.
Note that 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. 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.

​
”Another project is already using this domain” error

If you see this error, it usually means the domain is still connected to a previous deployment on another hosting service (for example, Netlify). This happens when the domain was not fully removed from that service’s domain management settings. To fix this issue, try following these steps:
  1. Log in to the hosting service where the domain was previously connected (for example, Netlify).
  2. Go to the domain management settings.
  3. Check if your domain is still listed or connected to any old projects.
    Domain records can be confusing, and that’s completely normal. If you run into any trouble, reach out to your registrar’s support team for help.
  4. Remove the domain if it is still connected.
  5. Return to your Bolt dashboard and try connecting the domain again.

​
GitHub authentication issues

This occurs when:
  1. You signed up for Bolt using a GitHub account.
  2. Then you created a new Bolt account, then try to connect the same GitHub account to this new account in the GitHub integration.
If you use GitHub for authentication to log in to Bolt, it’s also used by the GitHub integration by default. You can’t separate these uses. To resolve this and use the GitHub account in the new Bolt account:
  1. Create a new login method for the old account:
    1. In the first Bolt account (where you originally signed up using GitHub), do a password reset using the email address associated with the GitHub account. This creates an email + password login for the Bolt account.
    2. Log out.
  2. Remove GitHub authentication from the old account:
    1. Log in to the old account using the email and password.
    2. Go to Settings > Credentials.
    3. On the GitHub section, click Delete.
  3. Connect the GitHub integration in the new account:
    1. Log in to the new account where you want to use the GitHub integration.
    2. Go through the steps to connect the GitHub integration as normal.

​
Supabase row level security rules aren’t working

Prompt Bolt to remove all the rules, then prompt to add the relevant row level security rule back in.

​
Supabase edge functions

This diagram outlines some example services users may want to use edge functions for, and how these interact with one another. At each point of interaction in the diagram, there is the potential for an error: Edge Functions

​
CORS (cross-origin resource sharing) errors

If your edge function isn’t working, it may be due to a CORS error. To check this:
  1. Open Chrome DevTools: press Command + Option + J on Mac, Control + Shift + J on Windows or Linux.
  2. Check the Network tab. Look for errors related to CORS.
  3. Next, check if CORS headers are set correctly in the file responsible for your edge function. Here are the CORS headers for a chatbot built with Bolt using OpenAI: 
    const corsHeaders = {
'Access-Control-Allow-Origin': '*',
'Access-Control-Allow-Methods': 'POST, OPTIONS',
'Access-Control-Allow-Headers': 'Content-Type, Authorization',
};
You can use Discussion Mode to ask Bolt if CORS headers exist and are set correctly in your application.

​
Missing secret

When using edge fuctions with services like OpenAI, you must add the secret in the Edge Functions section of your project in Supabase. With your project open, hover over the left-hand side of the page and open Edge Functions > Secrets: "Screenshot of the secrets button in Supabase" After doing this, prompt Bolt to make it aware of this update and continue development.

​
Webhooks: authorization headers and JWT

If you have a webhook that is invoked by a third-party service (for example, GitHub or Slack), you need to disable JWT verfication on your edge function in Supabase and add any forms of validation and authorization that are required. For example, GitHub describes the proper procedure for validating webhook deliveries.