Cloudron Forum

All good here!
Upvote this message for an "update went smoothly" report to @girish

@xarp
Another vote for LibreTranslate. It seems that Mastodon v4 now offers translation using the LibreTranslate API. So it would be sweet to have this running on the same server.

"️ We are planning to release important security fixes for #Mastodon on July 6th, between 13:00 and 15:00 UTC. They will be available for the 4.1, 4.0 and 3.5 versions as well as a nightly release, to make the upgrade as small and painless for everyone as possible. Be ready to upgrade!"
https://mastodon.social/@Mastodon/110644992947398414

@girish Yay! Thank you.
I am all new to this Linux game so I wasn't aware I could just set the environment variables like that.

For everyone else, this is what you need to do:

──────────────────────────────

1. Set up S3 with Synapse. See my post here: https://forum.cloudron.io/post/60415

2. Create a database.yaml file in /app/data/configs that contains the postgres database credentials.
   You can find those in the existing homeserver.yaml file.

    user: xxx
    password: xxx
    database: xxx
    host: postgresql

3. Create a script (e.g., s3cleanup.sh) with the following contents:

#!/bin/bash
cd /app/data/configs
export AWS_ACCESS_KEY_ID=[your S3 compatible access key]
export AWS_SECRET_ACCESS_KEY=[your s3 compatible secret access key]
/app/code/env/bin/s3_media_upload update /app/data/data/media_store 1m
/app/code/env/bin/s3_media_upload upload --delete --endpoint-url https://yours3storageendpoint.com /app/data/data/media_store [your s3_bucket_name]

4. Run the s3cleanup.sh script.
   It will look up media that hasn't been touched for 1m (= 1 month) or whatever you set above. It needs to be an integeger value, followed by either m = month(s), d = day(s) or y = year(s).
   It will create a cache.db file that refers to the media that matches your criteria.
   In the second step, it will upload all files from the cache.db to your s3 storage and delete the local copies.

The output looks like this:

Syncing files that haven't been accessed since: 2022-12-25 14:59:14.674154
Synced 603 new rows
100%|████████████████████████████████████| 603/603 [00:00<00:00, 16121.24files/s]
Updated 0 as deleted
100%|████████████████████████████████████| 603/603 [03:25<00:00,  2.93files/s]
Uploaded 603 media out of 603
Uploaded 3203 files
Uploaded 263.6M
Deleted 603 media
Deleted 3203 files
Deleted 263.6M

Edit: Added path /app/data/configs to script to make it work as cron job.
Edit2: Added more choices for duration suffixes in 's3_media_upload update' job.

Disclaimer: This is to the best of my knowledge and understanding. It worked for me, but I accept no liability for loss of data on your server caused by my incompetence.

