Connecting to Arctickey

Connection Details#

After creating an instance, you'll get:

FieldExample
Hosteu.arctickey.com
Port6379 (varies per instance)
Passwordak_xxxxxxxxxxxx
TLSRequired

Connection String Format#

TEXT
rediss://:PASSWORD@HOST:PORT

Note: rediss:// (with double 's') indicates TLS/SSL. Regular redis:// won't work.

Example:

TEXT
rediss://:ak_abc123xyz@eu.arctickey.com:6379

TLS/SSL Configuration#

All Arctickey connections require TLS. Most clients support this out of the box:

Node.js (ioredis)#

JavaScript
const redis = new Redis({ host: 'eu.arctickey.com', port: 6379, password: 'your-password', tls: { rejectUnauthorized: false, // Required for self-signed certs }, });

Python (redis-py)#

Python
r = redis.Redis( host='eu.arctickey.com', port=6379, password='your-password', ssl=True, ssl_cert_reqs=None, # Required for self-signed certs )

redis-cli#

Terminal
redis-cli --tls -h eu.arctickey.com -p 6379 -a YOUR_PASSWORD

GUI Clients#

For TablePlus, RedisInsight, Medis, etc.:

  1. Enable SSL/TLS in connection settings
  2. Disable Verify Certificate (we use self-signed certs)
  3. Enter host, port, and password

Environment Variables#

We recommend storing credentials in environment variables:

Environment
# .env ARCTICKEY_HOST=eu.arctickey.com ARCTICKEY_PORT=6379 ARCTICKEY_PASSWORD=ak_your_password_here # Or as a URL ARCTICKEY_URL=rediss://:ak_your_password@eu.arctickey.com:6379

Troubleshooting#

"Connection refused" or timeout#

  1. Check your firewall allows outbound connections on the port
  2. Verify the host and port are correct
  3. Ensure you're using rediss:// (TLS), not redis://

"Authentication failed"#

  1. Check the password is correct
  2. Ensure no extra whitespace in the password
  3. Try regenerating credentials from the dashboard

"SSL/TLS handshake failed"#

  1. Ensure your client supports TLS
  2. Disable certificate verification (self-signed certs)
  3. Check you're using the TLS port, not a non-TLS one

Connection drops#

  1. Implement reconnection logic in your client
  2. Use connection pooling for multiple concurrent operations
  3. Check your instance hasn't been put to sleep (Free tier)