Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content

Support

3.7k Topics 26.5k Posts

Get help for your Cloudron

  • SMTP timeout after updating to 8.3.1

    Solved email smtp relay ipv6
    19
    1 Votes
    19 Posts
    7k Views
    R
    Yeah can confirm, and thanks for the help diagnosing. I wasn't given any advanced notice of the SMTP block, it was hidden in release notes somewhere. This is now unblocked.
  • Unable to detect IPv6. API server (ipv6.api.cloudron.io) unreachable

    Solved networking ipv6
    3
    1 Votes
    3 Posts
    868 Views
    J
    @hakh looks like IPv6 connectivity in your server is not working. Does ping6 ipv6.api.cloudron.io work for you?
  • Email search error

    email fts
    2
    1 Votes
    2 Posts
    607 Views
    avatar1024A
    Hi, did you check this, this and this? I got the similar errors when trying to run the indexing but after a few retry it works. I tried to index email mailbox separately (by running the command inside the rebuild-index.sh for each mailbox separately) and identified which one caused the problem, then I had to open/read the problematic folders with a mail client, and then the index worked. Given this feels like another duplicate, @staff, there might be something up / to improve with how the indexing is handled.
  • Email sending issue (was: URGENT)

    Locked Solved email
    60
    1
    0 Votes
    60 Posts
    22k Views
    J
    Continued at https://forum.cloudron.io/topic/13576/email-sending-issue-again-was-urgent
  • SMTP Issues

    Solved email relay smtp
    13
    1
    1 Votes
    13 Posts
    4k Views
    M
    @BrutalBirdie Ok fixed. The Cloudron did not even show me that. I have fixed the issue now.
  • No question. No error. No mess. Just a thank you for the Cloudron product.

    Solved
    6
    18 Votes
    6 Posts
    2k Views
    girishG
    Flattered Thanks for the appreciation.
  • Restore not possible when mailbox is included in backup

    Solved backup restore mail
    10
    1
    2 Votes
    10 Posts
    4k Views
    robiR
    @nebulon here's what an AI found: Tarball Permissions The tarball contains files with ownership/permissions the process can’t replicate (e.g., root-owned files). Example: Extraction fails when tar.extract preserves original ownership. SELinux/AppArmor Security policies block filesystem operations despite correct permissions. Tar Library Behavior: The tar library (likely tar-fs) might try to preserve file permissions from the tarball. If the tarball contains files owned by root and the app runs as yellowtent, extraction fails unless permissions are ignored. Fix: Modify the code to ignore permissions: javascript const tarStream = tar.extract({ cwd: destinationPath, ignore: () => true }); Debugging Steps Check Permissions: javascript console.log('Source:', fs.statSync(sourcePath).mode.toString(8)); console.log('Dest:', fs.statSync(destinationPath).mode.toString(8)); Ensure Directory Exists: javascript if (!fs.existsSync(destinationPath)) fs.mkdirSync(destinationPath, { recursive: true }); fs.accessSync(destinationPath, fs.constants.W_OK); Add Error Logging: javascript const readStream = fs.createReadStream(sourcePath).on('error', (err) => console.error('Read:', err)); const unzipStream = zlib.createGunzip().on('error', (err) => console.error('Gunzip:', err)); const tarStream = tar.extract({ cwd: destinationPath }).on('error', (err) => console.error('Tar:', err)); Potential Fixes Ignore Tar Permissions: javascript const tarStream = tar.extract({ cwd: destinationPath, ignore: () => true }); Test with Logging: Run the modified code with error handlers. async function tarExtract(sourcePath, destinationPath) { ensureSafePath(sourcePath); ensureSafePath(destinationPath); console.log('Source:', sourcePath, fs.statSync(sourcePath)); console.log('Dest:', destinationPath, fs.existsSync(destinationPath) ? fs.statSync(destinationPath) : 'does not exist'); const readStream = fs.createReadStream(sourcePath) .on('error', (err) => console.error('Read error:', err)); const unzipStream = zlib.createGunzip() .on('error', (err) => console.error('Gunzip error:', err)); const tarStream = tar.extract({ cwd: destinationPath }) .on('error', (err) => console.error('Tar error:', err)); readStream.pipe(unzipStream).pipe(tarStream); await streamPromise(tarStream); } Conclusion The error is likely a mismatch between the Cloudron app’s user permissions and the filesystem.
  • Cannot upload GCP service account key to restore app

    Solved restore gcp
    6
    1 Votes
    6 Posts
    2k Views
    J
    This is fixed in the new UI for Cloudron 9
  • Volume shows no files, although they are there

    Solved volumes filemanager
    2
    1 Votes
    2 Posts
    919 Views
    J
    Usually, the issue here is that the SFTP service is not running . Services -> SFTP -> Restart maybe?
  • Issue with Cloudron Backup via Cloudflare Tunnel to MinIO

    cloudflare backups
    2
    1 Votes
    2 Posts
    1k Views
    nebulonN
    Looks like Cloudflare is interfering here and changing the data in transit? You would have to contact Cloudflare about this, but I have no high hopes that this would get anywhere.
  • Can not connect to CIFS, ports not allowed in iptables

    Solved cifs storagebox
    3
    1 Votes
    3 Posts
    1k Views
    perelinP
    Thx for the hint. Will see what Hetzner support has to say.
  • Network Error with Cloudron Apps - Need Help

    Solved networking dns
    2
    1 Votes
    2 Posts
    871 Views
    J
    @SamGreenwood I would run the troubleshooting tool for a start - https://docs.cloudron.io/troubleshooting/#troubleshooting-tool
  • Only Superadmins can change user roles

    Solved user management
    3
    3 Votes
    3 Posts
    888 Views
    perelinP
    Just recheck... and I can do this. Was 100% it was not possible. Might have been an "between my ears" problem, sry
  • 0 Votes
    20 Posts
    4k Views
    jdaviescoatesJ
    @wmlutz said in Outbound SMTP (Transactional Email) Stopped Working - Invalid login: 535 Authentication failed: @jdaviescoates got it! It was the IP allowlist. Glad to be of assistance @wmlutz said in Outbound SMTP (Transactional Email) Stopped Working - Invalid login: 535 Authentication failed: mailgun's transactional email cost which is cents/mo. I don't think I've ever paid anything yet as I've not yet gone over the 1000 free messages a month or whatever it is...
  • This topic is deleted!

    0
    0 Votes
    0 Posts
    10 Views
    No one has replied
  • can't install cloudron due to unbound issues

    Solved unbound installation
    23
    0 Votes
    23 Posts
    8k Views
    girishG
    @potemkin_ai said in can't install cloudron due to unbound issues: It seems like unbound is only used for SpamHause and during setup. If the setup issue will resorted, only SpamHause issue will remain. It's also used for DNS propagation checks (during app install, change location etc) and also verify validity of DNS records for Let's Encrypt. We cannot rely on caching resolvers because they would cache not found (NXDOMAIN) entries for very long periods of time. The recommendation is to keep all the outbound ports open - https://docs.cloudron.io/security/#outbound-ports .
  • Vulnerabilities in Ingress NGINX

    Solved nginx security
    3
    2 Votes
    3 Posts
    1k Views
    d19dotcaD
    @Kubernetes Yeah this is specific to the Nginx Ingress Controller which runs on Kubernetes. It won’t be related to Cloudron at all since Cloudron doesn’t use Kubernetes. Cloudron won’t be vulnerable to this.
  • Demo Server Glitches

    Solved
    3
    0 Votes
    3 Posts
    1k Views
    robiR
    It did not change earlier, but now hours later it seems to have. All my instances were fine, just the demo server seemed affected like it was possessed by someone
  • 8.3.1 upgrade

    Solved
    12
    1 Votes
    12 Posts
    5k Views
    robiR
    @nebulon I think it's important to highlight how impressive this actually is. A DB upgrade is no small feat for one app, let alone 60-80 apps and multiple DBs that many Cloudrons here run. Then to jump across two DB version upgrades, all while seamlessly restitching everything back up so apps function properly. Traditionally there would be a team of SREs doing this for a week. Yet it happens in a few hours if not minutes. So there will be some red timeout messages and UI glitches while the process is going on (the red messages were waiting for me this AM while the system upgrade happened over night as I left my dashboard tab open), however with some patience and understanding everything comes back up as if by self-healing magic. Sure it could be more polished (how about making a browser refresh after a successful upgrade to clear all the red messages?), but once you know, it's just more important to be in gratitude that it all just works and business continues as usual. I for one appreciate this magic and hence the makers of this wonderful self-hosting system from the time I first met them during a meetup in Silicon Valley, CA. Cloudron gives me TONS of time back, which is also why I can take the time to write about it, run fun experiments, and not have to be stuck troubleshooting standard app deployment woes. Thank you Cloudron & Team for another seamless upgrade and intangibly so much more.
  • Is "Disk Usage" also counting mounted (network) drives?

    Solved disk usage
    4
    1 Votes
    4 Posts
    1k Views
    J
    @perelin the docker usage is reported searately (the second line in your screenshot). It's around 20GB. This seems reasonable. The graphs numbers from du are not accurate when it comes to docker . You have to use docker system df . Looks like the space is being used somewhere else. Did you happen to use another backup location previously ? I guess the only way to find out is to run du on each folder starting from root