# 50007: Connection key could not be issued

Identifier: `connection_key_unavailable`



The connection was established without a connection key, so it cannot later be resumed and cannot be published on behalf of. This is caused by a fault on the Ably side rather than by the client.

## What you should do

Nothing in the client needs to change, and there is no need to handle the error specially: publishing and subscribing on the connection work normally. Closing and reconnecting gets a new connection, which will have a key once the fault is resolved.

The effect to be aware of is that this connection cannot be continued if it drops, so a client that reconnects starts a fresh connection with a new connection ID, and presence members re-enter under that new ID. A server publishing on behalf of the connection has no key to name it with.

Ably is notified whenever this occurs, so it is already being investigated.

## Why it happens

Each connection key is signed when it is issued, so that it can later be verified as naming the connection it claims to. When that signature cannot be produced, the connection is allowed through without a key rather than being refused, so that messaging keeps working.

## What you'll see

The error is reported with code 50007 and HTTP status 500, with the message `Unable to issue a connection key`. It arrives in the error field of the response that confirms the connection, which reaches the connected state with no connection key in its connection details.