Restarting Development Server

When your development server gets stuck, you have the option to restart.

Just as when you're working locally, there are a number of factors that may result in needing to restart your development server.

Stackbit is smart and picks up many of these scenarios. For example, when you change anything in your package.json file in the code editor, Stackbit will automatically restart your development server.

If you run into an issue in which the visual editor or your website isn't behaving as you'd expect, try this series of steps:

  1. Refresh your browser: That's fast and often resolves minor issues.
  2. Restart the development server: This can be done by opening your project settings, going to the Advanced tab, and scrolling down to Troubleshooting. Choose Restart Preview. This usually takes about as long as it does to boot your local Next.js development server.
  3. Restart container: If you still haven't cleared the issue. There is a Restart Container button below the Restart Preview button. This restarts the entire editing experience, which usually takes a few minutes to complete.
Troubleshooting settings
Troubleshooting settings

If you're still having trouble after following these steps, contact us.