> 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/https-did-not-appear-immediately.md).

# HTTPS did not appear immediately

The site opens only over HTTP, the browser shows a certificate error, or HTTPS does not start working immediately after installation.

### Symptoms

* the browser shows a certificate warning;
* `https://` does not open;
* `http://` opens, but HTTPS does not;
* Telegram Mini App does not start because of secure connection issues.

### Possible causes

* the domain has not yet been pointed to the server;
* ports `80` or `443` are closed;
* Caddy could not issue a certificate;
* Let's Encrypt temporarily rejected the request;
* DNS has recently changed and has not yet propagated.

### What to check

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

Check port availability from the outside via the hosting panel or an external port checker.

### How to fix it

1. Make sure the domain points to the server.
2. Check that the following ports are open `80` and `443`.
3. Update the edge configuration:

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

4. Check the Caddy logs:

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

{% hint style="warning" %}
Telegram Mini App requires HTTPS. Until the certificate is issued, the catalog may open unreliably in the browser, and may not open at all in Telegram.
{% endhint %}

### When to contact support

If Caddy explicitly writes in the logs about a certificate issuance error, save the error text. It usually shows whether the problem is with DNS, the firewall, or the certificate authority's limits.


---

# 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/https-did-not-appear-immediately.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.