Connect your application

Allow your application's address

Add the public outbound IP used by your application server. Your laptop and your application can have different addresses. For a hosting platform with changing outbound addresses, confirm its supported connectivity options before allowing a broad network range.

Use TLS and verify the certificate

Your connection details include the endpoint, port and CA certificate. Enable certificate verification in your client. Database endpoints use a dedicated hostname under db.staticweb.space. These DNS-only endpoints connect directly to your database server; the web portal’s Cloudflare CDN does not proxy database TCP traffic. Keep credentials in a secret store or server-side environment variables. The examples below contain placeholders, not real credentials.

psql "host=YOUR_ENDPOINT port=5432 dbname=app user=app_user sslmode=verify-full sslrootcert=./ca.pem"

mysql --host=YOUR_ENDPOINT --port=3306 --user=app_user --password \
  --ssl-mode=VERIFY_IDENTITY --ssl-ca=./ca.pem

If the connection fails

Check the deployment is ready, the source IP is allowed, the database name and password are correct, and the client uses the supplied hostname and CA. A timeout commonly indicates a network rule; an authentication error commonly indicates the user, password or permissions.

Use a connection pool

Your plan limits concurrent connections. Reuse connections through your framework's pool, and budget for all application replicas, background jobs and administrative tools together.