problems with realtime and websockets

[DaavidGG]

I have self-hosted Supabase with Docker on Oracle Cloud, and when I try to listen for changes in real time, I get the following error.

I have tried removing the RLS policies from the tables, but that does not work either.

This is my Docker Compose configuration for realtime.

realtime:
container_name: realtime-dev.supabase-realtime
image: supabase/realtime
restart: unless-stopped
ports:
- "4000:4000"
networks:
- supabase_network
depends_on:
db:
condition: service_healthy
analytics:
condition: service_healthy
healthcheck:
test:
[
"CMD",
"curl",
"-sSfL",
"--head",
"-o",
"/dev/null",
"-H",
"Authorization: Bearer ${ANON_KEY}",
"http://localhost:4000/api/tenants/realtime-dev/health"
]
timeout: 15s
interval: 15s
retries: 3
environment:
PORT: 4000
DB_HOST: ${POSTGRES_HOST}
DB_PORT: ${POSTGRES_PORT}
DB_USER: supabase_admin
DB_PASSWORD: ${POSTGRES_PASSWORD}
DB_NAME: ${POSTGRES_DB}
DB_AFTER_CONNECT_QUERY: 'SET search_path TO _realtime'
DB_ENC_KEY: supabaserealtime
API_JWT_SECRET: ${JWT_SECRET}
SECRET_KEY_BASE: ${SECRET_KEY_BASE}
ERL_AFLAGS: -proto_dist inet_tcp
DNS_NODES: "''"
RLIMIT_NOFILE: 10000
APP_NAME: realtime
RUN_JANITOR: true
JANITOR_INTERVAL: 60000
LOG_LEVEL: "info"
SEED_SELF_HOST: true
command: >
sh -c "/app/bin/migrate && /app/bin/realtime eval 'Realtime.Release.seeds(Realtime.Repo)' && /app/bin/server"

This is my Kong.yml:

Secure Realtime routes

• name: realtime-v1-ws
  _comment: 'Realtime: /realtime/v1/websocket -> ws://realtime:4000/socket/websocket'
  url: http://realtime:4000/socket/websocket
  routes:
  • name: realtime-v1-ws
    strip_path: true
    paths:
    • /realtime/v1/websocket
      protocols:
    • http
    • https
      plugins:
  • name: cors
    config:
    origins:
    - "*"
    methods:
    - GET
    - POST
    - OPTIONS
    headers:
    - Authorization
    - apikey
    - Content-Type
    - Accept
    - Origin
    credentials: true
    max_age: 3600
  • name: request-transformer
    config:
    add:
    headers:
    - "Connection:Upgrade"
    - "Upgrade:websocket"
    remove:
    querystring:
    - apikey
• name: realtime-v1-rest
  _comment: 'Realtime: /realtime/v1/* -> ws://realtime:4000/socket/*'
  url: http://realtime:4000/api
  protocol: http
  routes:
  • name: realtime-v1-rest
    strip_path: true
    paths:
    • /realtime/v1/api
      plugins:
  • name: cors
  • name: key-auth
    config:
    hide_credentials: false
  • name: acl
    config:
    hide_groups_header: true
    allow:
    - admin
    - anon

Can anyone help me with this problem?

[theunsa]

Hi @DaavidGG

I've had a similar problem and found this workaround (this is by no means the actual solution but maybe it can help you or others as well).

The issue

The problem seems to be that the default url value in the kong config for both realtime-v1-ws route and realtime-v1-rest route does not resolve.

url: http://realtime-dev.supabase-realtime:4000/socket

• so the realtime-dev.supabase-realtime did not resolve on my host where the supabase docker containers (including kong and realtime) were deployed
• but the actual container name that was spinned up during the deployment could be resolved by the services

The workaround

1. Hit a terminal on your host where the supabase services are deployed.

2. Find your realtime service container name

docker ps | grep realtime

• mine was like realtime-dev.$CONTAINER_PREFIX-realtime

3. Edit the kong config

vi /etc/dokploy/compose/batapp2-supabase-g5vso9/files/volumes/api

• find "realtime-v1-ws" and change its url to
  url: http://realtime-dev.$CONTAINER_PREFIX-realtime:4000/socket
• find "realtime-v1-rest" and change its url to
  url: http://realtime-dev.$CONTAINER_PREFIX-realtime:4000/api

4. Find your kong service container name and restart it

docker ps | grep kong

docker restart <YOUR-KONG-CONTAINER>

That did it for me, hope it can help you as well.

[xlmnxp]

Is there any possible way to have it fixed by upstream?