The Redis connection name [horizon] is reserved for internal use

[robbiekibler]

Horizon Version

5.35.0

Laravel Version

12.33

PHP Version

8.4

Redis Driver

PhpRedis

Redis Version

7.0.0

Database Driver & Version

No response

Description

Installing v5.35.0 of Horizon received this error

Steps To Reproduce

Running composer update

[gerardnll]

+1 here also. Seems like a bug with PR #1615.

On the horizon.php config file I'm using the 'horizon', database configured in database.php. That's the only place where I use it.

[nielspeen]

Same. Horizon adds the database.redis.horizon entry to the configuration itself, then complains about it existing.

[francoism90]

Same issue over here. I also don't understand the PR, because it's already documentated.

@nielspeen It seems so indeed, I also don't have any horizon reference in config/database.php.

[nielspeen]

@francoism90 Horizon puts it in the configuration. The configuration then gets cached (usually - on a production machine). Then on the next load, Horizon is confronted with the cached version of its own configuration.

[tudorr89]

Same issue here, any fix?

[carvemerson]

I’ve been using a configuration named horizon for years without issues, but now I'm facing the same issue. Not sure how the horizon key name can causes conflicts but....

Two quick fixes you can try:

✅ Option 1 — Downgrade

Downgrade to v5.34, which still works fine with the horizon key.

✅ Option 2 — Rename the Redis Connection

Rename the horizon Redis connection in database.php and update horizon.php accordingly.

config/database.php

// ❌ Before
'redis' => [
    'horizon' => [
        'host' => env('CRM_REDIS_SERVICE_HOST'),
        'port' => env('CRM_REDIS_SERVICE_PORT'),
    ],
],

// ✅ After
'redis' => [
    'horizon_data' => [
        'host' => env('CRM_REDIS_SERVICE_HOST'),
        'port' => env('CRM_REDIS_SERVICE_PORT'),
    ],
],

config/horizon.php

// ❌ Before
'use' => 'horizon',

// ✅ After
'use' => 'horizon_data',

the horizon_data is just an example, it can be any name different of horizon.

[nielspeen]

@carvemerson while your change is certainly necessary, it does not fix the problem for those of us who cache the configuration on production.

[carvemerson]

Yeah, for now I just frozen the version at v5.34, while think in a solution.

[carvemerson]

Fixed on v5.35.2, we can unfreeze the version :)

[gerardnll]

Fixed on v5.34.2, we can unfreeze the version :)

5.35.2