TURN and MongoDB not staying up on Cloudron

[bbm_noahgilbert]

Only post Cloudron or server issues in this topic. Use the specific app category for app issues.

• Please include a detailed description of the problem. Include screenshots when applicable. - Description below

• Run cloudron-support --troubleshoot on your server and post the output here like this:

root@my:~# cloudron-support --troubleshoot

═══ Host ═══
Vendor: Micro Computer (HK) Tech Limited Product: MS-A2
Linux: 6.8.0-149-generic
Ubuntu: noble 24.04
Cloudron: 10.1.6
Execution environment: none
none
Processor: AMD Ryzen 9 9955HX 16-Core Processor
BIOS AMD Ryzen 9 9955HX 16-Core Processor            Unknown CPU @ 2.5GHz x 32
RAM: 63432812KB
Disk: /dev/mapper/ubuntu--vg-ubuntu--lv  799G

═══ System ═══
[OK]    Root disk usage is OK (17%)
[OK]    Memory usage is OK (20%)
[OK]    Disk I/O on /home/yellowtent (ubuntu--vg-ubuntu--lv, unknown): 1554 MB/s write, iowait 1%
[OK]    Clock is NTP-synchronized
[OK]    node version is correct
Device "bonding_masters" does not exist.
[OK]    IPv6 is enabled in kernel. Public IPv6 address detected
[OK]    docker is running
[OK]    docker version is correct

═══ Networking ═══
[OK]    no incompatible persistent-firewall packages installed
[OK]    DNS is resolving via systemd-resolved
[FAIL]  Unbound is not resolving. However, Outbound DNS requests are not blocked. Investigate output of 'journactl -u unbound'
Using domain server:
Name: 127.0.0.150
Address: 127.0.0.150#53
Aliases: 

Host cloudron.io not found: 2(SERVFAIL)
[OK]    IPv4 HTTPS to api.cloudron.io/api/v1/helper/public_ip
[OK]    IPv6 HTTPS to api.cloudron.io/api/v1/helper/public_ip
[OK]    IPv4 HTTPS to auth.docker.io/token
[OK]    IPv6 HTTPS to auth.docker.io/token
[OK]    IPv4 HTTPS to acme-v02.api.letsencrypt.org
[OK]    IPv6 HTTPS to acme-v02.api.letsencrypt.org
[OK]    netplan is good

═══ Cloudron Platform ═══
[OK]    MySQL is running
[OK]    nginx is running
[OK]    Dashboard cert is valid (68 days remaining, expires Jan 16 11:35:19 2027 GMT)
[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 lazy-stopped (no installed Cloudron app uses the 'mongodb' addon)
[OK]    Service 'mail' is running and healthy
[OK]    Service 'graphite' is running and healthy
[OK]    Service 'sftp' is running and healthy
[OK]    box v10.1.6 is running
[OK]    Dashboard is reachable via IPv4 (https://my.blockbluemedia.com)
[OK]    Dashboard is reachable via IPv6 (https://my.blockbluemedia.com)
[OK]    Domain blockbluemedia.com is valid (200 days remaining, expires 2027-05-28T10:56:59Z)

======== Summary ========
PASS:  32
WARN:  0
FAIL:  1
SKIP:  0

Failures:
  - Unbound is not resolving. However, Outbound DNS requests are not blocked. Investigate output of 'journactl -u unbound'

For troubleshooting tips, see https://docs.cloudron.io/troubleshooting
To share a full diagnostic dump on the forum, run: cloudron-support --send-diagnostics

• Check for any errors in /home/yellowtent/platformdata/logs/box.log - No errors that I can see but happy to provide the file if needed.

For some reason on my Cloudron server, TURN and MongoDB don't stay up and while it appears to not affect my apps that I have, I don't know why they don't stay up on my server.
Running Ubuntu 24.04 with Cloudron 10.1.6

[james]

Hello @bbm_noahgilbert
If none of your installed apps use Turn or MongoDB, Cloudron will suspend the services until they are needed again to save some RAM and CPU performance.

[bbm_noahgilbert]

Ahh, that makes sense...

Thanks for clearing that up @james, was starting to think that there was some issue with my server because of those showing they were offline.

[james]

Hello @bbm_noahgilbert
I will update the Cloudron docs https://docs.cloudron.io/services/ to include this information.
Thanks for bringing this to my attention.