> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/publishing-apps/publishing-to-the-web/troubleshooting-domain-setup/custom-domain-is-not-secure.md).

# Custom Domain is Not Secure

If you're encountering a "not secure" error when accessing your app on a custom domain, it likely means that your website is not using an SSL certificate to encrypt the data being transmitted between the user's browser and the server. This is important for maintaining security and user trust, especially when handling sensitive information.

**Possible Reasons:**

1. **Browser Cache:**

   Clear your browser cache and cookies, as cached data might be causing the error to persist.
2. **Your SSL certificate needs to be reset:** This ensure the security of the data transmitted on your site/app. Adalo handles SSL for your domains and you can reset this in the domains section of the settings.

#### Resolution:

1. Follow the steps mentioned in [Adalo Help Doc | Resetting SSL](https://help.adalo.com/adalo-account/domains/resetting-ssl)

{% hint style="danger" %}
**Please note:** This can take up to 24h to take effect, though it usually happens much faster than that. Please not not reset your SSL multiple times without waiting the appropriate period, as you might exceed your limit on certificate regeneration attempts and will then have to wait up to 7 days to retry.
{% endhint %}

### **Still Need Help?**

If you're stuck, don't worry! Reach out to our [support team ](https://info.adalo.com/submit-a-support-ticket)for further assistance.

1. Include Steps Taken: Let us know what troubleshooting steps you've already tried.


---

# 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://help.adalo.com/publishing-apps/publishing-to-the-web/troubleshooting-domain-setup/custom-domain-is-not-secure.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.