This issue has not been solved.

The issue appears to be Cloudron specific and so clearly @Staff need to do something to make Discourse plugins install/ work as expected.

If I can't install the discourse-calendar on my Cloudron Discourse app then the Cloudron Discourse app is completely useless to me 😞

See e.g. https://meta.discourse.org/t/migration-failed-on-update-calendar-plugin-to-last-commit/239437/6

And https://forum.cloudron.io/post/55230

Thanks @girish ! It worked. The changes took effect when I ran the job manually.

@LoudLemur Right, it will be like so:

bundle exec rake plugin:install_gems['discourse-calendar']

New update was 1.17.3-1 and worked perfectly. Thx !

How should I read the doc made by the Cloudron team. 😉

@subven Thank you! I tried again

@robi said in Discourse: initial change email / passphrase problem:

@LoudLemur use a different browser, Firefox may have this issue with certain plugins.

thanks. using a chromium based browser did indeed solve this issue. there is something similar to this if you try and view windy.com in a mozilla browser, the animated wind arrows just disappear and it is streaks of lines across the map.

the whole interent seems to be degenerating into a 'only usable in google products' hell-hole.

@BrutalBirdie said in [SOLVED] Discourse cannot be found:

@LoudLemur
6ecf807e-08b3-4939-bbca-abdfad2a55f0-grafik.png

And whats about that Nice to meet you too we have written to each other in other topic before 😄

and thank you also for your efforts as a member of the Cloudron staff

No worries 👍

Oh, sorry about that! It is terrible to forget somebody who has helped. I think it was because I always thought there were just two staff at Cloudron. I am certainly glad there are more.

@brianb said in Installing More Than One Plugin at a Time:

@jdaviescoates handy? NOPE!

I get it... they need to make $ to keep discourse development (or nodebb) funded and moving forward. But after I got Discourse installed I thought there would be a nice UI for the Plugins... nope.

It's not hard but it is tedious.

Best I've been able to do so far is to go to official Discourse github repo and do a search for "discourse-plugin" which is how they tag MOST plugins.

https://github.com/orgs/discourse/repositories?q=discourse-plugin&type=all&language=&sort=

5c0672d4-090d-4836-82a2-864ca508aa82-image.png

I also keep their plugins page pulled up to know what is available and how they prioritize them.

https://www.discourse.org/plugins#business

@brianb Do you think this should be added to the doc for users to find good plugin sources faster?
And if the answer is yes... would you like to contribute that to the doc? 😉

I think just deleting the plugin directory inside /app/data/plugins and restarting the app will do it.

@luckow said in How to configure LDAP in Discourse?:

My 2 cents for the moment: please add the LDAP addon to this app, because of the plugin and some use cases, where LDAP makes sense.

+1000000

@briankb-0 said in How to Start Discourse with Plugins Disabled?:

@girish I'm sorry, I've already uninstalled and reinstalling the app

no worries, let us know if you hit it again.

@briankb-0 the launcher script only works with Discourse's own packaging stuff i.e if you use https://github.com/discourse/discourse_docker . It does not work in Cloudron, we have our own packaging at git.cloudron.io/cloudron/discourse-app

Generally, you should be able to do everything using rake or bundle exec since Discourse is just a rails app. See https://docs.cloudron.io/apps/discourse for some examples.

@freetommy Are you behind cloudflare by any chance? IIRC, they have a 100MB upload limit.

Ah, it's similar issue. It's not clear from the logs because that file is not in the manifest, I have fixed the package now to show the error.

Processing by CategoriesController#index as HTML Completed 500 Internal Server Error in 22ms (ActiveRecord: 0.0ms | Allocations: 1948) Discourse::Deprecation (Deprecation notice: use_admin_ip_whitelist is deprecated, use the use_admin_ip_allowlist. (removal in Discourse 2.6) At /app/code/lib/site_setting_extension.rb:211:in `public_send`) lib/discourse.rb:860:in `deprecate' app/models/site_setting.rb:241:in `block (2 levels) in <class:SiteSetting>' lib/site_setting_extension.rb:211:in `public_send' lib/site_setting_extension.rb:211:in `block in client_settings_json_uncached' lib/site_setting_extension.rb:210:in `map' lib/site_setting_extension.rb:210:in `client_settings_json_uncached' lib/site_setting_extension.rb:205:in `block in client_settings_json' lib/cache.rb:94:in `fetch' lib/site_setting_extension.rb:204:in `client_settings_json' app/controllers/application_controller.rb:596:in `preload_anonymous_data' app/controllers/application_controller.rb:407:in `preload_json' app/controllers/application_controller.rb:387:in `block in with_resolved_locale' app/controllers/application_controller.rb:387:in `with_resolved_locale' lib/middleware/omniauth_bypass_middleware.rb:71:in `call' lib/content_security_policy/middleware.rb:12:in `call' lib/middleware/anonymous_cache.rb:354:in `call' config/initializers/100-quiet_logger.rb:23:in `call' config/initializers/100-silence_logger.rb:31:in `call' lib/middleware/enforce_hostname.rb:23:in `call' lib/middleware/request_tracker.rb:198:in `call'

@solarsimon mm, usually that should not be required. Did you set the mail from address of the discourse app in the Email view - https://docs.cloudron.io/apps/#mail-from-address ?

App is out now, we have moved the package to use terser instead.

@jagadeesh-s2104 I have fixed the instructions. The u.activate is not needed anymore. BTW, it seems to update the email address already (despite the above error). Just run u.save! .

@brutalbirdie yes, thanks 😊

@murgero @girish
I think I figured it out: I suspect that I changed root's username soon after install, then forgot about it, or did not realize that I did so. I am not sure what happened with the password either, but what I had wasn't working. So I was able to change the email address associated with the (renamed) root account. Then I had to wait a couple days to get a new password while time4vps's occasionally available support opened port 25. It's set up correctly now.

Now that I mentioned it, I will state for the record that time4vps's support is NOT 24/7 like they so proudly state on their homepage. Their hours are GMT +3:
weekdays: 8:30 till 21:30
weekends: 10:00 till 16:30
So if you are on the West Coast of the US you can get support until 11:30 am on weekdays and until 6:30 am on weekends. 😕