Redis configuration issues

Oct 13, 2025 by pynkocean.com 8 views

Issue Summary

When creating a new booking in a self-hosting environment (local), the booking gets created (with status: accepted) but the v2 api returns 500 after a few minutes and 20 retries. This issue is critical as it affects the functionality of the self-hosted create booking feature, which is essential for users who prefer to host their Cal.com instance locally.

Steps to Reproduce

To reproduce this issue, follow these steps:

Setup self-hosting environment: Set up a self-hosting environment using Docker Compose, which includes Cal API, Redis, and Postgres. You can use the official Docker Compose configuration from the Cal.com GitHub repository.
Create a new booking: Call the POST /v2/bookings endpoint to create a new booking.
Observe the response: After a few minutes, the v2 api will return a 500 error.

Actual Results

The actual results of this issue are:

The v2 api returns a 500 error after a few minutes.
The booking is created with a status of accepted, but the api returns an error.

Expected Results

The expected results of this issue are:

A successful response with a 201 status code, indicating that the booking has been created successfully.

Technical Details

The technical details of this issue are:

Environment: The issue is observed on a Mac M1 computer with Docker Compose (Cal API, Redis, and Postgres) from the official Cal.com GitHub repository.
Logs: The attached logs show the debug output from the Cal API container, which indicates that the booking is created successfully, but the v2 api returns a 500 error after a few minutes.

Redis Involvement

After analyzing the logs, it appears that Redis is involved in this issue. The logs show that the Cal API container is using Redis to store data, but the exact reason for the 500 error is not clear. To further investigate this issue, we need to examine the Redis logs and configuration to determine if there are any issues with the Redis setup.

Possible Causes

Based on the logs and technical details, possible causes of this issue include:

Redis configuration issues: The Redis configuration may be incorrect or incomplete, leading to issues with data storage and retrieval.
Cal API configuration issues: The Cal API configuration may be incorrect or incomplete, leading to issues with data storage and retrieval.
Postgres configuration issues: The Postgres configuration may be incorrect or incomplete, leading to issues with data storage and retrieval.

Debugging Steps

To debug this issue, follow these steps:

Examine Redis logs: Analyze the Redis logs to determine if there are any issues with data storage and retrieval.
Check Cal API configuration: Verify that the Cal API configuration is correct and complete.
Check Postgres configuration: Verify that the Postgres configuration is correct and complete.
Test with a different Redis setup: Test the issue with a different Redis setup to determine if the issue is specific to the current Redis configuration.
Test with a different Cal API setup: Test the issue with a different Cal API setup to determine if the issue is specific to the current Cal API configuration.

Conclusion

Q&A

Q: What is the issue with the self-hosted create booking feature? A: The issue is that the v2 api returns a 500 error after a few minutes when creating a new booking in a self-hosted environment.

Q: What are the symptoms of this issue? A: The symptoms of this issue are:

The booking is created with a status of accepted, but the api returns an error.
The v2 api returns a 500 error after a few minutes.

Q: What are the possible causes of this issue? A: The possible causes of this issue include:

Redis configuration issues: The Redis configuration may be incorrect or incomplete, leading to issues with data storage and retrieval.
Cal API configuration issues: The Cal API configuration may be incorrect or incomplete, leading to issues with data storage and retrieval.
Postgres configuration issues: The Postgres configuration may be incorrect or incomplete, leading to issues with data storage and retrieval.

Q: How can I debug this issue? A: To debug this issue, follow these steps:

Examine Redis logs: Analyze the Redis logs to determine if there are any issues with data storage and retrieval.
Check Cal API configuration: Verify that the Cal API configuration is correct and complete.
Check Postgres configuration: Verify that the Postgres configuration is correct and complete.
Test with a different Redis setup: Test the issue with a different Redis setup to determine if the issue is specific to the current Redis configuration.
Test with a different Cal API setup: Test the issue with a different Cal API setup to determine if the issue is specific to the current Cal API configuration.

Q: What are the technical details of this issue? A: The technical details of this issue are:

Environment: The issue is observed on a Mac M1 computer with Docker Compose (Cal API, Redis, and Postgres) from the official Cal.com GitHub repository.
Logs: The attached logs show the debug output from the Cal API container, which indicates that the booking is created successfully, but the v2 api returns a 500 error after a few minutes.

Q: How can I reproduce this issue? A: To reproduce this issue, follow these steps:

Setup self-hosting environment: Set up a self-hosting environment using Docker Compose, which includes Cal API, Redis, and Postgres. You can use the official Docker Compose configuration from the Cal.com GitHub repository.
Create a new booking: Call the POST /v2/bookings endpoint to create a new booking.
Observe the response: After a few minutes, the v2 api will return a 500 error.

Q: What are the expected results of this issue? A: The expected results of this issue are:

A successful response with a 201 status code, indicating that the booking has been created successfully.

Conclusion

In conclusion, the issue of the v2 api returning a 500 error after a few minutes when creating a new booking in a self-hosted environment is a critical issue that affects the functionality of the self-hosted create booking feature. By following the debugging steps outlined above, we can identify the root cause of the issue and implement a fix to resolve the issue.