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

Apps - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. n8n stuck in broken update state after Cloudron/Docker crash

n8n stuck in broken update state after Cloudron/Docker crash

Scheduled Pinned Locked Moved Unsolved Support
1 Posts 1 Posters 8 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V Offline
    V Offline
    Valexico
    wrote last edited by
    #1

    Hi all,

    Following the Docker crash issue described here (cloudron.conf override conflict after Ubuntu/Docker update — solved by removing /etc/systemd/system/docker.service.d/cloudron.conf and rebooting, see https://forum.cloudron.io/topic/15417/solved-cloudron-down-after-ubuntu-docker-update-docker-service-fails-to-start), my Cloudron instance is back up but one of my apps is now in a broken state.

    App: n8n
    Current version: 2.16.1

    Problem:

    Cloudron shows n8n as having an available update. However when I try to update, it proposes the same version (2.16.1) and fails with:

    Downgrades are not permitted for apps installed from AppStore or Community. force to override

    I also received this notification:

    "The automatic update of the app at <url> failed: Downgrades are not permitted for apps installed from AppStore or Community. force to override"

    My guess is that the automatic update was triggered during the Docker crash window (17h ago, which matches the timing of the crash), leaving the app metadata in an inconsistent state — Cloudron thinks a newer version was installed, but the actual container never updated properly.

    Questions:

    • What should I do

    Thanks!

    1 Reply Last reply
    0

    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

    With your input, this post could be even better 💗

    Register Login
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

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