Troubleshooting

Installation

Find answers to common installation issues.

Cannot clone the repository

Issues related to cloning the repository are usually related to a Git misconfiguration in your local machine. The commands displayed in this guide using SSH: these will work only if you have setup your SSH keys in Github.

If you run into issues, please make sure you follow this guide to set up your SSH key in Github.

If this also fails, please use HTTPS instead. You will be able to see the commands in the repository's Github page under the "Clone" dropdown.

Please also make sure that the account that accepted the invite to TurboStarter, and the locally connected account are the same.

My environment variables from .env.local file are not being loaded

Make sure you are running the pnpm dev command from the root directory of your project (where the pnpm-workspace.yaml file is located)

Also, ensure that the .env.local files are present in the apps that need them. For example, the .env file should be present in the apps/web directory for the web app.

TurboStarter uses the dotenv-cli to load environment variables from a .env files. The dotenv-cli is automatically used when running the pnpm dev command from the root directory.

Next.js server doesn't start

This may happen due to some issues in the packages. Try to clean the workspace using the following command:

pnpm clean

Then, reinstall the dependencies:

pnpm i

You can now retry running the dev server.

Local Supabase doesn't start

If you cannot run the Supabase local development environment, it's likely you have not started Docker locally. Supabase requires Docker to be installed and running.

Please make sure you have installed Docker (or compatible software such as Colima, Orbstack) and that is running on your local machine.

Also, make sure that you have enough memory and CPU allocated to your Docker instance.

Last updated on

On this page

Ship your startup everywhere. In minutes.Get TurboStarter