Cloudron Forum

I am also experiencing the 404 problem with the latest version. While I can access the dashboard, all the booking links leads to 404s

@luckow You can disable signup within the Admin settings page. No need to define any additional env variables.

@jessencan I never reseeded the app store after adding the GOOGLE_API_CREDENTIALS to env file. It's not necessary. Simply restart the App and sign in with your admin account. Then you can enable the Google Calendar integration in the admin settings.

@nebulon It seems this issue is caused by incorrectly generated NEXTAUTH_SECRET and CALENDSO_ENCRYPTION_KEY

After switching the Google OAuth Screen App from Internal to External with testing, adding my Google accounts to the list of testing users, I have been able to add all 3 of Google accounts across different orgs. Everything seems to be working well!

I was able to successfully set up the Google Calendar app by following the Cal.com self-hosters instructions you linked. I created it as an "Internal App". After including the GOOGLE_API_CREDENTIALS variable in the .env file I had to restart the Cal.com cloudron app twice for it to properly recognize the OAuth Credentials.

Please be aware that you need to enclose the JSON value of the environment variable in single quotes ' and apparently include a new line after your last environment variable.

It should look something like this:

# Add custom environment variables in this file

NEXT_PUBLIC_APP_NAME="..."
NEXT_PUBLIC_COMPANY_NAME="..."
GOOGLE_API_CREDENTIALS='{"web":{...}}'

# don't forget to include the new line after the env variable

Note it is not necessary to reseed the app store as described in Cal.com docs. Simply restart the Cloudron Cal.com app after adding the env varible and navigate to the admin settings to enable the Google Calendar app for your instance. You can also skip the admin onboarding dialog where you can enable the Google Calendar plugin.

After completing the admin onboarding process, Cal.com requests you to setup 2FA to be able to access Admin settings. Attempting to do so results in an error. See below:

Sep 04 13:40:27@calcom/web:start: RangeError: Invalid key length
Sep 04 13:40:27@calcom/web:start: at Cipheriv.createCipherBase (node:internal/crypto/cipher:116:19)
Sep 04 13:40:27@calcom/web:start: at Cipheriv.createCipherWithIV (node:internal/crypto/cipher:135:3)
Sep 04 13:40:27@calcom/web:start: at new Cipheriv (node:internal/crypto/cipher:243:3)
Sep 04 13:40:27@calcom/web:start: at Object.createCipheriv (node:crypto:141:10)
Sep 04 13:40:27@calcom/web:start: at symmetricEncrypt (/run/calcom/apps/web/.next/server/chunks/13303.js:29:66)
Sep 04 13:40:27@calcom/web:start: at handler (/run/calcom/apps/web/.next/server/pages/api/auth/two-factor/totp/setup.js:171:103) {
Sep 04 13:40:27@calcom/web:start: code: 'ERR_CRYPTO_INVALID_KEYLEN'
Sep 04 13:40:27@calcom/web:start: }

I would see this as quite an urgent issue as it prevents from adding new apps to the platform.

@sparkwise Doesn't the PR you linked resolve the issues that have previously been blocking the packaging as a Cloudron app? Would it be possible for you to take another look @girish ? Cal.com would still be a killer app to have on the platform.

@nebulon Amazing! Thank you!!

@nebulon Interesting. I wasn't aware of that. Aren't all the necessary parts of the project public to deploy it on Cloudron? https://github.com/calcom/docker

I would be interested to know what priority the Cloudron team has for bringing Cal.com to Cloudron. To me it seems like a killer feature, and I don't quite understand why there has been so little input from them in this thread recently.

Is there a public app roadmap of some sort?

When trying to enable the Backblaze B2 app in NocoDB, a cloudron-specific error is occuring where the testing of the configuration fails due to the read-only file system of cloudron apps. This prevents the B2 app from functioning properly. I have confirmed with a NocoDB developer that this issue is Cloudron specific.

Nov 10 04:44:50 p :: [Error: EROFS: read-only file system, open '/app/code/temp.txt'] {
Nov 10 04:44:50 errno: -30,
Nov 10 04:44:50 code: 'EROFS',
Nov 10 04:44:50 syscall: 'open',
Nov 10 04:44:50 path: '/app/code/temp.txt'
Nov 10 04:44:50 }
Nov 10 04:44:50 POST /api/v1/db/meta/plugins/test 400 65 - 32.846 ms
Nov 10 04:45:00 GET /dashboard 301 185 - 4.418 ms

@roofboard said in Cal.com (was Calendso) - Calendly Alternative:

So I created a temporary database so long as you build this on a server with access to postgres this will work. The only problem is that I cannot figure out why it is stuck on localhost:3000 as opposed to accepting the new dns settings

Your work looks very promising! Unfortunately, there is not much feedback I can provide from the technical perspective.

@nebulon In which release will this fix be included

@nebulon That sounds like the right solution to me as well. I usually prefer setting the Title and Icon manually anyway.

Would also love to see web driver support, even if it is via an external service!

Would love to see support for Cal.com as well!

@murgero Are there any updates on your app? I would love to use it!