Migrations failing if enum types exist in different schemas

[Stealthwriter]

I'm getting this error while I start the server, what could be the issue? and how to fix it please?

{"level":"error","time":"2025-09-17T07:50:23.364Z","pid":1,"hostname":"b2a0c7bbbffa","err":{"type":"Error","message":"Migration failed. Reason: An error occurred running 'prices'. Rolled back this migration. No further migrations were run. Reason: type \"stripe.pricing_type\" does not exist","stack":"Error: Migration failed. Reason: An error occurred running 'prices'. Rolled back this migration. No further migrations were run. Reason: type \"stripe.pricing_type\" does not exist\n at /app/node_modules/.pnpm/pg-node-migrations@0.0.8/node_modules/pg-node-migrations/dist/migrate.js:108:27\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async /app/node_modules/.pnpm/pg-node-migrations@0.0.8/node_modules/pg-node-migrations/dist/with-lock.js:25:28\n at async connectAndMigrate (/app/packages/sync-engine/dist/index.cjs:2000:5)\n at async runMigrations (/app/packages/sync-engine/dist/index.cjs:2018:5)","cause":"An error occurred running 'prices'. Rolled back this migration. No further m

[kevcodez]

There is no such type in the sync-engine - could you post the code you're using that triggers the error? nvm wrong lookup

[Stealthwriter]

Im using the docker command from the docs, I used all default envs

…

On Wed, 17 Sep 2025, 12:30 PM Kevin Grüneberg ***@***.***> wrote: *kevcodez* left a comment (supabase/stripe-sync-engine#191) <#191 (comment)> There is no such type in the sync-engine - could you post the code you're using that triggers the error? — Reply to this email directly, view it on GitHub <#191 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6HMVXDYY5TXR7Y3UZNESNL3TELZJAVCNFSM6AAAAACGXLEQF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGMBRHEYTINBVGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[kevcodez]

Just launched a Postgres 15 instance via Docker

services:
  db:
    container_name: stripe-db
    image: supabase/postgres:15.1.1.4
    command: postgres -c config_file=/etc/postgresql/postgresql.conf
    restart: unless-stopped
    ports:
      - 55432:5432
    environment:
      POSTGRES_PASSWORD: postgres

and ran

 docker run -it \
  -e DATABASE_URL="postgres://postgres:postgres@docker.for.mac.localhost:55432/postgres" \
  -e STRIPE_SECRET_KEY=sk_test_... \
  -e STRIPE_WEBHOOK_SECRET=... \
  -e API_KEY="my-secret" \
  -p 8011:8080 \
  supabase/stripe-sync-engine:latest

Migrated successfully - do you have a reproducible example to reliably reproduce the error?

Did you perhaps already have some stripe schema prior to running the migrations?

[Stealthwriter]

I'm not using the open source supabase docker, I'm using the live production one from supabase directly.

could that be the case?

[Stealthwriter]

I'm using this URL postgresql://postgres:[YOUR-PASSWORD]@db.vqdtifewupwhdypyiskf.supabase.co:5432/postgres

[Stealthwriter]

yes I created a stripe schema manually but no tables in it, let me remove it and try again

[Stealthwriter]

still same issue, event if I delete schema stripe

[kevcodez]

I couldn't find any project with the ref vqdtifewupwhdypyiskf - is that your actual project reference? Wanted to check Postgres version and whether you're using OrioleDB

[Stealthwriter]

sorry I changed a letter by mistake while I was typing it here.

its actually -redacted-

[kevcodez]

Hm - will have to test later again against a Supabase instance - it should work with that Postgres version

The pricing type should also be created here:

stripe-sync-engine/packages/sync-engine/src/database/migrations/0003_prices.sql

Line 1 in f2d530a

DO $$

Could you try changing the port to 6543 instead of 5432?

Will test myself later today or tomorrow to try and repro

[Stealthwriter]

I created a new project which has the latest version, but now I get this error:

dotenv@17.2.2] injecting env (0) from .env -- tip: ⚙️ enable debug logging with { debug: true }
{"level":"error","time":"2025-09-17T09:26:16.199Z","pid":1,"hostname":"9420a37fbde0","err":{"type":"Error","message":"connect ENETUNREACH 2a05:d014:1c06:5f09:ae7a:5be:e5db:1116:5432 - Local (:::0)","stack":"Error: connect ENETUNREACH 2a05:d014:1c06:5f09:ae7a:5be:e5db:1116:5432 - Local (:::0)\n at internalConnect (node:net:1110:16)\n at defaultTriggerAsyncIdScope (node:internal/async_hooks:472:18)\n at GetAddrInfoReqWrap.emitLookup [as callback] (node:net:1523:9)\n at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:134:8)","errno":-101,"code":"ENETUNREACH","syscall":"connect","address":"2a05:d014:1c06:5f09:ae7a:5be:e5db:1116","port":5432},"msg":"Error running migrations"}

I think it's because this project doesn't have a dedicated IPV4 addon, is it required?

[Stealthwriter]

yes it worked when I added an IPV4 addon on the new project that runs the latest version of postgres, so you think the issue is the postgres version? mine on the main project is too old?

[kevcodez]

Dedicated IPv4 add-on is only required for direct connections to the database/pgbouncer in a network that doesn't support IPv6.

You can also connect via the shared connection pooler Supavisor instead to not have to get an IPv4 addon

[kevcodez]

mine on the main project is too old?

Will have to test - it should be fine. I tested this on Postgres 12, you're on Postgres 15 with the previously mentioned project, so that's surprising - you can try upgrading your project through your project's infra settings to verify