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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Offical apps | Community apps | Demo | Docs | Install
O

oouiy

@oouiy
Unfollow Follow
About
Posts
11
Topics
3
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Peergos on Cloudron - Community Package
    O oouiy
    Community Packages

    Peergos package 1.4.0 is out, with Peergos 1.42.0. The release has several security fixes, so please update soon. Upstream also asks that desktop and mobile clients be updated.

    What changes for Cloudron installs

    • Idle servers use much less CPU and write far less to disk.
    • P2P over QUIC now uses a pure Java implementation (Kwik) instead of a native library. I tested it with IPv6 and with the IPv4-only fallback.
    • The global user directory (PKI) has a new peer ID. Peergos updates its saved settings on the first start, so there's nothing to do.
    • Peergos' address book database now uses SQLite's WAL mode. The VACUUM INTO backups in Cloudron 10.1.6 handle that, so backups work as before.

    Install:

    cloudron install --versions-url https://raw.githubusercontent.com/tripod0429/peergos-app/main/CloudronVersions.json --location peergos.example.com --alias-domains '*.peergos.example.com'
    

  • Peergos on Cloudron - Community Package
    O oouiy
    Community Packages

    This is the right place to ask questions. In practice it can't happen on installs of this package. Sorting only exists to convert blockstores from Peergos versions more than a year old, from before each user got their own folder of blocks. A new server's blockstore is sorted from the moment it's created. Every install of this package is newer than that, so the hook never sees "still being partitioned".

    The wait only matters if someone moves a very old self-hosted Peergos into the app. Even then, the hook waits up to an hour. It backs up after that rather than failing for two reasons: Peergos gives the same answer when sorting failed and won't resume until a restart, so nothing is moving; and a failing hook makes Cloudron abort the whole backup.

    I will probably remove the "still being partitioned" wait in the next release to avoid confusion. I just saw the message appear in my Selenium test suite for the package, so I was overly cautious.


  • Peergos on Cloudron - Community Package
    O oouiy
    Community Packages

    Peergos package 1.3.1 is out. Making Peergos backups reliable took fixes on both sides, so here's a short summary, and thanks to both teams for turning them around so quickly.

    Cloudron

    • Restores never applied the SQLite dumps Cloudron takes during a backup (report). Fixed in 10.1.6: backups snapshot each database with VACUUM INTO, and restores put that snapshot back. The package now requires 10.1.6.

    Peergos

    • #1487 (1.39): a restart during the very first start, for example right after install, no longer leaves a server that can never start again.
    • #1488 (1.39): a new gc command that runs garbage collection inside the running server and waits until it's done.
    • 1.41.0: running with automatic garbage collection turned off no longer breaks mirroring of the global user directory (PKI).

    What this enables in the package

    • Garbage collection now runs in the package's backupCommand just before each backup, instead of on Peergos' 12-hour timer. It can no longer delete blocks while a backup is being copied, and backups taken on Cloudron 10.1.6 or later restore consistently.
    • Also new since 1.2.0: Peergos 1.41, a guard that stops a cloned app from running as a second copy of the same Peergos node, and the wildcard alias is now required, because the HTML viewer and third-party apps use hashed subdomains.

    Install:

    cloudron install --versions-url https://raw.githubusercontent.com/tripod0429/peergos-app/main/CloudronVersions.json --location peergos.example.com --alias-domains '*.peergos.example.com'
    

  • SQLite backups: restore never applies the dump (docker run without -i)
    O oouiy
    Support restore sqlite

    I'm glad it was helpful. In which release is this fix being included?


  • SQLite backups: restore never applies the dump (docker run without -i)
    O oouiy
    Support restore sqlite

    I maintain an unofficial package for Peergos (tripod0429/peergos-app) that lists its databases under localstorage.sqlite.paths. While testing backup and restore, I found that the SQLite dumps Cloudron takes during a backup are never applied on restore. A restored app gets the copies of its live database files that the backup upload made while the app was running.

    What happens

    From box master 21b1abd:

    1. backupSqlite dumps each listed database with sqlite3 <db> .dump before the upload starts services.js#L331-353. That part works as intended.
    2. The upload then copies the whole data directory, including the live database files. The listed paths aren't excluded.
    3. On restore, restoreSqlite replays each dump like this services.js#L363-382:
      docker run --rm ... <app image> sqlite3 <db> < <dump>
      
      There's no -i, so Docker doesn't pass stdin to the container. sqlite3 reads nothing and exits 0, and the restore carries on as if it worked.

    Quick check

    printf 'CREATE TABLE t(x); INSERT INTO t VALUES(42); SELECT x FROM t;\n' | docker run --rm cloudron/base:6.0.0 sqlite3
    printf 'CREATE TABLE t(x); INSERT INTO t VALUES(42); SELECT x FROM t;\n' | docker run --rm -i cloudron/base:6.0.0 sqlite3
    

    On my Cloudron server (Docker 29.6.2), the first command prints nothing and exits 0. The second prints 42. Podman 5.8.7 behaves the same way.

    Adding -i alone isn't enough

    The live database is already in the restored data, so every CREATE TABLE in the dump fails and sqlite3 exits 1. Cloudron's shell helper turns any non-zero exit into an error (shell.js#L58-84), so with only -i added, every restore of an app with sqlite.paths would fail. If that error were ignored instead, tables without a unique key would get duplicate rows:

    $ sqlite3 live.db "CREATE TABLE notes (body text); INSERT INTO notes VALUES ('one');"
    $ sqlite3 live.db .dump > dump.sql
    $ sqlite3 live.db < dump.sql; echo "exit $?"
    Parse error near line 3: table notes already exists
    exit 1
    $ sqlite3 live.db "select count(*) from notes;"
    2
    

    Why it matters

    For most apps a live copy is close enough, which is probably why this hasn't come up. But:

    • A database being written while it's copied can come back corrupted, which is what the dumps are there to prevent.
    • In WAL mode, the database and its -wal file are copied at different moments.
    • Apps that keep files next to their database can get rows pointing to files the upload had already passed.

    Suggested fix

    • In restoreSqlite, pass -i to docker run and replay each dump into a new file instead of the restored copy. Once the replay succeeds, move the new file over the database and delete any -journal, -wal or -shm file left from the live copy.
    • Optionally, leave the listed paths out of the upload, since the dumps replace them. That also avoids uploading every database twice.

  • Peergos on Cloudron - Community Package
    O oouiy
    Community Packages

    Updated to Peergos 1.38.0 (package 1.1.0). It should show up as an update in your dashboard.

    • App tiles in the newsfeed, a built-in address book, and the web UI is now on Vue 3
    • Login attempts are now rate limited
      If you added the app subdomains one by one instead of using a wildcard, make sure address-book.<app hostname> (e.g. address-book.peergos.example.com) is one of them
    • On servers without IPv6, P2P now listens on QUIC as well as TCP

    Upstream release notes: https://github.com/Peergos/web-ui/releases/tag/v1.38.0


  • Peergos on Cloudron - Community Package
    O oouiy
    Community Packages

    TL;DR: Peergos is a private, end-to-end encrypted, peer-to-peer platform for file storage, sharing and social, now packaged for Cloudron as a community app. Requires Cloudron 10.0 or later. Unofficial and community-maintained, not endorsed by Peergos or Cloudron; the packaging was written with the help of Claude.

    Links

    šŸ  Project homepage: https://peergos.org
    šŸ“– Docs: https://book.peergos.org
    šŸ“¦ Upstream repo: https://github.com/Peergos/Peergos
    šŸ” Security audits: https://github.com/Peergos/Peergos/tree/master/audits
    🧱 Cloudron package repo: https://github.com/tripod0429/peergos-app

    Why Peergos is different

    Peergos has been in development since 2013 and has had two independent security audits, in 2019 and 2024, with the reports published. Files, folders and posts are encrypted in your browser before they reach the server, so the server only ever stores ciphertext. It is designed to resist surveillance of both your data and your friendship graph. Your identity isn't tied to one server: you can log in through any Peergos instance, and share with and follow people on other servers.

    On top of the encrypted filesystem you get secret links, a calendar, a social feed, private websites, and sandboxed third-party apps.

    Alongside Nextcloud and Seafile

    Peergos doesn't replace them; it fills a different gap. Nextcloud is a broad collaboration suite, and Seafile is fast file sync with optional encrypted libraries. Peergos is end-to-end encrypted by design for everything, including whom you share with, and federates peer-to-peer between servers. Good fit for sensitive files and private sharing next to your existing suite.

    šŸ“„ How to install

    In the App Store, open the Add custom app dropdown (top right), choose Community app, and paste:

    https://raw.githubusercontent.com/tripod0429/peergos-app/main/CloudronVersions.json

    Or with the CLI:

    cloudron install \
      --versions-url https://raw.githubusercontent.com/tripod0429/peergos-app/main/CloudronVersions.json \
      --location peergos.example.com \
      --alias-domains '*.peergos.example.com'
    

    Needs: 2 GB RAM, ports 4001 TCP and UDP reachable from the internet (peer-to-peer), and a wildcard alias for the app's own hostname, e.g. *.peergos.example.com, not *.example.com. The built-in apps (PDF viewer, calendar, editor) and third-party apps load from those subdomains, and the wildcard certificate needs a DNS provider Cloudron can drive.

    First run

    • On first start Peergos prints a single-use signup link in the app logs. Search for signup=true and open it without the :8000 Peergos appends. The first sync with the Peergos network can take a few minutes.
    • No Cloudron single sign-on: Peergos accounts are cryptographic identities that work across servers. New users join through signup links.
    • Settings live in /app/data/env.sh (File Manager, then restart): admin usernames, the default quota for new users (1 GiB unless changed), and more.

    Good to know

    • Backups cover the SQLite databases consistently. Install, backup/restore, location change and updates are covered by an automated browser test on a real Cloudron.
    • Peergos usernames are global across the Peergos network, so choose them like you would an email address.

    šŸ”“ Unlocks

    End-to-end encrypted storage, sharing and social on your own Cloudron, with Cloudron's backups and one-click updates, and a home server for your Peergos identity.

    šŸ› ļø For the Cloudron team: a case for an official app

    I'd love to see Peergos in the official App Store, and I'm happy to hand this package over or co-maintain it. Why I think it's a good fit:

    • Nothing like it in the store. Peergos adds end-to-end encrypted storage, sharing and social, with identities that work across servers. It complements Nextcloud and Seafile rather than competing with them.
    • Healthy upstream. In development since 2013, AGPL-3.0, two published security audits (2019 and 2024), and frequent releases: three in the two weeks before this post.
    • Low maintenance. One JVM process: no supervisor, no database addon, only localstorage with SQLite-aware backups. Java comes from Ubuntu's openjdk-25 package, as in Komga, Metabase and Stirling-PDF. Peergos upgrades its own database schemas on start, so an update is mostly bumping the pinned version and the jar's checksum. start.sh warns in the logs if a new release adds a database that isn't covered by backups yet.
    • Follows the official conventions. cloudron/base:6.0.0 pinned by digest, the /app/pkg layout, checklist items, an AGENTS.md, and a browser test laid out like the official app tests. The helpers use charlie's names, so switching to @cloudron/charlie is one import.
    • Already verified. The full life cycle (install, restart, backup and restore, location change, update from the previous version) passes on a real Cloudron.

    What adoption would involve: a Cloudron-style app id and image name, and screenshots on your CDN.

    One platform wish: Peergos serves its built-in apps from subdomains of the app's hostname, so admins have to add a *.<app hostname> alias by hand after installing. A manifest option for a default wildcard alias would make Peergos work right after install. The other differences are by design: P2P port 4001 must be reachable, and there's no single sign-on, because Peergos accounts are cryptographic identities.


  • deSEC anycast propagation timing out DNS challenge
    O oouiy
    Support desec certificates dns

    Thank you for taking the time to investigate. It seems like there are several tools that have successfully implemented DNS-based Let's Encrypt challenges and DNS-based automation for deSEC.

    If the higher TTLs really are a problem, could it be possible to just restrict the usage of deSEC to wildcard DNS + Certificate usage (wildcard A/AAAA record + DNS challenge for Let's Encrypt)? These records only need to be updated very infrequently if at all. I personally run my cloudron instance behind a VPN, which is why I am unable to use the HTTP based verification.

    deSEC is a very special provider that I think is worth putting the effort into supporting. AFAIK It's the only donation-run/free, European provider with DNSSEC support currently included in Cloudron. Hetzner doesn't support DNSSEC. It's also (likely) one of the most privacy respecting providers available.

    I have also made a post on their forum. Maybe some creative ideas will come about.


  • deSEC anycast propagation timing out DNS challenge
    O oouiy
    Support desec certificates dns

    It essentially cycles like this until the whole task fails. The incorrect value returned in the detail field is always the challenge from the previous challenge cycle despite waiting for DNS propagation. The article I linked mentioned that you might have to wait longer after the your own server notices the propagation, as when Lets Encrypt performs the lookup, it may not have propagated fully yet due to anycast. I think if you just put in a 2 min timer after waitForDns: _acme-challenge.DOMAIN.TLD has propagated, the problem would probably resolve itself.


  • deSEC anycast propagation timing out DNS challenge
    O oouiy
    Support desec certificates dns
    Jan 11 15:32:44 box:dns/waitfordns waitForDns: _acme-challenge.DOMAIN.TLD at ns ns2.desec.org: done
    Jan 11 15:32:44 box:dns/waitfordns isChangeSynced: _acme-challenge.DOMAIN.TLD (TXT) was resolved to 3fMwPROOF1 at NS ns1.desec.io (45.54.76.1). Expecting 3fMwPROOF1. Match true
    Jan 11 15:32:44 box:dns/waitfordns isChangeSynced: NS ns1.desec.io (2607:f740:e633:deec::2) not resolving _acme-challenge.DOMAIN.TLD (TXT): Error: queryTxt ECONNREFUSED _acme-challenge.DOMAIN.TLD. Ignoring
    Jan 11 15:32:44 box:dns/waitfordns waitForDns: _acme-challenge.DOMAIN.TLD at ns ns1.desec.io: done
    Jan 11 15:32:44 box:dns/waitfordns waitForDns: _acme-challenge.DOMAIN.TLD has propagated
    Jan 11 15:32:44 box:cert/acme2 notifyChallengeReady: https://acme-v02.api.letsencrypt.org/acme/chall/999999999/999999999/z99999 was met
    Jan 11 15:32:44 box:shell acme2: openssl rsa -modulus -noout
    Jan 11 15:32:44 box:cert/acme2 sendSignedRequest: using nonce yoRvt02QdRYOJ3f3RG8lRt7w1vP1puMtQ-23m1Ft7KNT_lgifKQ for url https://acme-v02.api.letsencrypt.org/acme/chall/999999999/999999999/z99999
    Jan 11 15:32:45 box:cert/acme2 waitingForChallenge: {"type":"dns-01","url":"https://acme-v02.api.letsencrypt.org/acme/chall/999999999/999999999/z99999","status":"pending","token":"REDACTED"}
    Jan 11 15:32:45 box:cert/acme2 waitingForChallenge: getting status
    Jan 11 15:32:45 box:cert/acme2 sendSignedRequest: using nonce yoRvt02QdMUP6-ljQHBPKYdBsopJcuppLJbX6rfUZtbsXrxSO0A for url https://acme-v02.api.letsencrypt.org/acme/chall/999999999/999999999/z99999
    Jan 11 15:32:46 box:cert/acme2 waitForChallenge: status is "invalid" "{"type":"dns-01","url":"https://acme-v02.api.letsencrypt.org/acme/chall/999999999/999999999/z99999","status":"invalid","validated":"2025-01-11T15:32:45Z","error":{"type":"urn:ietf:params:acme:error:unauthorized","detail":"Incorrect TXT record \"hdcgPROOF2\" found at _acme-challenge.DOMAIN.TLD","status":403},"token":"REDACTED"}"
    Jan 11 15:32:46 box:cert/acme2 Attempt 1 failed. Will retry: Unexpected status when waiting for challenge: invalid
    

  • deSEC anycast propagation timing out DNS challenge
    O oouiy
    Support desec certificates dns

    I'm currently experiencing this issue when using a domain hosted with deSEC. Issuing a certificate fails despite the relevant DNS entries being present. My server waits until the DNS entries are present and then attempts the DNS challenge. At this point, however, Lets Encrypt resolution cannot yet find these entries. Interestingly, on the following attempt cycles, I can see the "proofs" of the previous DNS challenge showing up in the Lets Encrypt API responses of the current challenge in the logs.

    Is there anyway to increase the timeout to min 2 minutes as the forum post suggests?

    Or maybe just a 60 second timeout between the propagation test succeeds and when the DNS challenge is started?

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search