Insufficient privileges while connecting to supabase about electric

[alco]

@p7gg Thanks for the video!

So you run both Supabase and Electric as Docker containers, but they both end up on separate virtual networks. Docker creates an isolated network for each container, or for a set of containers if you're using docker compose. Containers on the same network can see each other but they cannot see containers on other networks.

In your case, Supabase's localhost, or 127.0.0.1, is different from Electric's localhost. You can think of them both as if they're running on separate machines.

If Supabase exposes its port to the host OS, your Electric should be able to connect to it if you add this key under your electric service definition in the compose file:

extra_hosts:
  - "host.docker.internal:host-gateway"

and replace 127.0.0.1 with host.docker.internal in DATABASE_URL.

---

If you have further questions, please start a new thread in the #help-and-support channel in our Discord community or a new GitHub discussion here.

[p7gg]

same problem

[alco]

Hey @masylum and @p7gg. You must have followed an older version of the guide. The ELECTRIC_INBOUND_MODE variable has since been renamed to ELECTRIC_WRITE_TO_PG_MODE. See the up-to-date guide here.

[p7gg]

@alco I believe i had the right variable, although i had the same error.
I'll try and record a video, since I was running everything locally: supabase and electricsql

[p7gg]

Sorry for the delay, got slumped with work, @alco .
Realized that it wasn't the same error, but still getting one...
Might be because of my lack of docker knowledge tho. any pointers is greatly appreciated

issue-electricsql.mp4

[masylum]

Hey @masylum and @p7gg. You must have followed an older version of the guide. The ELECTRIC_INBOUND_MODE variable has since been renamed to ELECTRIC_WRITE_TO_PG_MODE. See the up-to-date guide here.

This fixed the issue. Lesson learned, reload the tabs once in a while! Thanks for the support and this awesome project

[p7gg]

@alco thank you very much.
Ran into another error, but I'll just reach out to the discord community, if I don't get a solution i'll post in the discussions for sure.