mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 09:25:06 +03:00
feat(docs): add lovable cloud troubleshooting guides (#40115)
* Add cant access to supabase * Add identify lovable backend guide * Improve guide with images and components * Improve style * Fix relative urls * Apply formatting rules * Put link in line * Apply formatting rules * Add Lovable and Lovable Cloud to words allows_list * Use Admonition for note * Apply several improvements to content
This commit is contained in:
Tomás Pozo authored and GitHub committed
1 parent
84126faa0a
commit
52cb7b654c
7 files changed
+280
No files matched your search
@@ -0,0 +1,131 @@
|
||||
---
|
||||
title = "Can’t Access Supabase Project When Using Lovable Cloud"
|
||||
topics = [
|
||||
"ai",
|
||||
]
|
||||
keywords = [
|
||||
"lovable",
|
||||
"lovable cloud"
|
||||
]
|
||||
---
|
||||
|
||||
## Problem
|
||||
|
||||
Your Lovable project has **Lovable Cloud** enabled, and you’re trying to connect directly to your Supabase project.
|
||||
|
||||
However, you don’t see the project listed on your [Supabase Dashboard](/dashboard), or you’re unable to access it through your Supabase account.
|
||||
|
||||
## Why this occurs
|
||||
|
||||
When you create a project connected to **Lovable Cloud**, the underlying Supabase instance is provisioned and managed entirely by **Lovable**.
|
||||
|
||||
These projects are not owned by your Supabase account, so they **don't appear on your Supabase Dashboard** or be accessible using your Supabase credentials.
|
||||
|
||||
## How to diagnose
|
||||
|
||||
You might be affected by this if:
|
||||
|
||||
- You recently created a project on Lovable and enabled the backend from the chat interface. By default, the Lovable platform uses **Lovable Cloud** for backend hosting.
|
||||
- You see Supabase references in your project’s configuration but **can’t access the project** from your [Supabase Dashboard](/dashboard).
|
||||
- The project ID or credentials used in your Lovable setup don’t match any project under your Supabase account.
|
||||
|
||||
## How to fix
|
||||
|
||||
There is **no automated way** to transfer a Supabase project from Lovable Cloud to your own Supabase account.
|
||||
|
||||
However, you can manually clone your project backend and migrate your data following Lovable’s official guide: [Self-Hosting Guide (Lovable Docs)](https://docs.lovable.dev/tips-tricks/self-hosting)
|
||||
|
||||
This process allows you to create a new Supabase project under your own account and connect it independently.
|
||||
|
||||
<Admonition type="note">
|
||||
|
||||
There are certain limitations described in Lovable’s documentation, so review the guide carefully before proceeding.
|
||||
|
||||
</Admonition>
|
||||
|
||||
## How to prevent
|
||||
|
||||
If you want direct access to your Supabase project from the start, make sure to:
|
||||
|
||||
- Avoid enabling Lovable Cloud if you plan to manage your Supabase project independently.
|
||||
- Create your project directly from the [Supabase Dashboard](/dashboard) and then **manually connect your Lovable project to your Supabase project**, or **start your Lovable project already connected** to your own Supabase project from the beginning.
|
||||
|
||||
## Additional resources
|
||||
|
||||
For more information, read [the Lovable Cloud FAQ](https://docs.lovable.dev/features/cloud#faq)
|
||||
|
||||
## Frequently asked questions
|
||||
|
||||
<Accordion
|
||||
type="default"
|
||||
openBehaviour="multiple"
|
||||
chevronAlign="right"
|
||||
justified
|
||||
size="medium"
|
||||
className="text-foreground-light mt-8 mb-6"
|
||||
>
|
||||
<div className="border-b mt-3 pb-3">
|
||||
<AccordionItem
|
||||
header="Can I get access to the Supabase SQL editor when using Lovable Cloud?"
|
||||
id="sql-editor-access"
|
||||
>
|
||||
|
||||
No. Projects running on **Lovable Cloud** use a managed Supabase backend that doesn't provide direct SQL editor access through [supabase.com/dashboard](/dashboard).
|
||||
|
||||
</AccordionItem>
|
||||
|
||||
</div>
|
||||
|
||||
<div className="border-b mt-3 pb-3">
|
||||
<AccordionItem
|
||||
header="Why doesn't my Supabase project appear on my dashboard?"
|
||||
id="project-not-showing"
|
||||
>
|
||||
|
||||
Lovable Cloud projects are owned and managed by **Lovable**, not by your personal Supabase account. They won't show up on your dashboard.
|
||||
|
||||
</AccordionItem>
|
||||
|
||||
</div>
|
||||
|
||||
<div className="border-b mt-3 pb-3">
|
||||
<AccordionItem
|
||||
header="Can I disconnect my project from Lovable Cloud and connect it to my own Supabase account?"
|
||||
id="disconnect-project"
|
||||
>
|
||||
|
||||
Once Lovable Cloud is enabled for a project, it **cannot be disconnected or switched** to an external Supabase connection.
|
||||
|
||||
However, you can **create a new Supabase project under your own account** and migrate your data by following Lovable's [Project Migration Guide](https://docs.lovable.dev/tips-tricks/self-hosting).
|
||||
|
||||
</AccordionItem>
|
||||
|
||||
</div>
|
||||
|
||||
<div className="border-b mt-3 pb-3">
|
||||
<AccordionItem
|
||||
header="I can't get my database URL to connect from an external tool (like BI tools or Postgres connectors)."
|
||||
id="database-url"
|
||||
>
|
||||
|
||||
External connections are **not supported** when your project runs on Lovable Cloud.
|
||||
|
||||
</AccordionItem>
|
||||
|
||||
</div>
|
||||
|
||||
<div className="border-b mt-3 pb-3">
|
||||
<AccordionItem
|
||||
header="I can't get my service role key to integrate an external service (like n8n or Make.com)."
|
||||
id="service-role-key"
|
||||
>
|
||||
|
||||
Service role and API keys are **not accessible** for Lovable Cloud–managed projects.
|
||||
|
||||
If you need to integrate with external automation or API-based tools, you'll need to **create and manage your own Supabase project**, then connect Lovable to it directly.
|
||||
|
||||
</AccordionItem>
|
||||
|
||||
</div>
|
||||
|
||||
</Accordion>
|
||||
@@ -0,0 +1,145 @@
|
||||
---
|
||||
title = "Identifying Lovable backend: Lovable Cloud or Supabase"
|
||||
topics = [
|
||||
"ai",
|
||||
]
|
||||
keywords = [
|
||||
"lovable",
|
||||
"lovable cloud"
|
||||
]
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
When you create a project in **Lovable**, your app’s backend can be connected to one of two options:
|
||||
|
||||
- **Lovable Cloud** — The backend (Supabase instance) is managed entirely by **Lovable**.
|
||||
- **Your own Supabase project** — The backend is a Supabase project you created and manage directly in your [Supabase Dashboard](/dashboard).
|
||||
|
||||
Knowing which backend your project uses helps you understand where your database, API keys, and configuration are managed.
|
||||
|
||||
## How to identify your backend
|
||||
|
||||
In the Lovable interface, click the **Cloud icon** on the top bar of your project editor. This section shows which backend your project is currently connected to.
|
||||
|
||||
|
||||
|
||||
<Admonition type="note">
|
||||
|
||||
The Cloud icon appears for all projects, regardless of which backend type you're using. Click it to see your actual backend configuration.
|
||||
|
||||
</Admonition>
|
||||
|
||||
Once you open the Cloud settings, you see one of two interfaces depending on your backend type:
|
||||
|
||||
### Lovable Cloud backend
|
||||
|
||||
If the page shows a menu and screens to manage your Database tables, and Users from within Lovable (similar to the screenshot below), then your backend is managed by **Lovable Cloud**.
|
||||
|
||||
|
||||
|
||||
Your Supabase instance in this case is **owned and managed by Lovable**, not by your personal Supabase account.
|
||||
You won’t see this project in your Supabase Dashboard, and you won’t have access to service role keys or direct database URLs.
|
||||
|
||||
### Connected Supabase backend
|
||||
|
||||
If the page displays the Supabase icon, your Supabase project name, and some links that direct you to the Supabase Dashboard (similar to the screenshot below), then your Lovable project is connected to a **Supabase project you manage directly**.
|
||||
|
||||
|
||||
|
||||
## Summary
|
||||
|
||||
| Backend Type | Managed By | Appears in Supabase Dashboard | Service Role / DB Access |
|
||||
| ------------------------ | ---------- | ----------------------------- | ------------------------ |
|
||||
| **Lovable Cloud** | Lovable | ❌ No | ❌ No |
|
||||
| **Own Supabase Project** | You | ✅ Yes | ✅ Yes |
|
||||
|
||||
## Frequently asked questions
|
||||
|
||||
<Accordion
|
||||
type="default"
|
||||
openBehaviour="multiple"
|
||||
chevronAlign="right"
|
||||
justified
|
||||
size="medium"
|
||||
className="text-foreground-light mt-8 mb-6"
|
||||
>
|
||||
<div className="border-b mt-3 pb-3">
|
||||
<AccordionItem
|
||||
header="Does this affect where my app is hosted?"
|
||||
id="app-hosting"
|
||||
>
|
||||
|
||||
No. Lovable Cloud only affects your **backend connection** (database and APIs), not your app hosting or frontend.
|
||||
|
||||
</AccordionItem>
|
||||
|
||||
</div>
|
||||
|
||||
<div className="border-b mt-3 pb-3">
|
||||
<AccordionItem
|
||||
header="Can I access my database URL or API keys if I'm on Lovable Cloud?"
|
||||
id="database-api-access"
|
||||
>
|
||||
|
||||
No. Lovable Cloud backend is managed entirely by Lovable, and connection credentials are not exposed.
|
||||
|
||||
</AccordionItem>
|
||||
|
||||
</div>
|
||||
|
||||
<div className="border-b mt-3 pb-3">
|
||||
<AccordionItem
|
||||
header="Can I switch from Lovable Cloud to my own Supabase backend?"
|
||||
id="switch-backend"
|
||||
>
|
||||
|
||||
There's no automated way to transfer your backend. You can create a new Supabase project and connect your Lovable app to it manually.
|
||||
|
||||
See [Lovable's Project Migration Guide](https://docs.lovable.dev/tips-tricks/self-hosting) for detailed steps.
|
||||
|
||||
</AccordionItem>
|
||||
|
||||
</div>
|
||||
</Accordion>
|
||||
|
||||
## Lovable Cloud – specific questions
|
||||
|
||||
<Accordion
|
||||
type="default"
|
||||
openBehaviour="multiple"
|
||||
chevronAlign="right"
|
||||
justified
|
||||
size="medium"
|
||||
className="text-foreground-light mt-8 mb-6"
|
||||
>
|
||||
<div className="border-b mt-3 pb-3">
|
||||
<AccordionItem
|
||||
header="My project uses Lovable Cloud, can I move it to Supabase?"
|
||||
id="move-to-supabase"
|
||||
>
|
||||
|
||||
There's no automated way to transfer your backend from Lovable Cloud to your own Supabase account.
|
||||
|
||||
You can create a new Supabase project and migrate your data manually.
|
||||
|
||||
See [Can't Access Your Supabase Project When Using Lovable Cloud](/docs/guides/troubleshooting/cant-access-supabase-project-lovable-cloud) for more details.
|
||||
|
||||
</AccordionItem>
|
||||
|
||||
</div>
|
||||
|
||||
<div className="border-b mt-3 pb-3">
|
||||
<AccordionItem
|
||||
header="My project uses Lovable Cloud, but I can't see my Supabase project."
|
||||
id="cant-see-project"
|
||||
>
|
||||
|
||||
That's expected — Lovable Cloud backend is managed by Lovable and doesn't appear in your Supabase Dashboard.
|
||||
|
||||
Learn more in [Can't Access Your Supabase Project When Using Lovable Cloud](/docs/guides/troubleshooting/cant-access-supabase-project-lovable-cloud).
|
||||
|
||||
</AccordionItem>
|
||||
|
||||
</div>
|
||||
</Accordion>
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 81 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 70 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 52 KiB |
@@ -125,6 +125,8 @@ may_uppercase = [
|
||||
"LlamaIndex",
|
||||
"Llamafile",
|
||||
"Logs Explorer",
|
||||
"Lovable",
|
||||
"Lovable Cloud",
|
||||
"Magic Link",
|
||||
"Mailpit",
|
||||
"Management API",
|
||||
|
||||
@@ -224,6 +224,8 @@ allow_list = [
|
||||
"LlamaIndex",
|
||||
"Llamafile",
|
||||
"Logflare",
|
||||
"Lovable",
|
||||
"Lovable Cloud",
|
||||
"Lua",
|
||||
"Mailgun",
|
||||
"Mailpit",
|
||||
|
||||
Reference in new issue
Block a user