supabase start ignores api port and uses default instead

[alita-moore]

Describe the bug
I have the port configured to 64321 for the api but the system is starting kong on 54321

To Reproduce
Steps to reproduce the behavior:

1. set the port to 64321 in the config.toml
2. start it
3. notice it's not on that port

Expected behavior
it should be hosting the kong server on port 64321

System information

• Version of OS: ubuntu 24.04
• Version of CLI: 2.67.1
• Version of Docker: Docker version 29.1.3, build f52814d
• Versions of services:
  SERVICE IMAGE | LOCAL | LINKED
  ------------------------|------------------------|--------
  supabase/postgres | 17.6.1.064 | -
  supabase/gotrue | v2.184.0 | -
  postgrest/postgrest | v14.1 | -
  supabase/realtime | v2.68.4 | -
  supabase/storage-api | v1.33.0 | -
  supabase/edge-runtime | v1.69.28 | -
  supabase/studio | 2025.12.09-sha-434634f | -
  supabase/postgres-meta | v0.95.1 | -
  supabase/logflare | 1.27.0 | -
  supabase/supavisor | 2.7.4 | -

[alita-moore]

update: it seems that this only happens when you're running on a fresh system that's never started the supabase project before, but if you supabase stop then supabase start it begins to behave correctly 🙃