Cloudron Forum

Thank you @joseph and @james for coming to the rescue so quickly.

I have no idea what happened, but I reapplied all my firewall rules (which had not been reconfigured) and restarted the mail service (from the system->services menu, where the mail service was had a red light), and suddenly things worked again. The mail log window has started spewing out log entries like the ones I paste below, but that is perhaps normal? There are tons of these, I only pasted a few of them.

Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:04 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:05 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog
Aug 12 12:09:06 [GET] /eventlog

Hello

Something serious has happened to my Cloudron. I'm not exactly sure about timing (I've been away for family reasons), but my mail clients cannot connect to the Cloudron mail server at all. What's worse, I cannot connect to the SSH service of my Cloudron. It gives "connection refused", so I cannot run the cloudron-support --troubleshoot command.

What are my options? Any way to fix this?

Update: Here's the logs:

2026-08-12T08:25:44Z setup_fts: fts is disabled in config
2026-08-12T08:25:44Z setup_dovecot: Changing ownership
2026-08-12T08:25:45Z setup_haraka: Copying config template
2026-08-12T08:25:45Z setup_haraka: removing any 0 length queue files
2026-08-12T08:25:45Z setup_spamd: Changing ownership
2026-08-12T08:25:45Z Starting supervisor
2026-08-12T08:25:45Z 2026-08-12 08:25:45,765 INFO Included extra file "/etc/supervisor/conf.d/dovecot.conf" during parsing
2026-08-12T08:25:45Z 2026-08-12 08:25:45,766 INFO Included extra file "/etc/supervisor/conf.d/haraka.conf" during parsing
2026-08-12T08:25:45Z 2026-08-12 08:25:45,766 INFO Included extra file "/etc/supervisor/conf.d/mail-service.conf" during parsing
2026-08-12T08:25:45Z 2026-08-12 08:25:45,766 INFO Included extra file "/etc/supervisor/conf.d/redis.conf" during parsing
2026-08-12T08:25:45Z 2026-08-12 08:25:45,766 INFO Included extra file "/etc/supervisor/conf.d/solr.conf" during parsing
2026-08-12T08:25:45Z 2026-08-12 08:25:45,766 INFO Included extra file "/etc/supervisor/conf.d/spamd.conf" during parsing
2026-08-12T08:25:45Z 2026-08-12 08:25:45,766 INFO Included extra file "/etc/supervisor/conf.d/tika.conf" during parsing
2026-08-12T08:25:45Z 2026-08-12 08:25:45,766 INFO Set uid to user 0 succeeded
2026-08-12T08:25:45Z 2026-08-12 08:25:45,774 INFO RPC interface 'supervisor' initialized
2026-08-12T08:25:45Z 2026-08-12 08:25:45,774 CRIT Server 'inet_http_server' running without any HTTP authentication checking
2026-08-12T08:25:45Z 2026-08-12 08:25:45,775 INFO supervisord started with pid 1
2026-08-12T08:25:46Z 2026-08-12 08:25:46,779 INFO spawned: 'dovecot' with pid 64
2026-08-12T08:25:46Z 2026-08-12 08:25:46,787 INFO spawned: 'haraka' with pid 65
2026-08-12T08:25:46Z 2026-08-12 08:25:46,794 INFO spawned: 'mail-service' with pid 66
2026-08-12T08:25:46Z 2026-08-12 08:25:46,798 INFO spawned: 'redis' with pid 67
2026-08-12T08:25:46Z 2026-08-12 08:25:46,808 INFO spawned: 'spamd' with pid 68
2026-08-12T08:25:46Z 67:C 12 Aug 2026 08:25:46.915 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
2026-08-12T08:25:46Z 67:C 12 Aug 2026 08:25:46.915 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2026-08-12T08:25:46Z 67:C 12 Aug 2026 08:25:46.915 * Redis version=8.4.0, bits=64, commit=00000000, modified=1, pid=67, just started
2026-08-12T08:25:46Z 67:C 12 Aug 2026 08:25:46.915 * Configuration loaded
2026-08-12T08:25:46Z 67:M 12 Aug 2026 08:25:46.918 * Increased maximum number of open files to 10032 (it was originally set to 1024).
2026-08-12T08:25:46Z 67:M 12 Aug 2026 08:25:46.918 * monotonic clock: POSIX clock_gettime
2026-08-12T08:25:46Z 67:M 12 Aug 2026 08:25:46.934 * Running mode=standalone, port=6379.
2026-08-12T08:25:46Z 67:M 12 Aug 2026 08:25:46.944 * Server initialized
2026-08-12T08:25:46Z 67:M 12 Aug 2026 08:25:46.945 * Ready to accept connections tcp
2026-08-12T08:25:46Z Warning: fd limit (ulimit -n) is lower than required under max. load (1024 < 1500), because of default_client_limit
2026-08-12T08:25:47Z loaded TLD files:
2026-08-12T08:25:47Z 1=1436
2026-08-12T08:25:47Z 2=7838
2026-08-12T08:25:47Z 3=3768
2026-08-12T08:25:47Z loaded 10156 Public Suffixes
2026-08-12T08:25:47Z Using iconv-lite only. To support rare encodings: npm install iconv
2026-08-12T08:25:47Z 2026-08-12 08:25:47,970 INFO success: dovecot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-08-12T08:25:47Z 2026-08-12 08:25:47,970 INFO success: haraka entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-08-12T08:25:47Z 2026-08-12 08:25:47,970 INFO success: mail-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-08-12T08:25:47Z 2026-08-12 08:25:47,970 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-08-12T08:25:47Z 2026-08-12 08:25:47,970 INFO success: spamd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-08-12T08:25:48Z Mail service endpoint listening on http://:::3000
2026-08-12T08:25:54Z loglevel: INFO
2026-08-12T08:25:54Z log format: DEFAULT
2026-08-12T08:25:54Z Starting up Haraka version 3.1.4
2026-08-12T08:25:54Z [INFO] [-] [plugins] loading delay_deny
2026-08-12T08:25:54Z [INFO] [-] [plugins] loading dns-list
2026-08-12T08:25:54Z [INFO] [-] [plugins] loading helo.checks
2026-08-12T08:25:54Z [INFO] [-] [plugins] loading headers
2026-08-12T08:25:54Z [INFO] [-] [plugins] loading tls
2026-08-12T08:25:54Z [INFO] [-] [core] loading tls.ini
2026-08-12T08:25:54Z [INFO] [-] [plugins] loading spf
2026-08-12T08:25:54Z [INFO] [-] [plugins] loading cloudron
2026-08-12T08:25:54Z [INFO] [-] [plugins] loading rcpt_to.in_host_list
2026-08-12T08:25:54Z [INFO] [-] [plugins] loading dkim
2026-08-12T08:25:54Z [INFO] [-] [plugins] loading spamassassin
2026-08-12T08:25:54Z [INFO] [-] [plugins] loading queue/smtp_forward
2026-08-12T08:25:54Z [INFO] [-] [plugins] loading limit
2026-08-12T08:25:54Z [NOTICE] [-] [server] Listening on [::0]:2525
2026-08-12T08:25:54Z [INFO] [-] [server] getting SocketOpts for SMTPS server
2026-08-12T08:25:54Z 2.0.0.127.zen.spamhaus.org. -> Error: queryA ECONNREFUSED 2.0.0.127.zen.spamhaus.org.
2026-08-12T08:25:54Z [INFO] [-] [dns-list] will re-test list zones every 30 minutes
2026-08-12T08:25:54Z [INFO] [-] [server] Creating TLS server on [::0]:2465
2026-08-12T08:25:54Z [NOTICE] [-] [server] Listening on [::0]:2465
2026-08-12T08:25:54Z [NOTICE] [-] [server] Listening on [::0]:2587
2026-08-12T08:25:54Z [INFO] [-] [cloudron] Initializing queue server on port 6000
2026-08-12T08:25:54Z [INFO] [-] [limit] connected to redis://127.0.0.1:6379/4
2026-08-12T08:25:54Z [INFO] [-] [outbound/queue] Loading outbound queue from /app/data/haraka-queue
2026-08-12T08:25:54Z [INFO] [-] [outbound/queue] Loading the queue...
2026-08-12T08:25:54Z [INFO] [-] [outbound/queue] [pid: undefined] 0 files in my delivery queue
2026-08-12T08:25:54Z [INFO] [-] [outbound/queue] [pid: undefined] 0 files in my load queue
2026-08-12T08:25:54Z [INFO] [-] [outbound/queue] [pid: undefined] 0 files in my temp fail queue

