Cloudron Forum

Today's blog post by Element: "Introducing the ESS Community migration tool" https://element.io/blog/introducing-the-ess-community-migration-tool/

Thanks! Fixed now

@girish said: @imc67 for the moment, it's best not to use allowlist. It's not exposed in UI because it's not really tested or working well. Currently, all it does it add anything in allowlist to SpamAssassin's whitelist_auth - https://spamassassin.apache.org/full/3.4.x/doc/Mail_SpamAssassin_Conf.html . Thanks for sharing this information, though I really would like to see this working officially because currently there is no way to “force allow” emails that gets into spam unneeded.

The well-known is usually served up by the main domain (example.com) so for a start if your nextcloud is installed on a subdomain, the well-known needs to be configured outside this nextcloud instance. So make sure to have an app installed at example.com so it gets routed to Cloudron. Then you can configure this via https://docs.cloudron.io/domains#well-known-locations Though not exactly sure if this nextcloud app would expect the same things as mastodon, but you can try to set the well-known mastodon accordingly, maybe that works. Otherwise we may have to add support for whatever this needs.

Thank you, that would be great!

If the client (outlook) reconnects it would do the authentication again and then we have to validate those credentials at the source, so Server A in your case. But if the mail server is restarting that is some other clue which might actually be the root cause. When that happens do you see anything in the mail service logs why it restarted? Maybe it ran out of memory or did it crash?

Mar 30 09:06:14 [3/30/2026, 16:06:14:098] [Server] Failed to detect IP from http://api.ipify.org 'getaddrinfo EAI_AGAIN api.ipify.org' Mar 30 09:06:14 [3/30/2026, 16:06:14:101] [Server] Failed to detect IP from http://ipinfo.io/ip 'getaddrinfo EAI_AGAIN ipinfo.io' Mar 30 09:06:14 [3/30/2026, 16:06:14:102] [Server] Failed to detect IP from http://ifconfig.me/ip 'getaddrinfo EAI_AGAIN ifconfig.me' Mar 30 09:06:14 [3/30/2026, 16:06:14:103] [Server] Public IP detection failed 'All public IP detection services failed! Please check your network connection' This looks like a network-related issue rather than something specific to MiroTalk. If SFU_ANNOUNCED_IP is not configured, the system will automatically rely on three external services to determine the instance’s public IPv4 address. Is there a firewall or network filter in between that might be blocking traffic? NOTE: As I can see, on Cloudron this is handled by the command in: https://git.cloudron.io/packages/mirotalksfu-app/-/blob/main/start.sh#L39 If it fails (mean not set SFU_ANNOUNCED_IP), MiroTalk SFU uses an internal fallback mechanism that queries three external services in sequence to determine a valid public IPv4 address for the instance.

OK, with the update that log message is gone (in our registry)

@jamie_casper pretty sure this is spam. You are just summarizing posts in all the threads. Can you confirm you are not a bot?

@d43m0n1k_sek Should this post be deleted or should we answer this? The original post is still deleted. Should I restore it? edit: i restored it right now, but unclear if I should be deleting the entire topic.

@micmc it will work in LAMP if you set the HOME environment variable to /app/data, then npm will have a place to write to.