> For the complete documentation index, see [llms.txt](https://vitrina-blogerov.gitbook.io/bloggers-showcase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/possible-errors/502-error-or-the-storefront-is-temporarily-unavailable.md).

# 502 error or the storefront is temporarily unavailable

The domain opens, but instead of the storefront, a 502 page is shown.

{% hint style="info" %}
502 usually means that the external Caddy is running, but cannot get a response from the backend of the selected language version.
{% endhint %}

### Symptoms

* the domain opens, but shows 502;
* one language version works, while the other does not;
* the admin panel and storefront of one version are unavailable;
* The Telegram Mini App shows a loading error.

### Possible causes

* the backend is still starting;
* the backend crashed;
* the database did not start;
* the backend cannot connect to PostgreSQL;
* the containers were stopped;
* the edge configuration is outdated after language changes.

### What to check

Check the containers of the required version:

```bash
sudo /opt/bloggers_platform/apps/ru/manager.sh status
```

Check the logs:

```bash
sudo /opt/bloggers_platform/apps/ru/manager.sh logs
```

If the problem is in routing, check the edge:

```bash
sudo /opt/bloggers_platform/manager.sh logs
```

### How to fix it

If this happened right after installation or an update, wait a couple of minutes.

If the containers did not recover, restart the version:

```bash
sudo /opt/bloggers_platform/apps/ru/manager.sh restart
```

If a new language version was added, update the edge:

```bash
sudo /opt/bloggers_platform/manager.sh refresh
```

### When to contact support

If 502 remains after restarting, logs are needed `backend` and `db` of the required language version.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://vitrina-blogerov.gitbook.io/bloggers-showcase/product-docs/product-docs-en/possible-errors/502-error-or-the-storefront-is-temporarily-unavailable.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.