Troubleshooting
Most sync problems come down to the shared database, the Redis connection, or a mismatch between servers. Work down this list.
| Symptom | Likely cause | Fix |
|---|---|---|
| A server fails to start after you enable Redis | redis.enabled is true but Redis cannot be reached | Check that Redis is running and that the uri is right, including any password. ProtonAuctions reports a Redis connection error when it cannot connect at startup. |
| Listings never appear on the other servers | The servers are not sharing one database | Redis only signals changes, it does not move data. Every server must share one MySQL or PostgreSQL Database. SQLite gives each server its own file, so there is nothing to share. |
| Some servers sync and others do not | A server is on a different uri or channel | Make the uri and channel identical on every server. A server on another channel hears nothing. |
| Nothing syncs, but there are no errors | Redis was never enabled, or a server was not restarted | Set redis.enabled to true on every server and restart each one. The redis block is read only at startup. |
| Sync stopped after a Redis upgrade or move | Redis is older than 6, or the address changed | ProtonAuctions needs Redis 6 or newer, because it publishes and subscribes on one connection. Confirm the version and that the uri still points at the right host. |
Redis is only the live-updates layer. If listings are wrong or missing rather than just slow to appear, the problem is almost always the shared database, not Redis. Start there, then check Cross-Server Sync.