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. Announcements
  3. Cloudron 3.3 released

Cloudron 3.3 released

Scheduled Pinned Locked Moved Announcements
17 Posts 7 Posters 3.6k Views 8 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.
  • girishG Offline
    girishG Offline
    girish
    Staff
    wrote on last edited by
    #1

    Cloudron 3.3 is now available for all. You can read more in our blog post.

    Highlights:

    • Ubuntu 18.04 Support
    • Cloudflare HTTP Proxy Support
    • Exoscale SOS backup regions
    • New events for domains, certs, mailbox activities
    • Dynamic DNS
    1 Reply Last reply
    1
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      Instructions on how to upgrade to Ubuntu 18.04 is here - https://cloudron.io/blog/2018-11-26-upgrading-to-bionic.html

      1 Reply Last reply
      2
      • necrevistonnezrN Offline
        necrevistonnezrN Offline
        necrevistonnezr
        wrote on last edited by
        #3

        @girish
        The instructions read

        Accept running an additional ssh deamon at port 1022

        I think it's therefore necessary to execute

        iptables -I INPUT -p tcp --dport 1022 -j ACCEPT
        

        before running the upgrade as suggested by the Ubuntu release updater, since Cloudron blocks this port via iptable by default (?).

        necrevistonnezrN 1 Reply Last reply
        0
        • necrevistonnezrN necrevistonnezr

          @girish
          The instructions read

          Accept running an additional ssh deamon at port 1022

          I think it's therefore necessary to execute

          iptables -I INPUT -p tcp --dport 1022 -j ACCEPT
          

          before running the upgrade as suggested by the Ubuntu release updater, since Cloudron blocks this port via iptable by default (?).

          necrevistonnezrN Offline
          necrevistonnezrN Offline
          necrevistonnezr
          wrote on last edited by
          #4

          Otherwise, the instructions worked great. Just updated my homeserver over SSH from 16.0.4 to 18.0.4.

          Thanks!

          1 Reply Last reply
          0
          • aheltonA Offline
            aheltonA Offline
            ahelton
            wrote on last edited by ahelton
            #5

            @girish How do I update to 3.3? I login to Cloudron and go to Setting and click 'Check for Updates' and nothing happens...? I'm still running 3.2.3 as seen below:

            Capture.PNG

            1 Reply Last reply
            0
            • girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #6

              @ahelton Do you have wallabag or owncloud installed? If so, the update is not available is not available if those apps are installed since the upstream apps are still adding support for newer database versions.

              aheltonA 1 Reply Last reply
              1
              • girishG girish

                @ahelton Do you have wallabag or owncloud installed? If so, the update is not available is not available if those apps are installed since the upstream apps are still adding support for newer database versions.

                aheltonA Offline
                aheltonA Offline
                ahelton
                wrote on last edited by
                #7

                @girish I have Wallabag installed, so that explains it. Thanks.

                1 Reply Last reply
                0
                • girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #8

                  @ahelton Upstream wallabag is close to fixing the issue. You can track it at https://github.com/wallabag/wallabag/pull/3758

                  S 1 Reply Last reply
                  1
                  • girishG girish

                    @ahelton Upstream wallabag is close to fixing the issue. You can track it at https://github.com/wallabag/wallabag/pull/3758

                    S Offline
                    S Offline
                    saglagla
                    wrote on last edited by
                    #9

                    I've seen that the isssue was merged. The update will be deployed soon ?
                    Still in 3.2.3 @girish 🙂

                    1 Reply Last reply
                    0
                    • girishG Offline
                      girishG Offline
                      girish
                      Staff
                      wrote on last edited by
                      #10

                      @saglagla https://github.com/wallabag/wallabag/issues/3739 also needs to be fixed. It looks like only wallabag 3.4 will support it.

                      S 1 Reply Last reply
                      0
                      • aheltonA Offline
                        aheltonA Offline
                        ahelton
                        wrote on last edited by
                        #11

                        Thanks for keeping us posted, @girish . Will just have to wait for Wallabag 3.4!

                        1 Reply Last reply
                        0
                        • girishG girish

                          @saglagla https://github.com/wallabag/wallabag/issues/3739 also needs to be fixed. It looks like only wallabag 3.4 will support it.

                          S Offline
                          S Offline
                          saglagla
                          wrote on last edited by
                          #12

                          @girish said in Cloudron 3.3 released:

                          @saglagla https://github.com/wallabag/wallabag/issues/3739 also needs to be fixed. It looks like only wallabag 3.4 will support it.

                          But that's mean there is some issue to migrate only ?
                          If I backup Wallabag, destroy it. Upgrade and then re-install, it will work ?

                          Or there is an issue between wallabag and cloudron > 3.2.3 ?

                          1 Reply Last reply
                          0
                          • nebulonN Offline
                            nebulonN Offline
                            nebulon
                            Staff
                            wrote on last edited by
                            #13

                            @saglagla the issue is the Postgresql version. The current wallabag is not yet compatible with the version of Postgres Cloudron > 3.2.3 ships. So reinstallation would not work. This is the reason we block the Cloudron update for instances which have wallabag installed.

                            J 1 Reply Last reply
                            1
                            • nebulonN nebulon

                              @saglagla the issue is the Postgresql version. The current wallabag is not yet compatible with the version of Postgres Cloudron > 3.2.3 ships. So reinstallation would not work. This is the reason we block the Cloudron update for instances which have wallabag installed.

                              J Offline
                              J Offline
                              jk
                              wrote on last edited by
                              #14

                              @nebulon said in Cloudron 3.3 released:

                              (...) The current wallabag is not yet compatible with the version of Postgres Cloudron > 3.2.3 ships. So reinstallation would not work. This is the reason we block the Cloudron update for instances which have wallabag installed.

                              It looks like making Wallabag support a newer version of Postgresql is literally a single-line patch.

                              Might it make sense to carry this as a custom patch for now and be done with it?

                              1 Reply Last reply
                              0
                              • iamthefijI Offline
                                iamthefijI Offline
                                iamthefij
                                App Dev
                                wrote on last edited by
                                #15

                                Looks like the patch that @jk referred to has been merged into Wallabag for 2.4, it would be nice to have this patched in the Cloudron version.

                                I've submitted a Merge Request for the wallabag-app here: https://git.cloudron.io/cloudron/wallabag-app/merge_requests/1

                                Is it possible to get this merged so that we can upgrade Cloudron?

                                1 Reply Last reply
                                0
                                • girishG Offline
                                  girishG Offline
                                  girish
                                  Staff
                                  wrote on last edited by
                                  #16

                                  I think I managed to get it work using the 2.4 branch. Tracking this at https://git.cloudron.io/cloudron/wallabag-app/issues/10

                                  1 Reply Last reply
                                  0
                                  • J Offline
                                    J Offline
                                    jk
                                    wrote on last edited by
                                    #17

                                    Thanks a lot!

                                    1 Reply Last reply
                                    0
                                    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