Supabase connection issue

Thanks for your response. But can you guide me how to access the backend url? As there is cloud menu in the loveable. I opened it and when i visit my database it says unable to connect

The URL you shared (designerv3-1-65488.lovable.app) is the frontend application, not the backend. Lovable hosts the UI, but it still needs a separate backend/API service to handle authentication and database access. That backend has its own URL, which is what the frontend calls in the background. The "unable to connect" message indicates that no backend service is running or connected yet, which is why the app is timing out and showing the 522 error.

Hi @Jehanzaib Javed ! I will help you. Both the Lovable preview and published domains returning a 522 error indicates that the backend (origin server) is not reachable. A 522 is a Cloudflare timeout, not a true CORS issue, and usually means the API server is down, sleeping, misconfigured, or blocked. First, verify that your backend URL opens directly in a browser and responds correctly. Then ensure the backend is publicly accessible over HTTPS and has proper CORS headers allowing the Lovable domains. Once the backend is reachable, the CORS-related messages should resolve automatically.

As there is cloud menu in the loveable. I opened it and when i visit my database it says unable to connect

there?

Thanks for your response. But can you guide me how to access the backend url?

browser and responds correctly. Then ensure the backend is publicly accessible over HTTPS and has proper CORS headers allowing the Lovable domains. Once the backend is reachable, the CORS-related messages should resolve automatically.

You don't access the backend URL from the Lovable cloud menu. The cloud section only manages services like the database and doesn't expose the backend endpoint directly. The backend URL is the API URL you configured in your project (usually from your backend hosting provider), and it should be accessible directly in a browser. The “unable to connect” message in the database view usually means the backend service is not running, sleeping, or misconfigured, which is why both preview and published domains are failing.

You don't access the backend URL from the Lovable cloud menu. The cloud section only manages services like the database and doesn't expose the backend endpoint directly. The backend URL is the API URL you configured in your project (usually from your backend hosting provider), and it should be accessible directly in a browser. The "unable to connect" message in the database view usually means the backend service is not running, sleeping, or misconfigured, which is why both preview and published domains are failing.

Is the project you are working on given to you by your client?

my site is currently deployed on the loveable and the domain i had is also generated via loveable:"https://designerv3-1-65488.lovable.app/auth"

yes the project is given to me by my client

That's totally understandable. Lovable itself doesn't automatically run or restart a backend — the backend must be hosted separately (for example on Render, Railway, Fly.io, or another server). To "restart" it, you need to log into the platform where the backend is hosted and start or redeploy the service there. If no backend has been set up yet, we'll need to create one and connect it to Lovable before the app can work properly.

yes the project is given to me by my client and i don't think so we have hosted the backend seperately

freelance.com ?

and i don't think so we have hosted the backend seperately

The Real Issue The backend exists and is configured - but it's not responding. Let me verify the current state: Read database This confirms exactly what we suspected: Confirmed Diagnosis Component Status Evidence Frontend Working App loads, React runs Backend URL Correct jixijhxgjpmducligaky.supabase.co API Keys Configured In .env and client Supabase Client Proper Using @supabase/supabase-js Database Connection TIMING OUT 544 error just now Auth Service TIMING OUT 522 errors you see Storage TIMING OUT Bucket loading fails What This Means The backend is connected but the infrastructure is unresponsive. This is NOT: A missing backend connection A CORS configuration issue A code problem

in job site?

Hi @Jehanzaib Javed ! I will help you. Both the Lovable preview and published domains returning a 522 error indicates that the backend (origin server) is not reachable. A 522 is a Cloudflare timeout, not a true CORS issue, and usually means the API server is down, sleeping, misconfigured, or blocked. First, verify that your backend URL opens directly in a browser and responds correctly. Then ensure the backend is publicly accessible over HTTPS and has proper CORS headers allowing the Lovable domains. Once the backend is reachable, the CORS-related messages should resolve automatically.

thank you soo much. but the issue is still there that I don't have access to the supabbase directly. As loveable is somewhat a closed env so we cannot edit everything directly just like we do in custom coding

The URL you shared (designerv3-1-65488.lovable.app) is the frontend application, not the backend. Lovable hosts the UI, but it still needs a separate backend/API service to handle authentication and database access. That backend has its own URL, which is what the frontend calls in the background. The “unable to connect” message indicates that no backend service is running or connected yet, which is why the app is timing out and showing the 522 error.

in job site?

You don't access the backend URL from the Lovable cloud menu. The cloud section only manages services like the database and doesn't expose the backend endpoint directly. The backend URL is the API URL you configured in your project (usually from your backend hosting provider), and it should be accessible directly in a browser. The “unable to connect” message in the database view usually means the backend service is not running, sleeping, or misconfigured, which is why both preview and published domains are failing.

hmm I understood the issue but I don't know how to restart the backend or something so it start working again or something

Thanks for your response. But can you guide me how to access the backend url? As there is cloud menu in the loveable. I opened it and when i visit my database it says unable to connect

Can you invite me?

That’s totally understandable. Lovable itself doesn’t automatically run or restart a backend — the backend must be hosted separately (for example on Render, Railway, Fly.io, or another server). To “restart” it, you need to log into the platform where the backend is hosted and start or redeploy the service there. If no backend has been set up yet, we’ll need to create one and connect it to Lovable before the app can work properly.

nope. freelance

okay?

oh, I know.

thank you soo much, but

freelance.com ?

thank you soo much. but the issue is still there that I don't have access to the supabase directly. As loveable is somewhat a closed env so we cannot edit everything directly just like we do in custom coding

nope. freelance

Thanks for confirming — that makes sense. Since you're using Supabase, the backend is hosted, and the timeouts indicate an issue on Supabase's infrastructure side (for example the project being paused, overloaded, or temporarily unavailable). The next step is to log into the Supabase dashboard, check whether the project is paused, and resume it if needed; restarting the database from there usually resolves this. If everything looks active, checking Supabase's status page or redeploying/restarting the project services from the dashboard would be the correct action.

oh, I know.

Hello, I have no idea why but I cannot access my build. Does anyone know where you can go to get help on that?

no sorry. we have a direct contract with the client and we are working remotely for him

I wanna work with you.

This is the informaiton I got * Issue: Backend/database timing out (544 errors) • Duration: Multiple hours • Impact: Cannot log in or access any data

hmm can you dm me?

Ofc