Cloudron Forum

@james said in Vaultwarden fails to start after update – DB migration error (SSO): From version Cloudron package version 1.22.2 => Vaultwarden Version 1.34.3 to Cloudron package version 1.23.0 => Vaultwarden Version 1.35.0 Despite my worries and concerns, I never actually hit this problem. Guess I was lucky. But I wonder why? My Vaultwarden started fine after doing that update. And then I immediately updated to the next version without issue too.

@nebulon could you please also approve me? I'd like to cast a vote for GlitchTip

Hello @mrejas and welcome to the Cloudron forum As stated above, this is the Cloudron forum and not the @peertube forum. Since you have stated: @mrejas said in Upgrade to 8.0.1 but interface seems to be 7.x: I have upgraded to 8.0.1 via Docker Compose. I assume, you are not hosting @peertube with Cloudron thus we won't be help you much here. The @peertube forum is here: https://framacolibri.org/c/peertube/38

Hmmm, this last build seems to have some issues. Stand by for a new version.

@jadudm what is the status of your package now ?

Thank you @james We performed these steps and it was successful: Add these lines in env.sh export NODES_EXCLUDE="["ExecuteCommand", "LocalFileTrigger"]" Restarted N8N Performed the test using these steps: (+) - Execute command Execute Once: ON Command: ffmpeg -version Test step Check the OUTPUT - ok (screenshot attached) [image: 1767355746616-screenshot-from-2026-01-02-13-03-11-resized.png]

@paradoxbound if I enable Dane, should I enable MTA-STS?

Another project of the sort is iocaine: https://iocaine.madhouse-project.org/documentation/3/getting-started/containers/ Was wondering if there's any chance to get that running.

@sfeldkamp see https://forum.cloudron.io/post/117766 for aliasDomains in CloudronManifest.json

That seems wrong. Please send a message to support@cloudron.io and the team will check.

@joseph That is correct. Thanks for the feature support.

I've tripled checked (created new key and secret) and it works...

Thanks for looking into it, @james . The situation is the same for me as for @jdaviescoates . Everything works as intended if I enter the address with a trailing slash. The issue only occurs when I don’t include the slash. I run two Yourls instances with the same issue. They are configured the same way. App version: Yourls 1.10.2 Package version: org.yourls.cloudronapp@1.11.2 User management option: Yourls’ own (not Cloudron) Date of installation: 2025-12-31 https://paste.cloudron.io/lixuxaqedo.php

@joseph is this a security enhancement that the Cloudron team can add to a future maintenance release? I would prefer to have Cloudron maintain control of the TURN service so it could enable it based on installed dependencies or leave it off if there are none. Much safer and won't create support issues if someone has disabled TURN ports themselves and then forgets to manage this properly externally.

Hello @luisegundo Have you looked at the official Chatwoot documentation for this? https://developers.chatwoot.com/self-hosted/configuration/features/integrations/instagram-channel-setup If so, have you tried following these steps, and if failing, please describe in detail the steps you have taken to reproduce your issue.