# No site found

> no_output, no_site, ssr_output — the build passed but there is nothing to serve. And what to do when the page opens blank.

Source: https://livops.dev/en/docs/error-output

## `no_output`: the output folder was not found

The build passed, but the folder in **Settings → Output** is not there. Frameworks usually write here:

| Framework | Folder |
| --- | --- |
| Vite, Vue, Svelte | `dist` |
| Create React App | `build` |
| Astro | `dist` |
| Angular | `dist/<project name>/browser` |
| Hugo | `public` |

If yours is different (say `build.outDir` in `vite.config`), set it in Settings.

## `no_site`: we could not tell what this project is

The build produced nothing and there is no file to serve. If it is a site, pick the framework in Settings or name the output folder. If it is a server or a bot, change the project type to **Application** or **Bot**.

## `ssr_output`: pages are rendered on the server

This app (Next.js, Nuxt, SvelteKit in SSR mode) renders each page on request. Deploy it as an **Application**, not a static site.

## The page opens, but blank

The log says `isn't in the build`. The page looks for its JS or CSS under another path. Check `base` in Vite or `basePath` in Next.js — for a site at the root it is `/`.

## The frontend calls `localhost`

In a visitor's browser `localhost` is their own computer. Put the API address in a variable and deploy again:

```js
const api = import.meta.env.VITE_API_URL
```

## The page loads files over `http://`

On an https page the browser blocks scripts and images over `http://`. Use `https://` or a path on the same site.
