Cloudron Forum

Got it, yes it was the token, i made a New one (PAT) and it seems that it works Thanks

From the server: ping -n docker.apehost.de -> works telnet idontexist.apehost.de -> Name or service not known telnet docker.apehost.de -> connection refused docker pull docker.apehost.de/path-to-exisiting-image -> Error response from daemon: Get "https://docker.apehost.de/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers) From my local machine: docker pull docker.apehost.de/path-to-exisiting-image -> works just fine

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

Here the results : zfs list a lot but here are the line corresponding to backup target (each used for different test, never at the same time) admin@truenas[~]$ sudo zfs list NAME USED AVAIL REFER MOUNTPOINT OnlyZpol 649G 2.88T 6.30G /mnt/OnlyZpol OnlyZpol/CloudronBackup 256G 2.88T 256G /mnt/OnlyZpol/CloudronBackup [...] OnlyZpol/UserTst 133G 2.88T 66.4G /mnt/OnlyZpol/UserTst OnlyZpol/UserTst/CloudronBck 66.4G 2.88T 66.4G /mnt/OnlyZpol/UserTst/CloudronBck [...] boot-pool 28.4G 68.5G 96K none cp -aRl /path/to/snapshot /path/to/test-copy I did the test on both backup path i have, works and is quick. myuser@truenas:~$ cp -aRl /mnt/OnlyZpol/UserTst/CloudronBck/snapshot/ /mnt/OnlyZpol/UserTst/CloudronBck/testdir/ myuser@truenas:~$ myuser@truenas:~$ cp -aRl /mnt/OnlyZpol/CloudronBackup/snapshot/ /mnt/OnlyZpol/CloudronBackup/testdir/ myuser@truenas:~$ Current compression is LZ4. I haven't change it to ZSTD yet as previous points. Moreover i'm not sure to understand the "accepting the sshfs path" part. So, with my limited knowledge, i'm unsure my issue come from cross-dataset references. But i will test again without hardlink. EDIT : as expected, same issue, remote copy fail....

That is a good hint, so something is not working reliably with the ldap connection then. Can you check on Server A if you hit any rate-limits? You should see them with journalctl -k | grep CLOUDRON_RATELIMIT_LOG on Server A

@james @joseph i found a potential issue. this only happen to Windows OS where microsoft ID is not connected and System only works with local account

@girish Had the same issue as @frenchybear. GCS fixed worked fine. Thx

https://forum.cloudron.io/topic/15310/spam-acl-whitelist-in-api-but-not-in-gui/

@p44 How I read it is that they designed it for CF, but each CF specific part has an alternative supported set of options, like DBs, from SQLite to Postgres, etc. One implementation idea might be to also package a self-hosted container for Workers, so that all plugins you use across all EmDash sites might live there.

Hello @mgan Your Dolibarr app in cloudron will display that an update is available or update automatically.

Hello @necrevistonnezr We have updated the default config template to reflect the upstream. An app update should be available.