@nebulon said:

I added the path info directive to test this, but the result is the same. Can't get past any auth there using the Authorization header. The path info is shown (I think correctly) in the debug logs though:

[PATH_INFO] => /accounts/ClientLogin/

I am also no php developer but it seems the auth part of the plugin would be unrelated to that at https://github.com/eric-pierce/freshapi/blob/master/api/greader.php#L39

It's been a while, and Cloudron has updated to Cloudron 9. Any chance that this upgrade makes installing this plugin any easier? I've tried myself, but haven't succeeded, but maybe someone smarter than me might figure out a way? It's still a plugin that would future proof TTRSS and be very useful, I believe.

There are setup instructions here: https://github.com/eric-pierce/freshapi#non-official-docker-based-installs and a discussion with a new post on permissions here: https://github.com/eric-pierce/freshapi/issues/7#issuecomment-3328543401

If anyone can solve this, I'll be very happy.

Thank you!

@robi I believe that's because the firewall drops the packages. So Google's servers just don't receive a response (timeout).

odie said:

Hello @james and @robi
Thank you for your follow-ups. I will try to clarify.

My Cloudron doesn't accept incoming emails from Google/Gmail. The e-mail bounces back to Google (Gmail) instead of being delivered.

I included the n8n logs, as they were done on a workflow I have setup using the Gmail node, and where I set both a Gmail and my Cloudron instance as recipients. The mail was received by my Gmail account, but was undelivered to my Cloudron box.

