> For AI agents: the complete documentation index is available at /en/llms.txt, the full documentation bundle is available at /en/llms-full.txt.

# Troubleshooting

## I got an email saying the build failed \{#jag-fick-ett-mejl-om-att-bygget-misslyckades}

The email contains the cause and the last 50 lines of the build log. Your site
**keeps showing the latest successful version** until the next build succeeds —
your visitors notice nothing.

Common causes, with the text as it appears in the email:

| In the email                        | What it means                                                                                                                                                                        |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `git fetch failed`                  | We can't reach the repository. Check that the deploy key is still there and that the repository's SSH address hasn't changed (for example if the project has been renamed or moved). |
| `git submodule failed`              | A submodule can't be fetched. It must be public — see [Themes](/en/static/hugo.md#teman).                                                                                            |
| `the build exited with code 1`      | Hugo found an error. The line with `ERROR` in the log excerpt tells you which file and line. Run `hugo` locally with the same version to see the same error.                         |
| `exited with code 255` or `aborted` | The build took more than 10 minutes and was aborted.                                                                                                                                 |
| `index.html is missing`             | The build succeeded but produced no home page. Check `baseURL`, and that the site has content or a `layouts/index.html`.                                                             |
| `symbolic link in the output`       | The built result contains a symbolic link. For security reasons we never publish those.                                                                                              |

Fix the error and push again.

## The webhook responds with an error \{#webhooken-svarar-med-fel}

| Response | Meaning                                                                                |
| -------- | -------------------------------------------------------------------------------------- |
| **202**  | All good — the build has started.                                                      |
| **403**  | The key in the address doesn't match. Check that you copied the whole webhook address. |
| **404**  | The address is wrong, or the site is suspended (see below).                            |
| **405**  | The request came as a GET. The webhook must send a POST.                               |

## The domain shows nothing or a certificate error \{#domanen-visar-ingenting-eller-ett-certifikatfel}

1. **Does DNS point the right way?** `dig +short www.example.com` should return
   `static.getgeek.se.` (or `94.142.251.165` for a domain without a prefix).
2. **Does the verification record exist?**
   `dig +short TXT _getgeek-static.www.example.com` should return your code.
   Without it we don't publish the site on the domain.
3. **Has the DNS change had time to propagate?** We check the verification record
   every ten minutes and email you when the domain is verified. Old DNS answers
   can, however, be cached by your provider for up to a few hours. The
   certificate is issued automatically as soon as DNS points the right way.

You can also press **Kontrollera domäner nu** (check domains now) on the service
page. The status shows, per domain, whether it is verified, waiting for a TXT
record or used by another account. If it still isn't right after an hour, get in
touch and we will take a look.

## The site shows "This site is temporarily suspended" \{#sajten-visar-den-har-sajten-ar-tillfalligt-avstangd}

The site has been suspended, usually because of an unpaid invoice. The content
is still there, and the site is back once the service is active again, which
happens when the invoice is paid. Contact us at [support@getgeek.se](mailto:support@getgeek.se) if you are
unsure why.

## I want to roll back to an earlier version \{#jag-vill-backa-till-en-tidigare-version}

We keep the five most recent versions. Press **Rulla tillbaka** (roll back) on
the service page in the portal — it takes a few seconds and goes one step back.
Press it again to go one more step. **Senaste version** (latest version) takes
you back to the newest one. The next push then publishes as usual.

You can also do it yourself in git: `git revert` whatever went wrong, and push.
