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. WordPress (Developer)
  3. 3.2.0 Update not showing up

3.2.0 Update not showing up

Scheduled Pinned Locked Moved Solved WordPress (Developer)
16 Posts 2 Posters 2.4k 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.
  • humptydumptyH Offline
    humptydumptyH Offline
    humptydumpty
    wrote on last edited by
    #3

    Yep, working now. Thank you!

    1 Reply Last reply
    0
    • humptydumptyH Offline
      humptydumptyH Offline
      humptydumpty
      wrote on last edited by
      #4

      @girish One of my sites gets stuck at "starting" after upgrading to 3.2.0. I reverted to a backup, and manually upgraded WP to 6.3.0 from the WP dashboard after confirming the issue was theme related (needed an upgrade beforehand). The site runs fine until I upgrade the Cloudron WP package to 3.2.0. Thoughts?

      girishG 1 Reply Last reply
      0
      • humptydumptyH humptydumpty

        @girish One of my sites gets stuck at "starting" after upgrading to 3.2.0. I reverted to a backup, and manually upgraded WP to 6.3.0 from the WP dashboard after confirming the issue was theme related (needed an upgrade beforehand). The site runs fine until I upgrade the Cloudron WP package to 3.2.0. Thoughts?

        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #5

        @humptydumpty Can you check in the logs where i gets stuck? I have seen this happen if a site is compromised. Can you check the contents of wp-config.php or wp-include.php before updating? Often, it has a suspcious include line.

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

          @humptydumpty Do you see any message like Error: A foreign object cache drop-in was found. To use Redis for object caching, run: wp redis update-dropin. ?

          humptydumptyH 1 Reply Last reply
          0
          • humptydumptyH Offline
            humptydumptyH Offline
            humptydumpty
            wrote on last edited by humptydumpty
            #7

            Yes, that was one of the things that stood out. There was also something like connection refused that repeated like 50 times. Then, health check failed after 7000 (m)s?

            At first, there was a mention of an error in the theme php file and I got that sorted out. It still refused to start though. My other sites are fine. I'm not using the redis plugin that Cloudron preinstalls on all my sites as I'm using W3TC's redis on some of my sites.

            1 Reply Last reply
            0
            • girishG girish

              @humptydumpty Do you see any message like Error: A foreign object cache drop-in was found. To use Redis for object caching, run: wp redis update-dropin. ?

              humptydumptyH Offline
              humptydumptyH Offline
              humptydumpty
              wrote on last edited by humptydumpty
              #8

              @girish OK, so both sites that are failing use W3TC's Redis feature and not Redis Object Cache. The sites that do use Redis Object Cache updated just fine.

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

                @humptydumpty thanks, I am pushing a fix.

                humptydumptyH 1 Reply Last reply
                0
                • girishG girish referenced this topic on
                • girishG girish

                  @humptydumpty thanks, I am pushing a fix.

                  humptydumptyH Offline
                  humptydumptyH Offline
                  humptydumpty
                  wrote on last edited by
                  #10

                  @girish Great. I was about to try the CLI "wp redis update-dropin" thing. But here's a copy paste in case something else is at play.

                  Aug 10 22:17:09 Connection refused
                  Aug 10 22:17:17 => Healtheck error: Error: Timeout of 7000ms exceeded
                  Aug 10 22:17:27 => Healtheck error: Error: Timeout of 7000ms exceeded
                  Aug 10 22:17:37 => Healtheck error: Error: Timeout of 7000ms exceeded
                  Aug 10 22:17:47 => Healtheck error: Error: Timeout of 7000ms exceeded
                  Aug 10 22:17:50 => Healtheck error: Error: connect EHOSTUNREACH 172.18.19.156:80
                  
                  1 Reply Last reply
                  0
                  • girishG Offline
                    girishG Offline
                    girish
                    Staff
                    wrote on last edited by
                    #11

                    wp redis update-dropin works but this happens because you are using some other object cache. Running that command will disable your current object cache.

                    1 Reply Last reply
                    0
                    • humptydumptyH Offline
                      humptydumptyH Offline
                      humptydumpty
                      wrote on last edited by
                      #12

                      I think I made the switch for performance reasons. It's been a while and I forgot the specifics. Anyway, I'll switch back to Redis Object Cache in the morning.

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

                        @humptydumpty Can you check with the latest package?

                        1 Reply Last reply
                        0
                        • humptydumptyH Offline
                          humptydumptyH Offline
                          humptydumpty
                          wrote on last edited by humptydumpty
                          #14

                          In short, package 3.2.0-2 has no breaking issues but requires manual enabling of Redis and manual updating of WP 6.3. See below for details.


                          Enabling Redis Manually

                          On the W3TC sites, the update installed Redis Object Cache and disabled W3TC's object cache with a message (Object Cache is disabled via filter.). However, Redis wasn't enabled in Redis Object Cache by default, I had to manually do that to get it going.

                          d464a4b1-aa25-4b78-bf84-ce37ea5cee91-image.png

                          85b811c8-3d9e-4d19-822c-7ef12bf7df81-image.png


                          Updating WP to 6.3 Manually

                          I have a staging site (non-W3TC, but is using that problematic theme I mentioned yesterday), Redis Object Cache was/is installed and enabled. I applied the package update 3.2.0-2 today. However, it didn't update WP to 6.3. I'm still seeing the update message in WP dash: fbb0d035-c83f-4fb7-b465-6e3475ccdb35-image.png

                          Edit: I forgot to mention that these sites were still on package 3.1.2 and did not have 3.2.0-1 installed (I reverted to a backup and disabled auto-updates yesterday). Perhaps that's why it didn't update WP 6.3?

                          girishG 1 Reply Last reply
                          0
                          • humptydumptyH humptydumpty

                            In short, package 3.2.0-2 has no breaking issues but requires manual enabling of Redis and manual updating of WP 6.3. See below for details.


                            Enabling Redis Manually

                            On the W3TC sites, the update installed Redis Object Cache and disabled W3TC's object cache with a message (Object Cache is disabled via filter.). However, Redis wasn't enabled in Redis Object Cache by default, I had to manually do that to get it going.

                            d464a4b1-aa25-4b78-bf84-ce37ea5cee91-image.png

                            85b811c8-3d9e-4d19-822c-7ef12bf7df81-image.png


                            Updating WP to 6.3 Manually

                            I have a staging site (non-W3TC, but is using that problematic theme I mentioned yesterday), Redis Object Cache was/is installed and enabled. I applied the package update 3.2.0-2 today. However, it didn't update WP to 6.3. I'm still seeing the update message in WP dash: fbb0d035-c83f-4fb7-b465-6e3475ccdb35-image.png

                            Edit: I forgot to mention that these sites were still on package 3.1.2 and did not have 3.2.0-1 installed (I reverted to a backup and disabled auto-updates yesterday). Perhaps that's why it didn't update WP 6.3?

                            girishG Offline
                            girishG Offline
                            girish
                            Staff
                            wrote on last edited by girish
                            #15

                            @humptydumpty said in 3.2.0 Update not showing up:

                            manual updating of WP 6.3

                            Note that with developer edition package, this is/was always the case. You have to update WP yourself from within the app.

                            1 Reply Last reply
                            1
                            • humptydumptyH Offline
                              humptydumptyH Offline
                              humptydumpty
                              wrote on last edited by humptydumpty
                              #16

                              On an unrelated note, there's an option in WP dash > Updates to have it auto-install new releases. I noticed some of my sites have that enabled and some don't. It's not a problem, but I mention it because maybe that should be disabled/hidden somehow since this should be handled by the packaging updates.

                              image.png

                              Edit: just noticed your latest reply, so I guess WP was auto-updating most of my sites and I thought the packaging was doing that.

                              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