Cloudron Forum

@girish Works like a charm. Many thanks for the fix!

I looked through the logs again today and found something conspicuous:

Apr 23 10:57:32 from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/imap/connection.rb:178:in `new_message_ids' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/imap/connection.rb:163:in `new_messages' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/imap/connection.rb:135:in `process_mailbox' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/imap/connection.rb:45:in `wait' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/mailbox_watcher.rb:37:in `block in run' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-client-0.21.1/lib/redis_client/connection_mixin.rb:71:in `call_pipelined': WRONGPASS invalid username-password pair or user is disabled. (redis://redis-19727d9f-cec9-4b73-8b77-3cf41a03008c:6379) (RedisClient::AuthenticationError) <30>1
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-client-0.21.1/lib/redis_client.rb:771:in `block in connect' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-client-0.21.1/lib/redis_client/middlewares.rb:16:in `call' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-client-0.21.1/lib/redis_client.rb:770:in `connect' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-client-0.21.1/lib/redis_client.rb:732:in `raw_connection' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-client-0.21.1/lib/redis_client.rb:697:in `ensure_connected' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-client-0.21.1/lib/redis_client.rb:292:in `call_v' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-5.0.8/lib/redis/client.rb:90:in `call_v' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-5.0.8/lib/redis.rb:152:in `block in send_command' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-5.0.8/lib/redis.rb:151:in `synchronize' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-5.0.8/lib/redis.rb:151:in `send_command' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-5.0.8/lib/redis/commands/strings.rb:95:in `set' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-namespace-1.10.0/lib/redis/namespace.rb:558:in `wrapped_send' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-namespace-1.10.0/lib/redis/namespace.rb:515:in `call_with_namespace' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-namespace-1.10.0/lib/redis/namespace.rb:389:in `block (2 levels) in <class:Namespace>' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/arbitration/redis.rb:41:in `deliver?' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/mailbox.rb:108:in `deliver?' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/imap/connection.rb:178:in `block in new_message_ids' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/imap/connection.rb:178:in `select' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/imap/connection.rb:178:in `new_message_ids' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/imap/connection.rb:163:in `new_messages' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/imap/connection.rb:135:in `process_mailbox' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/imap/connection.rb:45:in `wait' <30>1 
    2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - from /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/gitlab-mail_room-0.0.24/lib/mail_room/mailbox_watcher.rb:37:in `block in run'
Apr 23 10:57:32 2024-04-23 08:57:32,492 INFO exited: mail_room (exit status 1; not expected)
Apr 23 10:57:33 2024-04-23 08:57:33,494 INFO spawned: 'mail_room' with pid 60817

I find that in particular a bit strange:

2024-04-23T08:57:32Z cbe-svpv-http01 19727d9f-cec9-4b73-8b77-3cf41a03008c 1126 19727d9f-cec9-4b73-8b77-3cf41a03008c - /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/redis-client-0.21.1/lib/redis_client/connection_mixin.rb:71:in `call_pipelined': WRONGPASS invalid username-password pair or user is disabled. (redis://redis-19727d9f-cec9-4b73-8b77-3cf41a03008c:6379) (RedisClient::AuthenticationError) <30>1

...or is there a way to run:

sudo gitlab-ctl restart mailroom

?

Does this work for anyone without problems? I would be happy if I could get it to work soon.
I found this post, but I can't do it, because read-only filesystem.
https://gitlab.vibia.com/help/incoming_email/README.md

Enable mail_room in the init script at /etc/default/gitlab:

sudo mkdir -p /etc/default
echo 'mail_room_enabled=true' | sudo tee -a /etc/default/gitlab

Restart GitLab:

sudo service gitlab restart

Verify that everything is configured correctly:

sudo -u git -H bundle exec rake gitlab:incoming_email:check RAILS_ENV=production

Yes, I have set everything up according to the docs. I tried a little more today. I was able to find out that I can check the mails using the command

sudo -u git -H bundle exec rake gitlab:incoming_email:check RAILS_ENV=production

The result is now as follows:

Checking Incoming Email ...

Incoming Email: ... Checking Reply by email ...

IMAP server credentials are correct? ... Checking gitlab@mydomain.xyz
Checking servicedesk@mydomain.xyz
yes
Mailroom enabled? ... no
  Try fixing it:
  Enable mail_room
  For more information see:
  doc/administration/reply_by_email.md
  Please fix the error above and rerun the checks.
MailRoom running? ... can't check because of previous errors

Checking Reply by email ... Finished


Checking Incoming Email ... Finished

I've already tried a few things to activate mail_room, but I just can't do it. Does anyone have any ideas?

Unfortunately, nothing really noticeable from my point of view:

~/gitlab/log# tail -f mail_room_json.log 

I tried a fresh installation today. Unfortunately it didn't work either.

Hello everyone, the service desk of gitlab does not seem to work. I have set up everything according to the docs. The emails arrive, but gitlab does not generate tickets. What could be the reason?

This worked some time ago...but we never actually needed the function. Now we would like to use it...but unfortunately it no longer works.

btw. I just love how easy it is to transfer cloudron to a new server!

It seems like you're right and the new modem is the problem, sorry I forgot to mention that - didn't expect that to be the cause. (Because cloudron has been running very smoothly for over a year now).
Well, I have now moved the server to a VPS. Everything seems to be working there now. I will try to get my cloudron home server up and running again at a later date. Thank you very much for your time and support!

the output is the same everywhere

*   Trying xxx.xxx.xxx.xxx:443...
* connect to xxx.xxx.xxx.xxx port 443 failed: Connection timed out
* Failed to connect to my.domain.com port 443 after 131026 ms: Connection timed out
* Closing connection 0
curl: (28) Failed to connect to my.domain.com port 443 after 131026 ms: Connection timed out

Unfortunately, it's the same story.

Yes, the IP is resolved correctly. But without response. Could it be that this nginx route is no longer working properly?

Ok, I have now deleted the DNS setting, deactivated the IPv6 setting and restarted the server. Now OpenID no longer works for all apps and https://my.domain.com/.well-known/openid-configuration is no longer accessible.
But now I was able to perform a completely fresh installation of Surfer. However, the login via OpenID does not work there either.

The installation actually fails

@nebulon Correct!

OpenID authentication now only does not work with Typebot and Rally.
I have now also tested it with a fresh installation of Typebot:

box:taskworker Task took 66.659 seconds
Mar 14 00:15:47 ' at /app/code/builder/node_modules/.pnpm/openid-client@5.6.4/node_modules/openid-client/lib/helpers/request.js:140:13\n' +
Mar 14 00:15:47 ' at async AuthHandler (/app/code/builder/node_modules/.pnpm/next-auth@4.22.1_next@14.1.0_nodemailer@6.9.3_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/core/index.js:260:26)\n' +
Mar 14 00:15:47 ' at async D (/app/code/builder/apps/builder/.next/server/chunks/524.js:1:7871)\n' +
Mar 14 00:15:47 ' at async Issuer.discover (/app/code/builder/node_modules/.pnpm/openid-client@5.6.4/node_modules/openid-client/lib/issuer.js:143:22)\n' +
Mar 14 00:15:47 ' at async K (/app/code/builder/node_modules/.pnpm/next@14.1.0_@babel+core@7.22.9_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16545)\n' +
Mar 14 00:15:47 ' at async NextAuthApiHandler (/app/code/builder/node_modules/.pnpm/next-auth@4.22.1_next@14.1.0_nodemailer@6.9.3_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/next/index.js:22:19)\n' +
Mar 14 00:15:47 ' at async Object.signin (/app/code/builder/node_modules/.pnpm/next-auth@4.22.1_next@14.1.0_nodemailer@6.9.3_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/core/routes/signin.js:38:24)\n' +
Mar 14 00:15:47 ' at async U.render (/app/code/builder/node_modules/.pnpm/next@14.1.0_@babel+core@7.22.9_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16981)',
Mar 14 00:15:47 ' at async getAuthorizationUrl (/app/code/builder/node_modules/.pnpm/next-auth@4.22.1_next@14.1.0_nodemailer@6.9.3_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/core/lib/oauth/authorization-url.js:70:18)\n' +
Mar 14 00:15:47 ' at async openidClient (/app/code/builder/node_modules/.pnpm/next-auth@4.22.1_next@14.1.0_nodemailer@6.9.3_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/core/lib/oauth/client.js:16:14)\n' +
Mar 14 00:15:47 [next-auth][error][SIGNIN_OAUTH_ERROR]
Mar 14 00:15:47 error: {
Mar 14 00:15:47 https://next-auth.js.org/errors#signin_oauth_error outgoing request timed out after 3500ms {
Mar 14 00:15:47 message: 'outgoing request timed out after 3500ms'
Mar 14 00:15:47 message: 'outgoing request timed out after 3500ms',
Mar 14 00:15:47 name: 'RPError'
Mar 14 00:15:47 providerId: 'custom-oauth',
Mar 14 00:15:47 stack: 'RPError: outgoing request timed out after 3500ms\n' +
Mar 14 00:15:47 }
Mar 14 00:15:47 },

@girish No, but I was just able to find the problem. I tried to activate IPv6 after the update, but forgot to add the AAAA DNS records for the domain. I have now made the entries and it now works.

It looks like https://my.domain.xyz/.well-known/openid-configuration is not accessible, but how can I fix it?

Hello, the login via Cloudron OpenID no longer works for all apps since I updated to V7.7.0. I have already tried several things, reinstalled apps and now also reinstalled the entire server and restored it from the backup. What else can I do?

The following apps are affected:

• Matomo (Unexpected response from the OAuth service.)
• Typebot
• Gitea (/user/oauth2/cloudron for xxx.xxx.xxx.xxx:0, 500 Internal Server Error)
• Rallly

All apps are up to date.