It's out now

Closed due to inactivity

@shrey said in SSO for OpenProject: auto-login into OpenProject from Cloudron Dashboard LDAP doesn't support auto-login. You can login with your Cloudron username/password though .

I tried to drop down to the www-data user but no success. root@b1e03a66-bb9e-4808-aecf-68c518fed0d5:/app/code# ../data/tasks-via-email.sh rake aborted! ArgumentError: Missing `secret_key_base` for 'production' environment, set this string with `bin/rails credentials:edit` (ArgumentError) raise ArgumentError, "Missing `secret_key_base` for '#{Rails.env}' environment, set this string with `bin/rails credentials:edit`" ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/application/configuration.rb:519:in `secret_key_base=' /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/application/configuration.rb:503:in `secret_key_base' /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/application.rb:470:in `secret_key_base' /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/application.rb:205:in `block in message_verifiers' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/message_verifiers.rb:132:in `build' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/messages/rotation_coordinator.rb:85:in `block in build_with_rotations' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/messages/rotation_coordinator.rb:85:in `map' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/messages/rotation_coordinator.rb:85:in `build_with_rotations' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/messages/rotation_coordinator.rb:19:in `[]' /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/application.rb:232:in `message_verifier' /run/redmine/vendor/ruby/3.3.0/gems/activerecord-7.2.2.1/lib/active_record/railtie.rb:355:in `block (3 levels) in <class:Railtie>' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:97:in `class_eval' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:97:in `block in execute_hook' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:87:in `with_execution_control' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:92:in `execute_hook' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:62:in `block in on_load' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:61:in `each' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:61:in `on_load' /run/redmine/vendor/ruby/3.3.0/gems/activerecord-7.2.2.1/lib/active_record/railtie.rb:354:in `block (2 levels) in <class:Railtie>' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:94:in `block in execute_hook' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:87:in `with_execution_control' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:92:in `execute_hook' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:78:in `block in run_load_hooks' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:77:in `each' /run/redmine/vendor/ruby/3.3.0/gems/activesupport-7.2.2.1/lib/active_support/lazy_load_hooks.rb:77:in `run_load_hooks' /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/application/finisher.rb:94:in `block in <module:Finisher>' /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/initializable.rb:32:in `instance_exec' /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/initializable.rb:32:in `run' /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/initializable.rb:61:in `block in run_initializers' /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/initializable.rb:60:in `run_initializers' /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/application.rb:435:in `initialize!' /app/code/config/environment.rb:16:in `<top (required)>' /run/redmine/vendor/ruby/3.3.0/gems/zeitwerk-2.7.2/lib/zeitwerk/core_ext/kernel.rb:34:in `require' /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/application.rb:411:in `require_environment!' /run/redmine/vendor/ruby/3.3.0/gems/railties-7.2.2.1/lib/rails/application.rb:559:in `block in run_tasks_blocks' /run/redmine/vendor/ruby/3.3.0/gems/rake-13.2.1/exe/rake:27:in `<top (required)>' /home/cloudron/rbenv/versions/3.3.4/bin/bundle:25:in `load' /home/cloudron/rbenv/versions/3.3.4/bin/bundle:25:in `<main>' Tasks: TOP => redmine:email:receive_imap => environment (See full trace by running task with --trace) root@b1e03a66-bb9e-4808-aecf-68c518fed0d5:/app/code#

Hi @nebulon - thank you! Just confirming after updating, the emails are now being sent.

Given that the rake command arguments need to be tailored to the imap account and one can add more than one such account, the package does now not provide any scripts for this, but as @umnz pasted, adding a custom cron job with the mentioned command for each imap account via the Cloudron dashboard will solve this.

Update: i just did a workaround: i asked another user who has admin privilege to create another user for me. Logged in with new username/pass successfully. I didn't try the method with rail console MANY THANKS AGAIN FOR YOUR SUPPORT!!!

@nebulon Thanks a lot!

Our proposed fix got merged upstream now https://github.com/opf/openproject/pull/11500#pullrequestreview-1156355379

@nothing On Cloudron, all apps use the internal mail server. The internal mail server relays out depending on your relay configuration. Not sure I completely understood your problem. Why are you trying to change the SMTP configuration inside OpenProject ? You shouldn't have to do this.

@jdaviescoates [image: 1661180517854-543b7b4f-fafd-411b-822f-a715d7a681f0-image-resized.png] Bad news: I invested 1/2 hour to find something to hide the banner. Not found

@abargel ha ha, indeed It's mentioned quite casually without more explanation on how to do actually import it.

First thing first, did this solve your issue? @qwinter said in Getting an admin user for openproject: I haven't found anything that would do well as a wiki from the options that we have You don't like the option for wiki apps? https://www.cloudron.io/store/index.html#wiki @qwinter said in Getting an admin user for openproject: it's kinda surprising that the best FOSS can offer is no match to commercial offerings. Nice to hear/read

This is now fixed with latest app package. Existing installations still have to disable it with the previously mentioned psql commandline.

@nebulon yeah I tried reinstalling. It could be a resource issue. I'll investigate further.

@nebulon said in Frequent 500s because of permission denied /app/code/tmp/cache: Oh I see. Since I had access to your instance for fixing the issue anyways, I saw that the app was healthy and running, but the nginx reverse proxy config wasn't correctly updated. This may actually be a bug in Cloudron. The reason likely is that I've changed the app's internal port from 80 to 8000 to not require apache to run as root. To fix this quickly, I've just submitted the location form of the app configure, which triggers a recreation of the reverse proxy files. At least for me the app is now reachable. This explains a lot.

Thank you for sharing. There's a lot to unpack there, especially the postgres stuff. I can see how many users wouldn't know what to do there. Can you expand on all those 'postgres' parts and what to look for? The 'manual migration' may not be needed since the app will do that on restart exiting recovery mode.

This is now fixed with the latest OpenProject app package.