Our records show that the PostgreSQL service has already been fully deleted from your project - only one service remains in that project. The card you're seeing on the canvas is a stale UI artifact. A hard refresh of the page (Ctrl+Shift+R or Cmd+Shift+R) should clear it. If the ghost card persists after refreshing, try opening the project in an incognito/private browser window to confirm it's a local cache issue.

The stale UI artifact of the PostgreSQL service still remains on the project page even after hard refresh. The old PostgreSQL database no longer interferes with data, but the application is currently connected to an empty database instead of the intended Supabase database. The service is running normally, but the database switch is not completed yet.

There are actually two separate issues here:

Problem 1: Ghost card still showing in UI

Railway confirmed the service is already deleted — it's just a UI cache issue. Try:

Hard refresh (Ctrl+Shift+R / Cmd+Shift+R)

Open the project in an incognito/private window

Try a different browser

Problem 2: App connecting to empty database instead of Supabase ← the real issue

Your app still has the old Railway database environment variables. Fix:

Go to your Railway service → Variables tab

Remove/replace all old DATABASE_URL / POSTGRES_* variables

Add your Supabase connection string:

DATABASE_URL=postgresql://[user]:[password]@[host].supabase.co:5432/postgres

Redeploy the service

Bottom line: The ghost card is cosmetic and will resolve itself. The actual blocker is the environment variables still pointing to the old Railway database — update those to Supabase and your app will work correctly.

Hi there,

My app (service: adequate-perfection, project: genuine-bravery) is still connecting to the wrong database. The logs show environment variables are loaded, but it’s connecting to a database without the admins table, which strongly suggests a project-level PostgreSQL add-on/plugin is overriding my Supabase DATABASE_URL.

I’ve already tried:

1. Setting the correct Supabase DATABASE_URL at the service level
2. Redeploying the service multiple times
3. Carefully checking the project page (genuine-bravery) for the Plugins/Database section, but I cannot find any PostgreSQL plugin or add-on to remove/disconnect

Could you please help check if there’s a hidden project-level PostgreSQL plugin and guide me on how to remove it so my service can use the Supabase DATABASE_URL I’ve configured?

Thanks!

You can still connect your app to your supabase database regardless of whether you have a database in your project or not. You can just use supabase's database url, and confirm your app is using it by logging the variable. If you encounter any errors during your database connection, please share the error logs.

The hidden PostgreSQL plugin is likely injecting its own DATABASE_URL at project level, overriding your Supabase one.

Quick workaround — no need to delete anything:

You can still use Supabase regardless. Just add this to your service code temporarily to confirm which URL is actually being used:

console.log("DATABASE_URL:", process.env.DATABASE_URL);

Redeploy and check the logs. If it's showing the Railway Postgres URL instead of Supabase, explicitly set DATABASE_URL in your service Variables tab with your Supabase connection string — this should override the project-level injection.

If you still get connection errors after confirming the correct URL is loaded, share the error logs and we can dig further.