Very small quality of life request for 8.2:
Please ensure these tool tip / help / further reading links open in a new tab or window rather than linking directly to the resource which causes the user to lose any data they've entered into the form/process.
Hi team,
As a brand new user to this forum, I only have permissions to post and reply to the Comentario and Azuracast categories. A post I just made was moved from Comentario to the correct forum (per my request - OpenProject) and I am now unable to reply to it.
@Joseph any ideas on what is wrong with the settings for new users? If you move this topic I will have to create a new one in order to reply so please keep this in Comentario until we're finished troubleshooting and the issue is resolved.
Nice, my eyes send you their appreciation.
There is a post queue system to prevent initial posts from spammers (ask me how I know - my first post went there). Upvotes would help but only if a user can get their post seen in the first place. That makes the Comentario and Azuracast sub-forums a super weird "pre-screening" choice for customers who have just joined the Cloudron community.
@girish Yep, exactly that. AnyType and Appflowy are growing in popularity. Would be nice to see them 
@Joseph yep, I've managed to resend the verification email by "changing" my email to the same email address and it appears I now have access and correct permissions. That means for unverified users, they still have access to your two most recent forum additions Comentario and Azuracast. Thanks for your help!
Out of curiosity what constitutes an app being selected or not? 27 upvotes (at time of writing), a lot of engagement and views, clearly a very good fit for the Cloudron platform (which already has Baserow, Nocodb, Directus etc).. When a platform already has Docker support does that make it more or less difficult to get it onto Cloudron? I would assume it is easier?
Just a heads up that the documentation for Comentario is named Commento:
That's interesting. When I initially couldn't post I did go to my settings to see if my account wasn't verified but there was nothing to say it wasn't. I just tried to click the link in my email (it was sitting alongside several other Cloudron emails) but it has timed out / expired (says it is invalid). I'm not sure how I resend it to get verified?
+1 also take my upvote for Grist. A solid alternative to Nocodb.
Thanks for your help on this Joseph.
@Joseph I'm using Safari. Which browser are you using?
NOTE: I only have Azuracast and Comentario as options for posting? Please move to the correct forum.
Hi, new Cloudron user here.
I have set up a new instance of Cloudron (8.0) and installed OpenProject (whatever the latest version is served by the App Store). The application itself is working as expected, and SMTP relay is working - so emails are being sent outward.
However, I'm facing a weird issue when I try to test the Inbound Email feature for OpenProject.
I am assuming, based on another post in the OpenProject Cloudron App forum that Cloudron users must use the cron job approach as the OpenProject Docker Daemon approach is referring to OpenProject's Docker image and not Cloudron's.
So assuming cron is the correct approach, I'm running a script which I've set up by attempting to follow the documentation here:
https://www.openproject.org/docs/installation-and-operations/configuration/incoming-emails/
Essentially the script is:
bundle exec rake redmine:email:receive_imap host='imap.gmail.com' username='test_user' password='password' port=993 ssl=true ssl_verification=true allow_override=type,project project=test_project
When I test this via the OpenProject App Terminal, I get the error shown at the below. Assuming maybe it was a permission/terminal issue, I attempted to run it via a cron job that referenced an executable script to see if that worked instead. Same error. In fact, any rake commands via the terminal will generate this "Listen is not part of the bundle" error.
Jul 16 02:01:32 => Checking Inbox
Jul 16 02:01:40 172.18.0.1 - - [15/Jul/2024:14:01:40 +0000] "GET / HTTP/1.1" 301 945 "-" "Mozilla (CloudronHealth)"
Jul 16 02:01:45 rake aborted!
**Jul 16 02:01:45 Gem::LoadError: listen is not part of the bundle. Add it to your Gemfile. (Gem::LoadError)**
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/activesupport-7.1.3.4/lib/active_support/evented_file_update_checker.rb:3:in `<top (required)>'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/zeitwerk-2.6.15/lib/zeitwerk/kernel.rb:34:in `require'
Jul 16 02:01:45 /app/code/config/environments/development.rb:43:in `block in <top (required)>'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/railtie.rb:257:in `instance_eval'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/railtie.rb:257:in `configure'
Jul 16 02:01:45 /app/code/config/environments/development.rb:31:in `<top (required)>'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/zeitwerk-2.6.15/lib/zeitwerk/kernel.rb:34:in `require'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/engine.rb:568:in `block (2 levels) in <class:Engine>'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/engine.rb:567:in `each'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/engine.rb:567:in `block in <class:Engine>'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/initializable.rb:32:in `instance_exec'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/initializable.rb:32:in `run'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/initializable.rb:61:in `block in run_initializers'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/initializable.rb:50:in `each'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/initializable.rb:50:in `tsort_each_child'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/initializable.rb:60:in `run_initializers'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/application.rb:426:in `initialize!'
Jul 16 02:01:45 /app/code/config/environment.rb:33:in `<top (required)>'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/zeitwerk-2.6.15/lib/zeitwerk/kernel.rb:34:in `require'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/application.rb:402:in `require_environment!'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/railties-7.1.3.4/lib/rails/application.rb:588:in `block in run_tasks_blocks'
Jul 16 02:01:45 /app/code/vendor/bundle/ruby/3.3.0/gems/rake-13.2.1/exe/rake:27:in `<top (required)>'
Jul 16 02:01:45 /root/.rbenv/versions/3.3.2/bin/bundle:25:in `load'
Jul 16 02:01:45 /root/.rbenv/versions/3.3.2/bin/bundle:25:in `<main>'
Jul 16 02:01:45 Tasks: TOP => redmine:email:receive_imap => environment
Jul 16 02:01:45 (See full trace by running task with --trace)
I am not at all familiar with Ruby / GEM Package management and it seems it may be related to the Ruby production/development environment setting somewhere? I am a little bit lost on how to troubleshoot this issue.
You can reproduce the issue by simply typing into the OpenProject terminal:
rake redmine:email:receive_imap or bundle exec rake redmine:email:receive_imap
Assistance would be appreciated.
Thanks Robi. This issue is pretty specific so I'm looking for other Cloudron users to check their Wordpress (Developer) instances (under the Site Health panel) to see if this issue is isolated to my instance or not.
@girish could you or someone please move this to the OpenProject forum?
Also worth noting this is Cloudron running on Ubuntu 24.04 LTS (not sure if that helps).
The original post I'm referencing is: https://forum.cloudron.io/topic/10640/incoming-email-functionality
Anyone else find they are getting Loopback / REST API Errors when checking "Site Health" of a fresh WordPress (Developer) instance?
This is from the Site Health report built into Wordpress, which you can find at: /wp-admin/site-health.php?tab
Any ideas on what might be causing this?
Hmm, I have just tested this and there is definitely an issue with this app because while test emails are generated successfully from the OP backend, when you create a new user via OpenProject they are not sent an invitation/link to setup their account.
The test instance of OpenProject I'm using was originally set up to source users from Cloudron User Directory. Could this be part of the conflict?
Ah, I found the solution for anyone else who comes across this issue. I have to register each domain dependent on loopback within the Firewall/Router (in this case a Unifi UDM Pro).
Unifi Settings > Routing > DNS (Tab) > Create Entry
I had done this previously, but only for Cloudron (my.domain.com) which points to the same internal address. I haven't done this for any of the other applications that I've installed on Cloudron, and they seem to work and be accessible without issue. However, I'll keep this in mind in case I notice similar issues.
Also note, this change enhanced the performance of Wordpress by at least 10x.
So I've nuked my test instance of OpenProject so that I could relaunch it with app configured users instead of using Cloudron User Directory and I can confirm that emails invites do not go out -- regardless. Sending a test email via the OpenProject back end works - but creating a new user from the backend and sending them an invite doesn't. Manually resending the invitation link also doesn't work (and it doesn't throw an error either).
There is nothing in the logs to indicate there is a problem.
Someone else (not using Cloudron) but using Opensense experienced the same issue here:
https://www.reddit.com/r/OPNsenseFirewall/comments/18cntki/wordpress_site_health_error_using_opnsense_rest/
Router and firewall configuration suggestions here:
https://docs.opnsense.org/manual/how-tos/nat_reflection.html
Cloudron recommendations around hair-pinning:
https://blog.cloudron.io/installing-cloudron-on-a-home-server/
As the Wordpress instance is within a container within Cloudron and not on a physical device in my network, I'm not really sure how to proceed given every other website/instance hosted by Cloudron seems to be working as it should. I'm mindful this could be an error that isn't being reported or showing signs in other applications so I am interested in resolving it if I can.
Cloudron Configuration
IPv4: Static Public IP : X (detected) [1:1]
IPv6: Disabled
Firewall
Blocked IPs & Ranges 0 IP(s) blocked
Trusted IPs & Ranges 0 IPs trusted
Dynamic DNS: Disabled
Network configuration:
Domain A/B/C/D -> Static IP -> Router & Firewall -> Port Forward 80/443 -> Cloudron -> Wordpress Instance
Any thoughts or recommendations?