ALLOWED_HOSTNAMES environment variable breaks app startup

[sparkwise]

In our Cal.com app logs, I noticed these two lines:

WARN orgDomains.ts Match of WEBAPP_URL with ALLOWED_HOSTNAME failed ...
...
ALLOWED_HOSTNAMES: []

I modified the env file to specify ALLOWED_HOSTNAMES using the format demonstrated upstream (see .env.example#L64), but this made the app fail on startup.

I suspect that the issue here may be that the requested list syntax ('"a","b","c"') is somehow getting modified when Cloudron's env file is included in the Cal.com .env file.

[sparkwise]

Noting that this may be part of the problem underlying issue https://forum.cloudron.io/topic/9969/err_invalid_url-upstash-log-entries-sidequest-disable-telemetry-signup

[girish]

@sparkwise https://github.com/calcom/cal.com/issues/12201 is the upstream issue (despite closed, the issue exists)

[sparkwise]

Problem solved! With these two in my env file, I'm no longer seeing the error messages:
NEXT_PUBLIC_WEBAPP_URL=https://cal.example.com
ALLOWED_HOSTNAMES='"example.com","cal.example.com"'
(I suspect that the first hostname is sufficient on its own. Haven't yet tried removing the second one.)

[sparkwise]

I'm wrong. I see the same 404 reported upstream on user profiles after making this change.

[girish]

@sparkwise what's the motivation to set this variable? Does something break when this is not set?

[sparkwise]

Nothing specific. I saw the errors in the log, and was curious to see if anything changed or behaved differently after addressing them. I didn't notice any changes, other than the logs being cleaner.

[girish]

@sparkwise ah yes, that's what made me go down this route earlier as well. Unfortunately, I never found a fix for this. I think it requires some upstream fixes.