localhost URL after booking confirmation

[jkoopmann]

Found a bug? Please fill out the sections below. 👍

Issue Summary

After accepting a booking via the link in the e-mail I am redirected to

https://localhost:3000/booking/IDredacted?error=Booking%20%alread20confirmed

Steps to Reproduce

1. Enable booking confirmation
2. Book a meeting
3. Wait for the booking confirmation mail to you
4. Click accept

NEXTAUTH_URL and NEXT_PUBLIC_WEBAPP_URL are set correctly.

The actual acceptance is processed correctly. The booking already confirmed error comes because our E-Mail Security system while analyzing the e-mail calls the booking link. But the error should not point to localhost

[C9Glax]

Same here, docker sha256:3accd30392045d7440bda55c4e2325a86476ef6109464b4d26cd2b26bfa79a64 latest

NEXTAUTH_URL not set (therefor # Configure NEXTAUTH_URL manually if needed, otherwise it will resolve to {NEXT_PUBLIC_WEBAPP_URL}/api/auth should take effect, but isn't)

[C9Glax]

Looking at the redirection URL it contains an Error-Message:

https://localhost:3000/booking/7t3aPpnVeaAukQALCrDRBC?error=Attempted to call BrokenIntegrationEmail() from the server but BrokenIntegrationEmail is on the client. It's not possible to invoke a client function from the server, it can only be rendered as a Component or passed to props of a Client Component.

[olivierlambert]

Confirm, same issue in here

[naitikraj1000]

Hey I am not getting the error,can u provide the video

[jkoopmann]

In my case the error comes because my e-mail system replaces all URLs and calls the URLs for virus analysis. This means however that when I click the link

1. the meeting is accepted (due to the virus checking) and
2. The meeting is accepted AGAIN with my browser.

And (2) leads to the error and THAT error url is localhost:3000.

Maybe try to reproduce it by clicking the accept link twice.

[username3024]

I am currently trying to get to the root cause, may any of you quickly tell me if you are using a subdomain?
I tried some stuff and I only have the issue when using a subdomain so far. But maybe that is a totally unrelated issue adding to this.

[jkoopmann]

Not sure what exactly you are referring to as "subdomain". It is calcom.mydomain.eu (with my domain.eu obviously being different). I have it running behind a HA-Proxy. Which is why it is essential that the links are all rewritten and nothing remains at "localhost:3000".

[username3024]

I found an issue where the orgDomains.ts logic is causing trouble with domain verification, potentially triggering the localhost fallback

// Find which hostname is being currently used const currentHostname = ALLOWED_HOSTNAMES.find((ahn) => { const url = new URL(WEBAPP_URL); const testHostname = ${url.hostname}${url.port ? :${url.port} : ""}; return testHostname.endsWith(.${ahn}); });

Here's what's happening:
The code creates a URL object from WEBAPP_URL (which is https://calcom.domain.eu/), then it extracts just the hostname part (calcom.domain.eu).
Then it tries to check if this hostname ends with .${ahn} (so .calcom.domain.eu), and this will always fail because calcom.domain.eu doesn't end with .calcom.domain.eu

It might trigger the localhost fallback. Right now I am experimenting with a TLD instead of a subdomain and things seem oddly fine.

[nathanael-h]

Hi @username3024 I use it with a subdomain, like cal.something.com

[juliamrch]

Hi @username3024, observing the same behavior while using a subdomain calendar.domain.com.

Details

• Cal running behind a proxy
• Mail service: Tuta (no email scanning)

Flow

1. Click on Confirm from email
2. Redirects first to the correct domain, then falls back to localhost:3000.
3. When manually replacing the link, the confirmation page appears with the booking confirmed.

So the confirmation action goes through, but the issue arises when redirecting after booking confirmation.

[olivierlambert]

+1, exactly the same issue in here.