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
M

maksanse

@maksanse
Unfollow Follow
About
Posts
4
Topics
0
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Broken Update n8n to 2.36.8
    M maksanse
    N8N

    I debugged this on my instance with Claude Code and found what looks like the actual root cause, sharing here in case it helps.

    Root cause (confirmed via docker exec):
    /home/cloudron inside the container is owned by 998:998 with mode 750:

    $ docker exec <cid> ls -lan /home/
    drwxr-xr-x 1 998 998 4096 Aug 7 14:46 .
    drwxr-x--- 1 998 998 4096 Sep 1 10:59 cloudron
    

    But start.sh runs gosu cloudron:cloudron npm install ... and that user is uid=1000(cloudron) gid=1000(cloudron). Since 998:998 isn't in that user's groups and the dir is 750, UID 1000 has zero traversal access to /home/cloudron - it fails on the very first path component, not just on _cacache ownership. That's also why the chown -R 1000:1000 ~/.npm suggestion in the npm error message doesn't actually help here.

    On top of that, /home/cloudron is baked into a read-only image layer: chown as root inside the running container fails with "Read-only file system" on every file under it. So it can't be patched at runtime - it needs a fix in the image build (chown /home/cloudron to 1000:1000 at build time, or align the cloudron user's UID/GID with 998).

    Workaround that avoids touching /home/cloudron entirely, added to env.sh:

    export NPM_CONFIG_CACHE="/run/n8n/custom-node-modules/.npm-cache"
    

    This redirects npm's cache to a path start.sh already chowns to cloudron:cloudron before running the install step. Confirmed working on my instance - install succeeds and n8n starts normally with this in place.

    Hope this saves someone some time, happy for the team to take it from here.


  • Cloudron V7.6.3 : impossible to install or update discourse
    M maksanse
    Discourse

    Installation of Discourse works, but on first login, no email is sent to allow the login (nor received in spam) :
    Google Chrome - Discourse.png

    When trying the resend option, I get this message :
    Google Chrome - Discourse.png

    Is it something you are aware of / related to the issue you corrected ?

    Note : Cloudron emails (Outbound with Amazon SES) work normally and should be accessible to Discourse :
    Google Chrome - Cloudron.png

    Thank you for your help 🙏


  • Cloudron V7.6.3 : impossible to install or update discourse
    M maksanse
    Discourse

    Great ! Thank you for the notice 👍


  • Cloudron V7.6.3 : impossible to install or update discourse
    M maksanse
    Discourse

    Hello,
    I am also waiting to install a Discourse. Any news on this topic ?

    Regards

  • Login

  • Don't have an account? Register

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