Cloudron Forum

A few minutes ago I tried changing my AWS instance type, and suddenly I am unable to access my cloudron dashboard. I have tried deleting the DNS records from my cloudflare account but it still hasn't resolved the issue.

Vendor: Amazon EC2 Product: t3a.large
Linux: 6.17.0-1013-aws
Ubuntu: noble 24.04
Cloudron: 9.2.0
Execution environment: amazon
Processor: AMD EPYC 7571
BIOS AMD EPYC 7571  CPU @ 2.2GHz x 2
RAM: 8028308KB
Disk: /dev/root        24G
[OK]    Root disk usage is OK (50%)
[OK]    Memory usage is OK (38%)
[OK]    Clock is NTP-synchronized
[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]    IPv4 HTTPS to api.cloudron.io/api/v1/helper/public_ip
[SKIP]  IPv6 HTTPS to api.cloudron.io/api/v1/helper/public_ip — no public IPv6 address
[OK]    IPv4 HTTPS to auth.docker.io/token
[SKIP]  IPv6 HTTPS to auth.docker.io/token — no public IPv6 address
[OK]    IPv4 HTTPS to acme-v02.api.letsencrypt.org
[SKIP]  IPv6 HTTPS to acme-v02.api.letsencrypt.org — no public IPv6 address
[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
[WARN]  Service 'mongodb' is not running (may be lazy-stopped)
[OK]    Service 'mail' is running and healthy
[OK]    Service 'graphite' is running and healthy
[OK]    Service 'sftp' is running and healthy
[OK]    box v9.2.0 is running
[FAIL]  IPv4: could not load https://my.-------------.com
Maybe cloudflare proxying is not working. Delete the domain in Cloudflare dashboard and re-add it. This sometimes re-establishes the proxying
[SKIP]  Dashboard IPv6 reachability — no public IPv6 address
[OK]    Domain -----------.com is valid and has not expired

======== Summary ========
PASS:  25
WARN:  1
FAIL:  1
SKIP:  4

Failures:
  - IPv4: could not load https://my.--------.com

Warnings:
  - Service 'mongodb' is not running (may be lazy-stopped)

@joseph where can I make a request for this? I think it would be really cool if by default this was configured.

@mirotalk-57bab571- thank you so much !!

If the title didn't give it away, I am very new to the whole self hosted scene. I have been looking for an affordable way to create calls between my clients, and Mirotalk ticks all the boxes. However, I have no idea what the difference between the normal one and SFU are. I'm using the normal (works perfectly for me), but I'd like to know if there are any additional features with SFU that I am missing out on.