Yes, seems doable. First we need to get this Discourse 3.5 update through.

@girish Thanks. Looking forward. Would it be possible to include my little request with the update ? c.f. https://forum.cloudron.io/post/111958

For future users, there is documentation here - https://docs.cloudron.io/packages/discourse/

3.5 is stable now and brings lot's of new features...

Hi @james Do you suggest uninstalling all manually added plugins which will be bundled in the coming Discourse v3.5 ? To do so, I guess one has to delete the repo and rebuild the app ?

@matt-derrick gosu cloudron:cloudron bundle exec script/rails console does not give a rails console? (from your screenshot it does seem like that) . It just hangs is it? It works fine here on my cloudron too. You can try this on the demo cloudron to see how it is supposed to work . https://my.demo.cloudron.io (username/password is cloudron)

Unfortunately I can't tell you preciesly. Once, I did reset the all the users preferences via the console: https://meta.discourse.org/t/reset-default-categories-watching-setting/244930/8 But there was no error message in the dashboard. Otherwise, I didn't do anything of importance. For updates, I think the error message appeared not before 3.4.3 or 3.4.4… Sorry for the vagueness.

Was fixed, is working.

Works on a fresh instal atleast. [image: 1747991044489-9e1fee30-4e00-40af-a521-049548b79e66-image-resized.png]

@bmann I will take care of this and make sure your advanced guide will be added to https://docs.cloudron.io/apps/discourse/#incoming-email-setup Thanks for the already done write-up!

@wrapper this is quite an old issue. Can you create a new post with whatever issue you are facing?

Just to close this topic. With some help of the discourse AI on ask.discourse.com, I could solve the problem. It was not a bug but an entanglement of site settings and user preferences due to the modifications made over time. Solution: https://meta.discourse.org/t/reset-default-categories-watching-setting/244930/8

@joseph Perfect, thank you ! That did the job. And to my surprise, the settings (LibreTranslate API and URL) were still in place !

Confirming that Discourse backup worked properly after updating the app to pick up the 5.0.0 image. Thank you!

The commands below on the discourse Web terminal should get you the rails console. cd /app/code gosu cloudron:cloudron bundle exec script/rails console

This was sorted out on support. Discourse has a database table called javascript_caches which holds on to some old theme assets. Just removing the entries in that table makes the site load again. I got this hint from various threads. I think this was a bug in some old releases. https://github.com/discourse/discourse/pull/16669 is the fix upstream https://meta.discourse.org/t/uncaught-in-promise-error-could-not-find-module-discourse-widgets-search-menu-imported-from-discourse-theme-70-widgets-search-banner/300297 is the browser error https://meta.discourse.org/t/using-safe-mode-to-troubleshoot-issues-with-themes-and-plugins/53504 (there is a /?safe_mode=no_themes,no_plugins )

@cyph3rasi are you using Discourse on Cloudron ? If on Cloudron, you can use the memory limit slider to give the app mmore memory - https://docs.cloudron.io/apps/#memory-limit

@joseph That could be a solution indeed. Though I would need a new server then. And is it possible to migrate easily the existing Discourse users to become users of the new Cloudron instance ? I also came across this now: https://github.com/consideRatio/discourse-sso-oidc-bridge

The Discourse app that eventually installed when I upped the memory to 5.13 GB RAM, but which I've never even opened, just ran out of RAM which just doesn't seem right. (@staff I guess perhaps we should move all these posts from #5 onwards into the Discourse category?)