I will try to simplify: Mail sent from Gmail times out - it never reaches my Cloudron box at all.

Yesterday evening, I was able to test sending e-mails from Live (Microsoft) and Proton to my Cloudron box, and both of these go through. So it seems it is only mail from Gmail that my Cloudron box refuses to accept.

The "extra weird" thing is that, for my outgoing e-mails, I use Google's servers as outgoing SMTP. Despite this, e-mails sent with my Cloudron box are received by the Cloudron box, but not when they are sent from a Google account (this applies both to e-mails sent from Google's Gmail service and from Google hosted Workspace accounts).

It seems something on my Cloudron box is refusing to accept mail sent from Google.

Is there a way to reset Cloudron's spam filter training? For testing purposes, I have already disabled Spamhouse (Mail ACL), and there are 0 addresses on the blocklist in my spam filtering.

Thank you very much for providing assistance!

I managed to figure it out. The problem wasn't Cloudron related. I have a firewall in front of the Cloudron that is "learning", and it has at some time decided to pick up (and block) traffic from Google's servers on port 25. Once I fixed that, I received the emails.

Thank you for all your attempts at helping, and apologize for making you think about issues that I should have discovered earlier (I've tried fixing it on my Cloudron box for more than a week, and it just occurred to me now that the solution might exist elsewhere...).

Hello @james and @robi
Thank you for your follow-ups. I will try to clarify.

My Cloudron doesn't accept incoming emails from Google/Gmail. The e-mail bounces back to Google (Gmail) instead of being delivered.

I included the n8n logs, as they were done on a workflow I have setup using the Gmail node, and where I set both a Gmail and my Cloudron instance as recipients. The mail was received by my Gmail account, but was undelivered to my Cloudron box.

I will try to simplify: Mail sent from Gmail times out - it never reaches my Cloudron box at all.

Yesterday evening, I was able to test sending e-mails from Live (Microsoft) and Proton to my Cloudron box, and both of these go through. So it seems it is only mail from Gmail that my Cloudron box refuses to accept.

The "extra weird" thing is that, for my outgoing e-mails, I use Google's servers as outgoing SMTP. Despite this, e-mails sent with my Cloudron box are received by the Cloudron box, but not when they are sent from a Google account (this applies both to e-mails sent from Google's Gmail service and from Google hosted Workspace accounts).

It seems something on my Cloudron box is refusing to accept mail sent from Google.

Is there a way to reset Cloudron's spam filter training? For testing purposes, I have already disabled Spamhouse (Mail ACL), and there are 0 addresses on the blocklist in my spam filtering.

