Cloudron Forum

I have realized, that several organizations are very interested in the possibility of creating their own invitation email. The possibility of adding text and attach a kind of "onboarding"-manual for all running applications would be pretty nice. It would make it really easy to do these thing automated thereafter using the API.

ejabberd would be freakin amazing!!

@girish I'm glad to see your efforts put in this issue. I think we are getting closer! I looked at the sip-communicator config of yunohost - as their jitsi is working on my systems and they actually set those variables.

A further indication that this is the only missing piece is this thread here...

Are there environment variables for the local and the public IPs? I would like to test this.

One of my Gitlab instances is configured to receive emails and also does receive most of them and processes them into issues. However, quite a good amount are missing and I have done some testing to check where the problems are.

• Cloudron mail server seems to receive and handle everything well.
• /home/gitlab/log/mail_room_json.log contains almost no errors for the period of the last several days in which i know that several mails have been missed.
• I searched the other logfiles for other related information, but could not really get something of much value.

Does anyone else experience this issue? Where can I dig deeper to find the core of the problem?

I actually found this... Could be related: https://gitlab.com/gitlab-org/gitlab/-/issues/267121

Cheers

@girish I actually managed to get this running. The lower end of the section in the docs did the trick.

@opensourced nevermind, i figured it out!

@nebulon I actually have set up several Cloudron instances and none of them is able to get Jitsi to work. I suppose that if I provide a fresh VM, it wont be able to get it working either. Therefore it might be suitable for debugging.

(I still want to mention at this point that its neither port related, nor a networking issue as I have a working Jitsi (from Yunohost) on one of my VMs)

What do you think?

@girish I moved the appsdata folder to another mounted drive -> after creating the symlink (as root) i didn't propperly set the permissions. I fixed it, so all good now. Thanks!

@girish We do have our own server farm in a data center. As host for our VMs, we use Proxmox.

Within the last month, I had 3 cloudron instances (running productive apps for clients) crashing, because the NFS mount could not be mounted and the root filesystem was used instead.

I find it frustrating to run into this issue so often. Mostly because I know it can happen every moment and I cant do anything about it.

How about adding a checkbox in the backup settings with the title "Skip backup if storage is not available"?

I would find it very useful if i could enter custom nginx rules (generally or per application), that would survive updates. Is this possible at the time beeing?

@nebulon See that point. Two use cases are:

WordPress exposes the example.com/xmlrpc.php API per default. We already had several issues where attackers used those APIs to send spam mails from our applications. To fix this issue, either you need to install a plugin that disables the API (however, dose plugins which are available for free are crapy and I dont trust them), or you just disable those requests in the nginx.conf of the application. This is what I did, but through updates those custom lines were deleted.

I would like to restrict the Synapse Admin API to certain IPs.

@nebulon I actually run in the same issue on several instances. On some it still works however... I am using TrueNAS as the NFS server and it would be nice if i could keep using it. Any hint on where that error is coming from?

@girish I also see this error on one of my cloudrons.. Will your patch soon be released in an update?

@nebulon yes, i have vaultwarden installed...

I am facing the situation, where a before configured and running Cloudron instance is now showing the DNS setup window (on the previous running my.xy.com dashboard site).

When I then enter the domain again and choose wildcard for certificate configuration, I see the error msg "Already activated". In the box logs I see this:

2023-09-25T12:51:47.742Z box:platform BoxError: ER_BAD_FIELD_ERROR: Unknown column 'apps.enableTurn' in 'field list'
    at Query.queryCallback (/home/yellowtent/box/src/database.js:91:38)
    at Query.<anonymous> (/home/yellowtent/box/node_modules/mysql/lib/Connection.js:526:10)
    at Query._callback (/home/yellowtent/box/node_modules/mysql/lib/Connection.js:488:16)
    at Sequence.end (/home/yellowtent/box/node_modules/mysql/lib/protocol/sequences/Sequence.js:83:24)
    at Query.ErrorPacket (/home/yellowtent/box/node_modules/mysql/lib/protocol/sequences/Query.js:92:8)
    at Protocol._parsePacket (/home/yellowtent/box/node_modules/mysql/lib/protocol/Protocol.js:291:23)
    at Parser._parsePacket (/home/yellowtent/box/node_modules/mysql/lib/protocol/Parser.js:433:10)
    at Parser.write (/home/yellowtent/box/node_modules/mysql/lib/protocol/Parser.js:43:10)
    at Protocol.write (/home/yellowtent/box/node_modules/mysql/lib/protocol/Protocol.js:38:16)
    at Socket.<anonymous> (/home/yellowtent/box/node_modules/mysql/lib/Connection.js:88:28)

This situation happened after a scheduled reboot was executed. After the reboot succeeded, I ended up like this. What might have happened? Thanks in advance!

Awesome, thanks!