Cloudron Forum

Hi, tested on Firefox 148.0 on Arch Linux and Safari on iOS. Issue persists in a private/incognito window with no extensions. Older documents still fail to open.

Hi, thanks for the update. The new package seems to fix the issue for new documents, but older documents still fail to open with the same error.

Hi, we have the same issue. Confirmed on both Firefox and Chrome.
curl -I shows the root cause:

GET /extensions.js?ver=2026.2.0-1772167481346
→ 301 redirect to http://<redacted>/extensions.js/?ver=...

Content-Security-Policy: Nastavení stránky zablokovalo provedení skriptu (script-src-elem) na http://<redacted>/extensions.js/?ver=2026.2.0-1772167481346, protože porušuje direktivu „script-src 'self' 'unsafe-eval' 'unsafe-inline' resource: https://<redacted>"
Zdroj na adrese "https://<redacted>/extensions.js?ver=2026.2.0-1772167481346" byl zablokován kvůli rozdílnému MIME typu ("text/html") (X-Content-Type-Options: nosniff).
URI zdroje <script> není v tomto dokumentu povolen: „https://<redacted>/extensions.js?ver=2026.2.0-1772167481346".
Uncaught TypeError: can't access property "DocEditor", window.DocsAPI is undefined
    startOO https://<redacted>/common/onlyoffice/inner.js?ver=2026.2.0-1772167481346:2544

Nginx adds a trailing slash and downgrades HTTPS to HTTP. HSTS catches it and switches back to HTTPS, but the URL is now /extensions.js/ instead of /extensions.js → server returns HTML instead of JS → CSP blocks it → OnlyOffice fails to load.

@nebulon said in Czech Translation for Cloudron Now 100% Complete :

This is great! We will ship the next Cloudron version then with Czech (internally 9.1 is released for new installs already, so will be added to the next patch release then)

That’s great news, thank you!

@james said in Czech Translation for Cloudron Now 100% Complete :

Hello @archos
Thanks for your contribution.
I have added you to the translator group.

I probably don’t deserve that — my colleague did most of the translation work — but thank you very

Hi everyone,

I would like to share some good news regarding the translation contributions we’ve been working on over the past few weeks.

The Czech translation for Cloudron is now 100% complete. My colleague has been actively working on the translations and reviewing all strings to ensure consistency and quality.

Oh well, I thought the email issue would be fixed by the latest update,
but unfortunately the problem still persists.

@james Yes, you can use the same email address I use on this forum.
Would it be possible to invite my colleague as well, so we can work on the Czech translation together?

Thank you!

Hello,
we don’t have access to https://translate.cloudron.io/
yet, but we’d like to get involved in the Czech translation together with a colleague.
What is required to get access?

Thank you!

@james Thanks again for your response and also for reporting the issue on the Pixelfed GitHub.

@james Hello,
thank you very much for your reply.

Pixelfed development seems to be a bit slow at the moment.
Here is the output from the Pixelfed app web terminal:

 instance.curated_registration ....................................................................................................................  
  enabled .................................................................................................................................... false  
  resend_confirmation_limit ...................................................................................................................... 5  
  captcha_enabled ............................................................................................................................ false  
  state ⇁ fallback_on_closed_reg .............................................................................................................. true  
  state ⇁ only_enabled_on_closed_reg .......................................................................................................... true  
  notify ⇁ admin ⇁ on_verify_email ⇁ enabled .................................................................................................. true  
  notify ⇁ admin ⇁ on_verify_email ⇁ bundle .................................................................................................. false  
  notify ⇁ admin ⇁ on_verify_email ⇁ max_per_day ................................................................................................ 10  
  notify ⇁ admin ⇁ on_verify_email ⇁ cc_addresses ............................................................................................. null  
  notify ⇁ admin ⇁ on_user_response .......................................................................................................... false  

Admin email notifications for new user registrations stopped working in the latest Pixelfed version. This most likely started after the last update — registrations were previously closed, so I didn’t notice earlier. The issue occurs with filtered registrations (manual approval).

Details

• Users receive registration confirmation emails (working correctly)
• Admin no longer receives email notifications when a user registers
• This worked in the previous Pixelfed version
• Tested on two separate instances with the same result
• Main instance has ~2000 users, rollback is not an option

Verified configuration

• INSTANCE_CONTACT_EMAIL is set correctly
• ENFORCE_EMAIL_VERIFICATION=true is enabled
• Email delivery is working (users receive emails)

Question

Is anyone else experiencing this issue?

Admin notifications are critical for instances with manual approval enabled. At the moment, I have to manually check for new registrations several times a day.

Thanks for any advice!

