Supabase & Your Network: IPv4 and IPv6 compatibility #27034
TheOtherBrian1
announced in
Troubleshooting
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Network Compatibility with your Supabase Database
The internet uses a system called the Internet Protocol (IP) to route communication between devices. There are two main versions:
Supabase and IPv6:
All Supabase databases provide a direct connection string that maps to an IPv6 address.
Working with IPv6 Incompatible Hosts:
Here are your options if your server platform doesn't support IPv6:
Checking IPv6 Support:
The majority of services are IPv6 compatible. However, there are a few prominent ones that only accept IPv4 connections:
If you're still unsure if your network supports IPv6, you can run this cURL command on your deployment server:
If the command returns an IPv6 address, the network is IPv6 compatible.
Finding your Database's IP Address:
To determine your current IP address, you can use an IP address lookup website or the terminal command:
This command queries the domain name servers to find the IP address of the given hostname.
Example IPv6 Address:
2a05:d014:1c06:5f0c:d7a9:8616:bee2:30df
Identifying your connections:
The pooler and direct connection strings can be found in the database settings:
# Example connection string postgresql://postgres:[YOUR-PASSWORD]@db.ajrbwkcuthywfihaarmflo.supabase.co:5432/postgres
Supavisor in transaction mode (port 6543)
# Example transaction string postgresql://postgres.ajrbwkcuthywddfihrmflo:[YOUR-PASSWORD]@aws-0-us-east-1.pooler.supabase.com:6543/postgres
Supavisor in session mode (port 5432)
# Example session string postgresql://postgres.ajrbwkcuthywfddihrmflo:[YOUR-PASSWORD]@aws-0-us-east-1.pooler.supabase.com:5432/postgres
Beta Was this translation helpful? Give feedback.
All reactions