Skip to content
Runsite Platform

Connecting

Every Redis instance exposes two endpoints. Use the one that matches where you’re connecting from.

Internal vs external

Section titled “Internal vs external”
URLFormatWhen to use it
Internalredis://From other Runsite services in the same project. Stays on the private network — lowest latency, no public exposure.
Externalrediss:// (TLS)From your laptop, third-party tools, or anything running outside Runsite. Encrypted in transit.

Both URLs are standard Redis connection strings. You’ll find them on the instance’s Overview tab — copy them directly, don’t construct them by hand. The username is empty (Redis only uses the password).

A real internal URL looks like:

redis://:Xy9Pq~rN2fGHaUpQbZ~mLk7s@red-vakdj328fj02kdnv-a:6379

A real external URL looks like:

rediss://:Xy9Pq~rN2fGHaUpQbZ~mLk7s@red-vakdj328fj02kdnv-a.eu-central-redis.runsite.app

Notice:

  • The internal host (red-...-a) is short and only resolves inside Runsite. Default port :6379 is explicit.
  • The external host adds the region and base domain (eu-central-redis.runsite.app). Port is implicit — TLS clients use the standard Redis port automatically.
  • The external URL uses rediss:// (with two s) — that’s the TLS scheme. Don’t drop the second s or your client will try plain TCP.

From a Runsite Web Service

Section titled “From a Runsite Web Service”

Inside another Runsite service in the same project, use the internal URL. Add it as an environment variable in the service’s Environment tab:

Terminal window
REDIS_URL=redis://:Xy9Pq~rN2fGHaUpQbZ~mLk7s@red-vakdj328fj02kdnv-a:6379

Most Redis clients (ioredis, redis-py, go-redis, node-redis) accept this URL directly.

From your laptop

Section titled “From your laptop”

Use the external URL with redis-cli:

Terminal window
redis-cli -u "rediss://:Xy9Pq~rN2fGHaUpQbZ~mLk7s@red-vakdj328fj02kdnv-a.eu-central-redis.runsite.app"

Or paste it into your client (RedisInsight, Medis) — they all accept the standard URL.

Credentials

Section titled “Credentials”

The password is shown once, when you create the instance. After that the dashboard masks it.

There is no password reset. If you lose the password, you’ll need to delete the instance and create a new one. Save it in a password manager or in your service’s environment variables right away.