Thank you very much for providing assistance!

Hello

I have noticed that I can't receive email from external services (like gmail, office365 etc). I mostly use the email service for own specific things (Cloudron apps), and mail sent via Cloudron's delivery works fine. But mail from external service providers doesn't come through. I've tested sending from both gmail.com and live.com addresses. None work.

I ran the Cloudron troubleshooter, and that tells me everything is ok.

[OK]	node version is correct
[OK]	IPv6 is enabled in kernel. No public IPv6 address
[OK]	docker is running
[OK]	docker version is correct
[OK]	MySQL is running
[OK]	netplan is good
[OK]	DNS is resolving via systemd-resolved
[OK]	unbound is running
[OK]	nginx is running
[OK]	dashboard cert is valid
[OK]	dashboard is reachable via loopback
[OK]	No pending database migrations
[OK]	Service 'mysql' is running and healthy
[OK]	Service 'postgresql' is running and healthy
[OK]	Service 'mongodb' is running and healthy
[OK]	Service 'mail' is running and healthy
[OK]	Service 'graphite' is running and healthy
[OK]	Service 'sftp' is running and healthy
[OK]	box v9.1.5 is running
[OK]	Dashboard is reachable via domain name
[WARN]	Domain my.domainename expiry check skipped because whois does not have this information

Here's the log from an undelivered mail sent from a Google account. I chose this to test an n8n workflow with two mail address recipients, one gmail address and one address for my Cloudron. I know the mail is sent, because I received to email addressed to my gmail account, but the copy sent to my Cloudron domain (self hosted) is undelivered. I have tried to anonymize the headers by removing the mail addresses, domain name and ip address. Let me know if you need these:

Reporting-MTA: dns; googlemail.com
Arrival-Date: Wed, 01 Apr 2026 03:34:41 -0700 (PDT)
X-Original-Message-ID: <CAG-=ztFbapQFcHFM3-5RFk3UNXteT+y-zLURxVg2qt5E3xGjbQ@mail.gmail.com>

