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
  • 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 | Demo | Docs | Install
  1. Cloudron Forum
  2. Umami
  3. Umami update fails

Umami update fails

Scheduled Pinned Locked Moved Solved Umami
3 Posts 2 Posters 631 Views 2 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.
    • darkbenD Offline
      darkbenD Offline
      darkben
      wrote on last edited by
      #1

      Hi,

      i have problem with umami update (2.0.0) this morning

      Capture d’écran du 2022-11-30 10-56-09.png

      I'm on a Cloudron 7.2.5 server with ubuntu 18.04

      Thanks for your help

      Ben

      N 1 Reply Last reply
      0
      • darkbenD darkben

        Hi,

        i have problem with umami update (2.0.0) this morning

        Capture d’écran du 2022-11-30 10-56-09.png

        I'm on a Cloudron 7.2.5 server with ubuntu 18.04

        Thanks for your help

        Ben

        N Offline
        N Offline
        Neiluj
        wrote on last edited by Neiluj
        #2

        @darkben Hi Ben,

        I beleive this to be related to https://forum.cloudron.io/topic/7489/umami-update-1-37-0-package-version-1-6-0-won-t-start-errors-in-logs

        My understanding is that the upstream Umami developer(s) made some breaking changes in their previous release, leading to an automatic update not being possible. Please see the forum post for more details.

        @girish published this breaking changes under app package 2.0 in Cloudron so that no automatic update would take place and thus avoid inoperable application without notice.
        But the underlying situation remains.
        See here: https://forum.cloudron.io/post/52142

        Couple of "solutions" / workaround:

        • uninstall current app and re-install fresh from cloudron app store -> this will lead to previous Umami data / configs / stats being lost and require a new configuration from all sites.
        • install a second umami app package on cloudron, using a different subdomain/app name and run with the two package side by side -> this still requires a new configuration / migration of your sites to the new umami endpoint. However you can keep the stats in the old package (provided that you can revert the changes due to the update attempt).

        Neither are ideal, but it least it gets you running again.

        Hopefully this helps further.

        darkbenD 1 Reply Last reply
        3
        • N Neiluj

          @darkben Hi Ben,

          I beleive this to be related to https://forum.cloudron.io/topic/7489/umami-update-1-37-0-package-version-1-6-0-won-t-start-errors-in-logs

          My understanding is that the upstream Umami developer(s) made some breaking changes in their previous release, leading to an automatic update not being possible. Please see the forum post for more details.

          @girish published this breaking changes under app package 2.0 in Cloudron so that no automatic update would take place and thus avoid inoperable application without notice.
          But the underlying situation remains.
          See here: https://forum.cloudron.io/post/52142

          Couple of "solutions" / workaround:

          • uninstall current app and re-install fresh from cloudron app store -> this will lead to previous Umami data / configs / stats being lost and require a new configuration from all sites.
          • install a second umami app package on cloudron, using a different subdomain/app name and run with the two package side by side -> this still requires a new configuration / migration of your sites to the new umami endpoint. However you can keep the stats in the old package (provided that you can revert the changes due to the update attempt).

          Neither are ideal, but it least it gets you running again.

          Hopefully this helps further.

          darkbenD Offline
          darkbenD Offline
          darkben
          wrote on last edited by
          #3

          @Neiluj many thanks for your help.

          I reinstall another Umami and migrate my content.

          Problem solved

          1 Reply Last reply
          2
          • nebulonN nebulon marked this topic as a question on
          • nebulonN nebulon has marked this topic as solved on
          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