@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.

@rosano 2GB is the minimum for a single Discourse app, if you have other apps running as well, it's probably not enough - so yes, more RAM = better. I haven't tried a migration, but installing and setting it up worked fine.

@baslow please see https://forum.cloudron.io/topic/2232/changing-root-account-email-in-fresh-discourse-install/4 for the fix. Basically, run sudo -E -u root bundle exec script/rails console instead. (I am still investigating why the "-u cloudron" does not work, but that should not affect usage of the app.)

@scooke said in Changing root account email in fresh Discourse install: sudo -E -u root bundle exec script/rails console Thanks, it solved the issue

I guess this thread can be marked as "solved". Thanks for help, @girish and @BrutalBirdie

Yikes I had made numerous mistakes and it is working now. I had changed my username from admin and I was including the ruby prompts in the commands. I'm still brand new to Cloudron so hopefully I will have less and better questions in the future. Thanks so much @girish

@girish Awesome thanks.

This should be fixed in the latest package.

@ruihildt They renamed a constant from UnicodeUsernameWhitelistValidator to UnicodeUsernameAllowlistValidator To fix: Edit /app/data/site_settings.yml using file manager and replace UnicodeUsernameWhitelistValidator with UnicodeUsernameAllowlistValidator