Final-Recipient: rfc822; my-e-mail@cloudron-hosted-domain
Action: delayed
Status: 4.4.1
Diagnostic-Code: smtp; The recipient server did not accept our requests to connect. For more information, go to https://support.google.com/mail/answer/7720
[cloudron.domain.address. cloudron.domain.ip: timed out]
Last-Attempt-Date: Thu, 02 Apr 2026 06:07:53 -0700 (PDT)
Will-Retry-Until: Sat, 04 Apr 2026 03:34:41 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1775135213; cv=none;
       d=google.com; s=arc-20240605;
       b=bL/6dDqeqK2qYkXqqe7fYUCBrZ2b0+SmUG0S2EMaOIbX97QvtexoqsyFJRFMZRBViL
        Cxllz7/WqGTLVskzbkErO+t23tScVLypdXOHxWh/DIgy0PJKcodTfjX+LnFy0SBS+kWw
        494rA1ocmKFgS+U+3dFJZ046eLy5bL8sM7bqplCLFzQVyyVBkcjtZOAebsV+E7EgJ/VS
        Fxk/rbxKVWWAeT7m9VTZLY++lEU7qtOG4DLsnnEXaa6cSzez5usyz6RmS8gnk5L6/6j+
        mV5Vk8AZHCvOyaa0ZXf0SXqiKEnv7CvbZWbU8wwMGauvfoaZ5lSuTbFoirP1rAushlq3
        gF1Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605;
       h=to:subject:message-id:date:from:mime-version:dkim-signature;
       bh=hOd3S/vxaC77xcBp+F70rioo4lFCYJ1j1z6r0u3/2LA=;
       fh=xFLExUQpO7iut+1J5YZCxMf6a4gpJhZadTj6ynd8yr4=;
       b=lS2L/KeL3n1HPprQQMYFef4lrIIiyL6TU17RM76kHDYaSmXSndk754HTgEfi2kvmgh
        rfoJs44QsXpejs8rXMNaDtT/HcL8gba5w2W58TiF2rDcNsISpCO1a5S2RTbEKarN9mLE
        pQNsqeCtxO9M25+SqcaoO6lz79zex8FeSV5IrjpiVtOQcRCg6l25rSXYDdbmRO1XhpCQ
        hoS6zpvjQamPmE2bSCBhyvFd2yHZWpzJn5kBcdrQ1EGs4LxTD9X5OkuQMifa2Ren9PxP
        dCAekKNVwZb3CPNEUOpXtkISgLeY5hv714snz8WTKLqynPGV8r6BAd5rqjsLmkiLjWq6
        dH8g==;
       darn=my.domain
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
       d=google.hosted.domain; s=google; t=1775135213; x=1775740013; darn=my.domain;
       h=to:subject:message-id:date:from:mime-version:from:to:cc:subject
        :date:message-id:reply-to;
       bh=hOd3S/vxaC77xcBp+F70rioo4lFCYJ1j1z6r0u3/2LA=;
       b=SHxyZCo8N1GX8ZqRfHY10Z5apx14xqJ7zQUYF/rxBnWvjr0tXDmwzQbLa5vFG//IIH
        Pl9r5NImQRGPgbirVVNd8/3Hbo+LgsROjPqwuu3YukQ3Zlo7pyCxocZNd5D/mTXtPMu/
        AqQnNPczHwFYCtIyLTzVyYgM8WZlQ8tNxk0pPSnem+H0El/oSmJ2mTohcVj3ACFtvjHb
        ECVolIYiIYsWeZpZtUDhDcDzvHqAMUM8Qe/vFeQjEYT7SjchAZjSjb8lkQGim4JJ+r4y
        PDHo3A3YGnxOXkKUm4AavtnRZtIFqCuvv4Pg24D8Ml3hWkINQow48xrOZkyYn5OocMeh
        wFTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
       d=1e100.net; s=20251104; t=1775135213; x=1775740013;
       h=to:subject:message-id:date:from:mime-version:x-gm-gg
        :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
       bh=hOd3S/vxaC77xcBp+F70rioo4lFCYJ1j1z6r0u3/2LA=;
       b=shtb79Z9iseewp554cHd1jfWqOickpNfWnHTnO5IGh0dgko8Nfj/EI8zmaW6UlXSb5
        tnMhx+CE9mas89SCuioq8TpRgOYHarxeF3vdlHqki/cSODNvoP6VbzI5FcCuxHmGjA+i
        bP+L3O5MMuIughyH5zReONBJiKsoMFxdoh0GpCUG+r4Q9Fwkh3iC6eKxr1jN/bKTGofh
        T9K2lBlZIU2g1HkTj5nf+C+azZYRQLFvDCGZwBTYUxo/vkK2/8mJnXaoBoDQ79/zb29o
        l4fLbJQukUmpe25jw4MnWyiTMfSfnBGCXlN0nQIwxFi/Ovl/2AbdQ+ey/b9zmZu/+uDe
        PnYQ==
X-Forwarded-Encrypted: i=1; AJvYcCVHPy6AG3BpmqV4UzUfuT5iuVHFlhDEiw67SG0HVDTL5pTpvx0+RNWxUfbItaHLV9Y48mlgT4UK@my.domain
X-Gm-Message-State: AOJu0YxMaVMWC9yzoma0H7cVT3D5S6wuxAm2z/FXkd/6Yr45xK9cvMHG
	0utzZjeduKK1eXCcYQbbWMkvuNawT7nPJu1kc4YsGzFpbQdXp/i9CqaKkNGHsz2LGWph2ERd6h1
	nu1MIIsmpvBGO2cNDfbkkxFba2JLDKcJJ1Aji1bCfLYZ+CVUCsRxh8R8=
X-Gm-Gg: ATEYQzwjm2u9KIVKbehrz1nlfPFgK9pyVjVxBr0v6w4VuIDgcMdOaclozhRuMBJBb5R
	664/BcRqKYMwgihz+P3kLuwU2C3GuYrMuY2rEZJZ/I8Q/yMry+ex4FOtR7ta9+LAT7OoL6m6vp5
	E3y4HSbSAX3BTPRBkGXmJb/ByPcHYB7xDJSjVsRX1ThrCVvfm2LzZqA/yPxrW6iClEi6MEQkd9x
	EnyB9Z+jr8SZ0kazyUCp5W8L7mv2fXaCEx3xB+EO8KizuXjk44Fj3QxbYNX11b2IUE7X5YyvonQ
	AmLnU8p7
