Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • 1 Votes
    1 Posts
    31 Views
    No one has replied
  • 1 Votes
    3 Posts
    127 Views
    girishG

    @LoudLemur said in Setting up additional applications to work with cal.com:

    NEXT_PUBLIC_APP_NAME="cal.website.com"
    NEXT_PUBLIC_COMPANY_NAME="cal.website.com"

    What is the big deal? Why should we edit this, and what would we instead have there?

    This used to be for avoiding conflict with the cal.com cloud hosting solution itself. But it seems this doesn't work anymore, investigating.

  • Change logo for jitsi

    Locked Jitsi
    4
    0 Votes
    4 Posts
    192 Views
    bmannB

    Duplicate of https://forum.cloudron.io/topic/9427/jitsi-branding, let's close this one and use the branding one for requests.

  • 0 Votes
    8 Posts
    397 Views
    L

    @plusone-nick said in Jitsi Problem - Are you the host? Authenticate:

    Testing Results;

    Installing with "Leave user mgmt to app" the app installs with no user auth and it has a generated user/mod already logged in
    ed9414c3-74b3-46dd-94f7-41561e9c0809-image.png

    Installing with "Allow all user from this Cloudron"
    3025504d-b704-4a33-a842-acb32b33a3ae-image.png
    and I use my Cloudron username (not the email) with my standard Cloudron password and it works

    If you are using User/Group Policies double check them as I had a similar use case with a standard user not being able to join as they did not have the right permissions

    Hope this helps!

    It certainly does! Thank you very much for investigating.

    I reinstalled and it worked right away as you mentioned, when the option to leave it to the App was selected.

    I think we will need to develop some terminology such that the difference between Cloudron (the account here) and the Cloudron instance we are running is clearly signaled.