Cloudron Forum

So I tried an install of Cloudron, and the issue is the same. Anyone else with this issue?

So I found an issue I am having on all nextcloud servers I have on our cloudron.

On the mail app, there are menu items missing. I am not sure if it's an app issue or a Cloudron NextCloud container image issue. Please read this feature enhancement I asked for.

https://github.com/nextcloud/mail/issues/12805

I am going to make a new server with just nextcloud on to test this.

@james said:

Hello @apesorguk
That is a good idea.
Nextcloud apps are a notorious offender in breaking Nextcloud setups.

Totally agree, we have said to nextcloud that they should not release updates and apps until tested with all other apps. They need to get rid of untested apps as well.

@james said:

Hello @apesorguk
Sorry to read that you are having issues.
Neither Nextcloud nor Cloudron can provide a full coverage of every app available for Nextcloud for each update.
This issue was also already reported upstream for the polls app https://github.com/nextcloud/polls/issues/4619

Maybe you can try to disable the poll app with the following docs: https://docs.cloudron.io/packages/nextcloud#fixing-a-broken-install

or you try the suggested fix from the issue:

Quote:

To fix it I ran against the database:

DROP INDEX uniq_shares;
DROP INDEX uniq_token;
DROP INDEX uniq_subscription;
DROP INDEX uniq_unprocessed;
DROP INDEX uniq_watch;
DROP INDEX uniq_preferences;

Thank you. Worked a treat.

@sponch said:

Be careful with the Polls app. I’ve stopped using it because it bricked several Nextcloud instances for me multiple times.

We have gotten to the position of when ever we update apps now we also backup before hand sure to avoid issues with some app updates breaking the server.

I have tried to delete and delete data on remove, but when trying to install I get this An error occurred during the request.

Unable to proceed.
Database error when running migration 090000Date20260302212000 for app polls An exception occurred while executing a query: SQLSTATE[42P07]: Duplicate table: 7 ERROR: relation "uniq_watch" already exists

We have 2 nextcloud servers, one updated fine and one runs into this error we can not get rind of when the polls app is updated.

I get the following error when testing social app.

I have tried adding to .htaccess file, but when restarting server, the added lines do not remain as seems htaccess file gets reset.
i have tried adding a .wellknown file and adding the required lines there with no luck. The file and content stays when restarting but not seen by the app.

App Link: https://github.com/nextcloud/social
App Store Link: https://apps.nextcloud.com/apps/social

Has anyone found a fix or workaround?

Basically, there is no fix for allowing embedding on our own websites, even with specific origins set and for the app to load.

I remember at one point you should not set CSP for all apps, but now it seems it's on all apps even though it doesn't work with all of them.

They were only being embedded for the staff on our Nextcloud, not for the public. And we did restrict to our internal domains and had the same issues.

Just thought people should know that some apps don't work at all with CSP, causing these apps GUI to stop loading complely making it look like the app no longer works.

So I found an issue with 3 apps when setting the ability to embed.

Freescout, Chatwoot and Open WebUI

Using the preset configuration to allow embedding

# Allow embedding from all sites
default-src 'self';
frame-ancestors 'none';

It cause a issue with Freescout and Chatwoot loading at all when going directly and shows an error on the website embedding it.

I thought the app became currupt so I installed the setup again and tried to add the CSP again to face the same issue. Chatwoot after removing the CSP did not work but freescout worked again.

Open WebUI just shows a huge Open WebUI logo.

Thanks for you help

Ok so I deleted the alias we had for it under development and tried to add the mailbox and now its worked. Bare in mind I only added the alias after the error to see if I get the error adding as a alias.

Yes it is showing there, for somereason just not showing on the GUI

is there no way to search via terminal?

No we don't I have checked every app we use.

No mailing lists at all. Another strange thing is I can add them as an alias without error.

I am trying to add a mailbox, but it says it already exsists but when I search the mailbox, nothing shows.

Thanks all fixed now. I found this worked even with the line brake.

I have run the command sed -i 's/\r$//g' /app/data/fix_db.sh to fix the new line characters and then run bash /app/data/fix_db.sh again and it ran as expected. Disabled recover mode and confirmed things are back to working as expected.

@james I get this problem.

root@bf8db951-7632-4ddf-bf9b-8b58cd65ffe5:/app/code# bash /app/data/fix_db.sh
/app/data/fix_db.sh: line 2: $'\r': command not found
=> Checking if DEFAULT_CHARACTER_SET_NAME and DEFAULT_COLLATION_NAME are set to utf8mb4 and utf8mb4_unicode_ci
/app/data/fix_db.sh: line 4: $'\r': command not found
/app/data/fix_db.sh: line 8: $'\r': command not found
/app/data/fix_db.sh: line 22: syntax error near unexpected token `$'in\r''
'app/data/fix_db.sh: line 22: `    case $yn in
root@bf8db951-7632-4ddf-bf9b-8b58cd65ffe5:/app/code#

So everytime I upgrade from Vaultwarden 1.34.3 to 1.35.0 the instance becomes unresponsive, saying connection failure in the terminal and nothing really in the logs apart from connection failure again.