X-Received: by 2002:a05:6512:1388:b0:5a2:b514:4fbb with SMTP id
2adb3069b0e04-5a2c2109806mr1380632e87.11.1775039681610; Wed, 01 Apr 2026
03:34:41 -0700 (PDT)
Received: from 1066260365263 named unknown by gmailapi.google.com with
HTTPREST; Wed, 1 Apr 2026 03:34:40 -0700
Received: from 1066260365263 named unknown by gmailapi.google.com with
HTTPREST; Wed, 1 Apr 2026 03:34:40 -0700
MIME-Version: 1.0
From: oddgeir@google.hosted.domain
Date: Wed, 1 Apr 2026 03:34:40 -0700
X-Gm-Features: AQROBzC58mMCN5sKP30LQKYOrMJIgzCMHAJUt1i5vFiZFe9Vyyf_psEcP_buESA
Message-ID: <CAG-=ztFbapQFcHFM3-5RFk3UNXteT+y-zLURxVg2qt5E3xGjbQ@mail.gmail.com>
Subject: n8n Workflow Failure: Example Workflow
To: my-email@gmail.com, my-e-mail@cloudron-hosted-domain
Content-Type: text/plain; charset="UTF-8"

I plan on trying to troubleshoot tomorrow (I get family over for an Easter gathering now), so any help/tips will be much appreciated.

I did a clean install of n8n and it installed quickly. So something is/was up with my old n8n instance. Not a huge problem, I'll just migrate my workflows to the new and archive the old instance.

@james Installing n8n-nodes-browserless from Settings > Community nodes, clicking Install a community node and pasting n8n-nodes-browserless works fine.

However, when I try to install Playwright the same way (n8n-nodes-playwright), the installation just hangs and n8n stops responding. The only way to get it back to working again, is to restore from backup.

This is what the Cloudron log window shows:

Mar 28 13:54:12 2026-03-28T12:54:12Z
Mar 28 13:54:12 Current working directory: /run/n8n/custom-node-modules
Mar 28 13:54:12 Installing Playwright system dependencies...
Mar 28 13:54:12 Node version: v24.13.1
Mar 28 13:54:12 Operating System: linux
Mar 28 13:54:12 Starting browser setup...
Mar 28 13:54:12 ⚠️ Not running as root. Attempting to install dependencies with sudo...
Mar 28 13:54:12 🐧 Linux detected - checking system dependencies...
Mar 28 13:54:13 playwright@1.58.2
Mar 28 13:54:13 ⠙⠹⠸⠼⠴⠦⠧⠇Need to install the following packages:
Mar 28 13:54:27 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:54:37 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:54:47 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:54:57 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:55:07 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:55:17 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:55:27 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:55:37 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:55:47 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:55:57 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:56:07 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:56:17 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:56:27 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:56:37 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:56:47 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:56:57 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:57:07 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:57:17 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:57:27 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:57:37 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:57:47 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:57:57 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:58:07 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:58:17 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:58:27 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:58:37 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:58:47 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:58:57 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:59:07 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:59:17 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:59:27 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:59:37 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:59:47 => Healthcheck error: AbortError: The operation was aborted
Mar 28 13:59:57 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:00:07 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:00:17 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:00:27 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:00:37 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:00:47 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:00:57 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:01:07 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:01:17 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:01:27 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:01:37 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:01:47 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:01:57 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:02:07 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:02:07 pipeFileToRequest: piped /home/yellowtent/appsdata/4f8054d1-098f-425f-b14d-74e47a9bc4eb/dump.rdb, waiting for response
Mar 28 14:02:07 pipeFileToRequest: piped /home/yellowtent/appsdata/4f8054d1-098f-425f-b14d-74e47a9bc4eb/postgresqldump, waiting for response
Mar 28 14:02:07 pipeFileToRequest: piping /home/yellowtent/appsdata/4f8054d1-098f-425f-b14d-74e47a9bc4eb/dump.rdb
Mar 28 14:02:07 pipeFileToRequest: piping /home/yellowtent/appsdata/4f8054d1-098f-425f-b14d-74e47a9bc4eb/postgresqldump
Mar 28 14:02:07 pipeFileToRequest: response status code 200
Mar 28 14:02:07 pipeFileToRequest: response status code 200
Mar 28 14:02:07 pipeFileToRequest: success
Mar 28 14:02:07 pipeFileToRequest: success
Mar 28 14:02:17 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:02:27 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:02:37 => Healthcheck error: AbortError: The operation was aborted
Mar 28 14:02:47 => Healthcheck error: AbortError: The operation was aborted