@eddowding
Cloudron gives you plenty of protocols to choose from.
I am backing up to https://www.hetzner.com/storage/storage-box via SSHFS. Only paying €3.81 currently (for 1 TB), which is more than fair IMO.
If your VPS is not in Europe, you can also check out IDrive e2 (https://www.idrive.com/e2/pricing). It's an S3 compatible service.

I had the opportunity to test the first production release of Documenso (v0.9 from two weeks ago). Everything worked perfectly. The GUI looks very much like PandaDoc without any options. Right now, you can only add a date and signature field. The date cannot be formatted. Signatures can be added with mouse / touch or by just typing your name (unfortunately, this cannot be turned off). The feature set is extremely basic, but the project looks very promising. I'd love to have it available in Cloudron as soon as the staff decides it is safe to implement.

You can test the current version at https://sign.adminforge.de
This is a test instance. I've asked the admin if it's OK to share the link here. He is looking for testers that share their feedback (see https://adminforge.de/kontakt/).

@thoresson I had the same. Deleting browser cache and cookies solved the problem for me.

@jdaviescoates

Sure! It is quite easy, once you know what you are doing.

Take the following code and replace the <S3...> boxes with your S3 compatible storage's data.

media_storage_providers:
- module: s3_storage_provider.S3StorageProviderBackend
  store_local: True
  store_remote: True
  store_synchronous: True
  config:
    bucket: <S3_BUCKET_NAME>
    region_name: <S3_REGION_NAME>
    endpoint_url: <S3_LIKE_SERVICE_ENDPOINT_URL>
    access_key_id: <S3_ACCESS_KEY_ID>
    secret_access_key: <S3_SECRET_ACCESS_KEY>

Make sure the endpoint URL starts with https://
Copy the code to your clipboard.

Open the file manager of your Synapse App in Cloudron Dashboard. Navigate to configs and open the homeserver.yaml file. Paste the code from your clipboard at the end of the configuration file.
Save and restart the app.

@girish Now I can see it, too. Thanks! I'll give it a try.
Update: Works great. Tested with Element and Fedilab so far.

I find it totally confusing. I have to look on the left for new messages and on the opposite side for notifications. Plus tiny symbols on the sidebars and a huge font in the middle.

I will certainly adapt to it, but if you are counting votes for returning the classic theme, here is my +1.

Documenso pretty much clones the GUI from PandaDoc, what I have used before. So it was pretty appealing to me.

Due to the lack of features, I gave DocuSeal another chance in the meantime, and now I am very used to it. I am not self-hosting, I even decided for a paid subscription. The author @docuseal is very response and added my feature requests in no time. Sticking with DocuSeal now.

I had changed to Argon2id a while ago. Since I was not sure about this needs to be done, but it was offered to me, I also rotated my encryption key as explained here: https://bitwarden.com/help/account-encryption-key/
No matter if you just change the algorithm or rotate the key, you will need to log out on all your devices (desktop client, mobile client, browser extension) and login in again afterward.
What I did had no impact on OTP.

I am very stingy when it comes to my server resources, so I'd love to be able to assign quotas of less than 1 GB to some users (those who only need their mailbox to identify and receive server messages). Could you adapt the slider or introduce an input field instead?

@scooke

Fixed that for you:

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves arat umip pku ospke avx512_vnni md_clear arch_capabilities

Welcome to the club of one-liners.

@girish said in serious Cloudflare goof:

I am not a Cloudflare customer, so I don't know the expectations of Cloudflare customers. Your recommendation is clear. Any other cloudflare customers here? Do you always proxy your sites via Cloudflare? Maybe we should add a checkbox to allow "proxied" setup at domain setup time.

Cloudflare Domain customer here. Not using proxy. I have doubts about GDPR compliancy.

Hi there,

It would be pretty cool to have the option to forward users to a status page instead of showing the generic "Cloudron App Error - please retry in a few minutes" page.
I'd really like to forward to my Uptime Kuma page (hosted on another server).

This VPS exclusively runs Cloudron. There was no entry on the unattanded log for this time.
I will open a support ticket with my provider. Thanks, @murgero and @girish!

@JLX89 Thanks for pointing me to the Cloudron API. That's a much more elegant way to track the status with Uptime Kuma than my current approach! Not to mention that it probably uses less bandwidth than loading the actual app web interface for each uptime check.

Still, I'd like to have a page in the Cloudron GUI that allows me to set up custom error pages.

P.S. / Edit: For others who are reading this thread and like to make use of the API health check, this is the actual URL to enter in Uptime Kuma:
https://my.cloudron.domain/api/v1/apps/{AppIdFromStep2}?access_token={TokenFromStep1}

It was indeed a mishap in my provider's area of responsibility. Thanks again for pointing me in the right direction.

@robi
Is there any specific you'd like to know?
I just did as mentioned in the doc:

1. Created a new directory /home/yellowtent/boxdata/custom_pages
2. Created two html files app_not_responding.html and notfound.html with nano and pasted in the HTML code that I had prepared on my computer
3. Saved and voilà

The HTML files contained an explanation of what went wrong and a link to my already existing uptime kuma status page, where I put a note to users if there is a longer downtime (planned or unplanned). I have uptime kuma running on a separate VPS so it does not depend on Cloudron to be working. I am checking for health via API as suggested earlier in this thread. You can see the result here: https://status.42bit.io