Jan 06 12:13:28 0: vaultwarden::init_logging::{{closure}}
Jan 06 12:13:28 10: std::sys::backtrace::__rust_begin_short_backtrace
Jan 06 12:13:28 11: main
Jan 06 12:13:28 12: <unknown>
Jan 06 12:13:28 13: __libc_start_main
Jan 06 12:13:28 14: _start
Jan 06 12:13:28 1: std::panicking::panic_with_hook
Jan 06 12:13:28 2: std::panicking::panic_handler::{{closure}}
Jan 06 12:13:28 3: std::sys::backtrace::__rust_end_short_backtrace
Jan 06 12:13:28 4: __rustc::rust_begin_unwind
Jan 06 12:13:28 5: core::panicking::panic_fmt
Jan 06 12:13:28 6: core::result::unwrap_failed
Jan 06 12:13:28 7: vaultwarden::db::DbPool::from_config
Jan 06 12:13:28 8: vaultwarden::main::{{closure}}
Jan 06 12:13:28 9: vaultwarden::main
Jan 06 12:13:28 Please generate a secure Argon2 PHC string by using `vaultwarden hash` or `argon2`.
Jan 06 12:13:28 See: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page#secure-the-admin_token
Jan 06 12:13:28 [2026-01-06 12:13:28.418][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
Jan 06 12:13:28 [INFO] Using saved config from `/app/data/config.json` for configuration.
Jan 06 12:13:28 [NOTICE] You are using a plain text `ADMIN_TOKEN` which is insecure.
Jan 06 12:13:28 \--------------------------------------------------------------------/
Jan 06 12:13:28 | https://github.com/dani-garcia/vaultwarden/discussions or |
Jan 06 12:13:28 | https://github.com/dani-garcia/vaultwarden/issues/new |
Jan 06 12:13:28 | https://vaultwarden.discourse.group/ |
Jan 06 12:13:28 | Report suspected bugs/issues in the software itself at: |
Jan 06 12:13:28 | Send usage/configuration questions or feature requests to: |
Jan 06 12:13:28 | official channels to report bugs/features, regardless of client. |
Jan 06 12:13:37 => Healthcheck error: AbortError: The operation was aborted
Jan 06 12:13:41 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.123:3000
Jan 06 12:13:41 2026-01-06T12:13:41Z
Jan 06 12:13:41 2026-01-06T12:13:41Z
Jan 06 12:13:41 2026-01-06T12:13:41Z
Jan 06 12:13:41 2026-01-06T12:13:41Z
Jan 06 12:13:41 /--------------------------------------------------------------------\
Jan 06 12:13:41 0: vaultwarden::init_logging::{{closure}}
Jan 06 12:13:41 10: std::sys::backtrace::__rust_begin_short_backtrace
Jan 06 12:13:41 11: main
Jan 06 12:13:41 12: <unknown>
Jan 06 12:13:41 13: __libc_start_main
Jan 06 12:13:41 14: _start
Jan 06 12:13:41 1: std::panicking::panic_with_hook
Jan 06 12:13:41 2: std::panicking::panic_handler::{{closure}}
Jan 06 12:13:41 3: std::sys::backtrace::__rust_end_short_backtrace
Jan 06 12:13:41 4: __rustc::rust_begin_unwind
Jan 06 12:13:41 5: core::panicking::panic_fmt
Jan 06 12:13:41 6: core::result::unwrap_failed
Jan 06 12:13:41 7: vaultwarden::db::DbPool::from_config
Jan 06 12:13:41 8: vaultwarden::main::{{closure}}
Jan 06 12:13:41 9: vaultwarden::main
Jan 06 12:13:41 => Exporting env vars expected by Vaultwarden
Jan 06 12:13:41 => Starting Bitwarden
Jan 06 12:13:41 Please generate a secure Argon2 PHC string by using `vaultwarden hash` or `argon2`.
Jan 06 12:13:41 See: https://github.com/dani-garcia/vaultwarden/wiki/Enabling-admin-page#secure-the-admin_token
Jan 06 12:13:41 [2026-01-06 12:13:41.691][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
Jan 06 12:13:41 [INFO] Using saved config from `/app/data/config.json` for configuration.
Jan 06 12:13:41 [NOTICE] You are using a plain text `ADMIN_TOKEN` which is insecure.
Jan 06 12:13:41 \--------------------------------------------------------------------/
Jan 06 12:13:41 | Starting Vaultwarden |
Jan 06 12:13:41 | https://github.com/dani-garcia/vaultwarden/discussions or |
Jan 06 12:13:41 | https://github.com/dani-garcia/vaultwarden/issues/new |
Jan 06 12:13:41 | https://vaultwarden.discourse.group/ |
Jan 06 12:13:41 | Report suspected bugs/issues in the software itself at: |
Jan 06 12:13:41 | Send usage/configuration questions or feature requests to: |
Jan 06 12:13:41 | This is an *unofficial* Bitwarden implementation, DO NOT use the |
Jan 06 12:13:41 | official channels to report bugs/features, regardless of client. |
Jan 06 12:13:41 |--------------------------------------------------------------------|
Jan 06 12:13:52 => Healthcheck error: Error: connect EHOSTUNREACH 172.18.16.123:3000

I then have to restore the 1.34.3 version for vaultwarden to work again. I have also had to disable auto update. Please note that I know there are two updates from 1.34.3, but both updates have the same connection issue.