SSH tunnel / private DB

STYD Cloud cannot reach a database that only exists on localhost or on a private network, and it has no SSH tunnel option. This page explains what works instead.

The connection form connects directly to the server address and port you enter. Addresses on localhost and on private networks (for example 10.x, 172.16–31.x, 192.168.x) are refused, and there is no tunnel, VPN or jump-host setting.

How STYD connects

STYD connects from the internet, from two fixed addresses: 109.123.235.222 (IPv4) and 2407:3640:2324:5796::1 (IPv6). It only runs read queries. For that to work, your database must be reachable at a public address.

If your database is on a private network

  • Give it a public address and limit your firewall or security group to the two addresses above, so only STYD can connect.
  • Or point STYD at a read replica that is exposed the same way, and keep the main database private.
  • Or use a custom, private installation, which can reach a database inside your own network: see Custom AI.
If the address goes through Cloudflare’s proxy, it cannot carry database connections. Use a DNS-only name, or the server’s own address.

Security cautions

Never open a database to the whole internet. Allow only the two STYD addresses, always use a read-only database user, and test the connection before relying on it. If you are unsure, ask your database or network administrator.