Sounds excellent, @james ! I'm guessing several apps could benefit from from having access to Browserless. Looking forward to this arriving in the appstore.

@james Thank you @james! I was under the (wrong) impression that it was already installed (due to it being listed in /app/code/node_modules, thank you so much for clarifying.

Having chromium (for eg. playwright) would probably be a good thing. I can imagine several use cases where a headless web browser could be useful.

It's listed in /app/code/node_modules (both playwright and playwright-core) but I can't find out how to use a Playwright node. Can anyone help?

@girish said:

@rmdes @odie I have updated the app to use symlinks under /app/data/bridges. You can add new bridges there or delete some symlink and add your own.

Thank you! Works excellent!

Reopening this. I suggested this in the community app topic here. @robi suggested this may now be possible to address.

My suggestion was this:

I'd love to see RSSBridge packaged in a way that you could update individual bridges directly from their repo. The official Cloudron app has the bridges in a read only folder. Lots of bridges are updated constantly, while the main app seems to be working without much problems. So as a consequence we don't get the fixed bridges on Cloudron, leading to more and more broken bridges, but with the app itself working as it should.

@robi said:

@odie the package can be adjusted to fix that.. just ask the team by creating a separate post for it

I did a while ago but it wasn't implemented. I can try again my previous suggestion, I can post again in this thread

Sorry for hijacking this topic. I will not post more about this in this topic.

I'd love to see RSSBridge packaged in a way that you could update individual bridges directly from their repo. The official Cloudron app has the bridges in a read only folder. Lots of bridges are updated constantly, while the main app seems to be working without much problems. So as a consequence we don't get the fixed bridges on Cloudron, leading to more and more broken bridges, but with the app itself working as it should.

@froodle said in Stirling v2: How to change password:

Hey creator of Stirling PDF here
We didn't drop it on purpose
We just missed change user password in the migration to V2
The 'missed' feature discussed before was changing another users password that isn't your own
We are adding both in upcoming update

Also we should have roll called as admin and the can manage settings etc as description, on my screen it shows as such, could be a UI bug related to your browser or something else
Are you able to provide a screenshot and extra info for that?

Thank you for adding this pw-change feature. I would still prefer to have a "change password" button on my "Settings->Security" menu. It's a bit weird having to go into the "People" menu, select your own user, and then change the password from there.

Here's the screenshot of the "admin role" title. It appears when you add a user. For me, it's confusing when one role is "user" and the other is a really long text (instead of "admin"):

@james Thank you for pointing to this file. It's incredible to me that in 2025, with all the security issues around, that they decide to drop such a feature. This sounds inherently insecure. Astonishing!

I followed your advice and established a new user and proceeded to delete the old admin user. Thank you for this suggestion.

To other users of this app - they decided to call the admin role "Can manage settings and invite members, with full administrative access" instead of calling it "admin".

Hello

I installed the Stirling PDF v2 package, and I can't find any place to change the admin password.

There are no password change options available anywhere that I can see. Tried on 4 different browsers but no success.

Anyone care to help?

@nebulon Thanks.

I chose to do a restore, since I could manually replace files that were updated/changed during these days.

Edit: will you pull the update? Or should I set my Nextcloud instance to stop auto updating?

I still have two issues remaining, but these have probably been there a long time:

    WebSocket server URL is not configured. Real-time collaboration requires a separate WebSocket server. Basic whiteboard functionality works without it. For more details see the documentation ↗.
    No High-performance backend configured - Running Nextcloud Talk without the High-performance backend only scales for very small calls (max. 2-3 participants). Please set up the High-performance backend to ensure calls with multiple participants work seamlessly. For more details see the documentation ↗.