6 months ago
I'm trying to deploy the cal.com template following the blog post https://blog.railway.com/p/calendso I have entered the GOOGLEAPICREDENTIALS and hit deploy.
My Cal service keeps failing the health checks and thus the deployment fails. I cannot identify any error in the logs. Am I missing something?
My Project id is 7341d25f-bb86-466d-a637-9d3962998829
19 Replies
6 months ago
Hey! I'm looking through both of those links and I might be missing something but I dont exactly see a template link? Both are returning not found.
Could be an issue with it simply not existing anymore
6 months ago
i had the same issue...
hi could let me know if you have solved the issue please? I run into the same issue as well….
6 months ago
Hello! As I mentioned all of these links are resolving to "page not found" looking like they simply don't exist.
I believe that is the root of your issues as searching the template registry also results in no matches for "cal.com" "calcom" "calendso" or anything starting with "cal" related to the intention of calcom.
here is the link from callcom official website: https://cal.com/docs/self-hosting/deployments/railway
here is the link from callcom official website: https://cal.com/docs/self-hosting/deployments/railway
6 months ago
Thanks! Taking a peek now.
Thank youi! It failed for the health check (the health check path is api/logo by default

6 months ago
Yeah this looks to be a template issue! I think it's a bit outdated.
I'd suggest reaching out to the cal team on getting it updated.
6 months ago
I see that the env vars are still calling it calendso. I assume those have been updated on latest which would lead to mismatch and issues all around

thank you for the help! I assume we only can wait for the update from the cal.com team right?
6 months ago
Well, that's something I need to reach out to the template owner about. I'll do so start of work week.
6 months ago
Don't have anything yet! Reaching out now
a month ago
Hi, any updates? still not working 
16 days ago
Any updates on this? @noahd Changing health path to /api/v2/health didn’t solve the issue neither.