@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

@IniBudi said in Discourse Plugin Compability?: https://github.com/discourse/discourse-subscriptions https://github.com/discourse/discourse-reactions Did you get these working?

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 )

+1 on guidance how to uninstall plug-ins from the CLI please

@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?)

@girish said in Possible to make this Discourse Events plugin work on Cloudron?: I think this one is gosu cloudron:cloudron bundle exec rake plugin:install_all_gems ! That seemed to do the job, I think, maybe. The plugin seems to have installed: [image: 1707564502811-f2a7dd2f-3d7e-4a27-9a8e-32b3881cf1e0-image-resized.png] But when I try to click on Events as shown above (and which links to https://bridport.events/admin/events ) I get this: [image: 1707564625874-c9f35c86-a31e-46a5-92fb-84c08a968e61-image.png] ️ Error loading route Caused by plugin 'discourse-events-e0079339aeef4bbe41336a3766e010483478c7374fcb7d7e0574c835848c6e01' (this message is only shown to site administrators) I also note that when running e.g. gosu cloudron:cloudron bundle exec rake posts:rebake I get: fatal: not a git repository (or any of the parent directories): .git I got that a few times during the install process too.

Seems impossible https://meta.discourse.org/t/how-can-i-use-multiple-hostnames/136306 Maybe it would be nice to show this in the App Store, like with badges or something... We chose Discourse over NodeBB for no apparent reason. Maybe it would have made a difference.

@nafets-lesierk see this comment from @IniBudi

@girish Thank you!!

Upstream bug is fixed in Discourse 3.2.0 (latest package)

@nebulon Oh I see, thank you for the explanation.

Thanks for this! Everything Worked on my end!

Okay, I've come one step further. The situation with the domain was apparently caused by Firefox. With Vivaldi there is a successful login again, or an error, depending on the plugins. How unnecessary Actually Discourse only works with one plugin, but the plugin itself does not work: Discourse User Notes With the other tested plugins nothing works, only the error message: "Oops The software powering this discussion forum encountered an unexpected problem...." I only tested two further Plugins: check-list and reactions My test procedure is simply to remove the plugin folder and restart the app. I have no idea whether this is a reliable test.

@nebulon thank you, all sorted now!