Cloudron Forum

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.

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)

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

This would be great for the demo server to gain insights into how folks use the UI, session replay

Glad it worked out in the end. It is probably not obvious also to use the credentials from the env variables which have IMAP in them....

@firmansi yes, it’s in “in production” for me. Have not used everything because there’s so much that can be done. Currently for me it is : one of my Telegram bot handlers, providing some basic tasks handing invoice downloading from a couple of suppliers who require login and fetch Planning to extend its functionality. Only “issue” is that Searx is too slow for it so I use Brave API for search - cost is pennies.

@Mathieu https://docs.cloudron.io/packaging/ is a good place to get started