Title: [Application] on Cloudron – Endurain

• Main Page: https://docs.endurain.com/
• Git: https://github.com/endurain-project/endurain
• Licence: AGPL-3.0
• Dockerfile: Yes
• Demo: https://demo.endurain.com/

• Summary:
  Endurain is a self-hosted fitness tracking service that allows users to manage and analyze their training data while keeping full control over hosting and privacy. It supports activity imports, external service integrations (Strava/Garmin), and multi-user usage.

• Notes:
  Endurain is Docker-based and configured via environment variables, which aligns well with Cloudron’s app model. It supports SSO authentication and uses PostgreSQL for scalable data storage. Privacy-first and self-hosted focus makes it a good fit for Cloudron users.

• Screenshots:
  https://github.com/endurain-project/endurain/blob/master/screenshot_01.png

@IniBudi Many thanks for the guide, everything seems to be working fine now.
The application has been successfully updated and is running properly.

@james Thanks for the links. The workaround looks rather complex, and I honestly don’t feel confident performing manual database changes. I’m wondering whether it would be safer to resolve this by reinstalling the app and restoring from a backup.

@robi Thanks for the suggestion. I’ve tried restarting and increased the app memory — it’s now set to 4 GB, which should be sufficient. Unfortunately, it still ends with the same migration error.

@Kubernetes said in Vaultwarden fails to start after update – DB migration error (SSO):

@archos No issues on my Cloudron after updating Vaultwarden.
Thanks for the feedback.
On our server we have two Vaultwarden apps — both were updated, but only one updated without issues. The other one fails with the migration error.

After updating the Vaultwarden app on Cloudron, the application never reaches the Running state and gets stuck in a start / restart loop.

The app logs show the following error:

Dec 29 18:21:11 9: vaultwarden::main
Dec 29 18:21:11 [2025-12-29 17:21:11.256][panic][ERROR] thread 'main' panicked at 'Error running migrations: QueryError(DieselMigrationName { name: "2024-03-06-170000_add_sso_users", version: MigrationVersion("20240306170000") }, DatabaseError(Unknown, "Referencing column 'user_uuid' and referenced column 'uuid' in foreign key constraint 'sso_users_ibfk_1' are incompatible."))': src/db/mod.rs:505
Dec 29 18:21:11 [INFO] Using saved config from `/app/data/config.json` for configuration.
Dec 29 18:21:11 [WARNING] Please use the admin panel to make changes to them:
Dec 29 18:21:11 [WARNING] SIGNUPS_ALLOWED, INVITATIONS_ALLOWED, YUBICO_CLIENT_ID, YUBICO_SECRET_KEY
Dec 29 18:21:11 [WARNING] The following environment variables are being overridden by the config.json file.
Dec 29 18:21:14 2025-12-29T18:21:14+01:00
Dec 29 18:21:14 2025-12-29T18:21:14+01:00
Dec 29 18:21:14 2025-12-29T18:21:14+01:00
Dec 29 18:21:14 2025-12-29T18:21:14+01:00
Dec 29 18:21:14 /--------------------------------------------------------------------\
Dec 29 18:21:14 0: vaultwarden::init_logging::{{closure}}
Dec 29 18:21:14 10: std::sys::backtrace::__rust_begin_short_backtrace
Dec 29 18:21:14 11: main
Dec 29 18:21:14 12: <unknown>
Dec 29 18:21:14 13: __libc_start_main
Dec 29 18:21:14 14: _start
Dec 29 18:21:14 1: std::panicking::panic_with_hook
Dec 29 18:21:14 2: std::panicking::panic_handler::{{closure}}
Dec 29 18:21:14 3: std::sys::backtrace::__rust_end_short_backtrace

It looks like the migration related to SSO fails, but I’m not sure what the correct or recommended way to handle this situation is.

Has anyone encountered this issue?
Is there a supported way to fix this without manually modifying the database?

Thanks for any pointers.

@james Thank you for the information, I suspected that this would not be possible.
I will proceed with reinstalling the application and restoring it from a backup.

Just to confirm: the backup will not be deleted when uninstalling the app, correct?

Thanks again for the confirmation and explanation.

Hi,

I have Vikunja running on Cloudron.
During the initial installation, I selected "Leave user management to the app".

Now I would like to switch the app to Cloudron SSO:

• in the app settings, I changed it to "Only allow the following users and groups"
• selected a Cloudron group
• saved the configuration

How do I configure the application so that users can log in using the SSO button?

Specifically:

• do I need to configure anything manually inside Vikunja (OIDC settings)?
• or should the SSO login button appear automatically after changing the Cloudron settings?

Thank you very much for any tips or guidance.