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. Error in apps accessing NFS volume after upgrade to v9.1.6

Error in apps accessing NFS volume after upgrade to v9.1.6

Scheduled Pinned Locked Moved Solved Support
nfsnetwork
33 Posts 2 Posters 135 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.
  • S Stirchley.coop

    Hi here are the results:

    root@v2202403157799261297:~# uname -r
    5.15.0-176-generic
    

    I only tried installing nfs-kernel-server as it was suggested as a fix for NFS not working, so I might just uninstall it if it doesn't affect anything.

    I will try updating now. Thanks for your help!

    jamesJ Offline
    jamesJ Offline
    james
    Staff
    wrote last edited by james
    #6

    Hello @stirchley.coop

    @Stirchley.coop said:

    I only tried installing nfs-kernel-server as it was suggested as a fix for NFS not working, so I might just uninstall it if it doesn't affect anything.

    As a rule of thumb for Cloudron.
    Cloudron should work out of the box without any issues.
    Any suggested fix with installing apt packages should be considered to cause more harm than solve anything.
    I would advise to always open a topic in our forum first before trying anything on your own.


    For the port 995 already in use issue.

    Could it be that by installation of some apt package, some recommended other apt packages got installed which is now using port 995?

    Can you check the following command:

    netstat -tulpen | grep -i 995
    

    And also:

    lsof -i :995
    

    Please share the output of these commands.

    1 Reply Last reply
    0
    • S Stirchley.coop

      Is there a way to downgrade to 9.1.6? I can't see an option to do this from the UI

      jamesJ Offline
      jamesJ Offline
      james
      Staff
      wrote last edited by
      #7

      Hello @stirchley.coop

      @Stirchley.coop said:

      Is there a way to downgrade to 9.1.6? I can't see an option to do this from the UI

      No. Downgrading Cloudron is not an option.

      1 Reply Last reply
      0
      • S Offline
        S Offline
        Stirchley.coop
        wrote last edited by
        #8

        Hi James.
        Output:

        root@v2202403157799261297:~# netstat -tulpen | grep -i 995
        Command 'netstat' not found, but can be installed with:
        apt install net-tools
        root@v2202403157799261297:~# lsof -i :995
        root@v2202403157799261297:~#
        

        Should I apt install net-tools?

        1 Reply Last reply
        1
        • jamesJ Offline
          jamesJ Offline
          james
          Staff
          wrote last edited by
          #9

          Hello @stirchley.coop
          Yes you can install net-tools.

          1 Reply Last reply
          0
          • S Offline
            S Offline
            Stirchley.coop
            wrote last edited by
            #10

            Ok after installing I get this:

            root@v2202403157799261297:~# netstat -tulpen | grep -i 995
            root@v2202403157799261297:~# lsof -i :995
            root@v2202403157799261297:~#
            
            1 Reply Last reply
            0
            • S Offline
              S Offline
              Stirchley.coop
              wrote last edited by
              #11

              I'm thinking I uninstall Cloudron from the server and reinstall version 9.1.5 with yesterday's backup

              jamesJ 1 Reply Last reply
              1
              • jamesJ Offline
                jamesJ Offline
                james
                Staff
                wrote last edited by
                #12

                Hello @stirchley.coop
                Can you please share the output of the command:

                docker ps -a
                

                and

                docker network list
                
                1 Reply Last reply
                0
                • S Offline
                  S Offline
                  Stirchley.coop
                  wrote last edited by Stirchley.coop
                  #13

                  @james

                  root@v2202403157799261297:~# docker ps -a
                  CONTAINER ID   IMAGE                                      COMMAND                CREATED          STATUS    PORTS     NAMES
                  f472efd072b2   registry.docker.com/cloudron/mail:3.18.2   "/app/code/start.sh"   17 minutes ago   Created             mail
                  root@v2202403157799261297:~# docker network list
                  NETWORK ID     NAME       DRIVER    SCOPE
                  cbe520222cfe   bridge     bridge    local
                  e28b8f24a89c   cloudron   bridge    local
                  f8d98b330cd7   host       host      local
                  d58248fbb326   none       null      local
                  root@v2202403157799261297:~#
                  
                  1 Reply Last reply
                  0
                  • S Stirchley.coop

                    I'm thinking I uninstall Cloudron from the server and reinstall version 9.1.5 with yesterday's backup

                    jamesJ Offline
                    jamesJ Offline
                    james
                    Staff
                    wrote last edited by
                    #14

                    Hello @stirchley.coop

                    @Stirchley.coop said:

                    I'm thinking I uninstall Cloudron from the server and reinstall version 9.1.5 with yesterday's backup

                    This would be the easy / safe route.
                    I think we can figure out this issue together and fix your server without restoring from a backup.
                    But the decision is up to you.


                    This output:

                    root@v2202403157799261297:~# docker ps -a
                    CONTAINER ID   IMAGE                                      COMMAND                CREATED          STATUS    PORTS     NAMES
                    f472efd072b2   registry.docker.com/cloudron/mail:3.18.2   "/app/code/start.sh"   17 minutes ago   Created             mail
                    

                    is very suspicious.
                    No other docker container running from cloudron except this one.

                    Can you try to restart the box.service with:

                    systemcrtl restart box.service
                    

                    Then you can also observe the box.log with:

                    tail -f /home/yellowtent/platformdata/logs/box.log
                    

                    To see all log messages from Cloudron.

                    1 Reply Last reply
                    0
                    • S Offline
                      S Offline
                      Stirchley.coop
                      wrote last edited by james
                      #15

                      @james a lot of network errors so far:

                      root@v2202403157799261297:~# systemcrtl restart box.service
                      Command 'systemcrtl' not found, did you mean:
                        command 'systemctl' from deb systemd (249.11-0ubuntu3.20)
                        command 'systemctl' from deb systemctl (1.4.4181-1.1)
                      Try: apt install <deb name>
                      root@v2202403157799261297:~# systemctl restart box.service
                      root@v2202403157799261297:~# tail -f /home/yellowtent/platformdata/logs/box.log
                      2026-04-24T17:54:34.309Z docker: deleteContainer: deleting turn
                      2026-04-24T17:54:34.310Z services: startTurn: starting turn container
                      2026-04-24T17:54:34.310Z shell: services: /bin/bash -c docker run --restart=unless-stopped -d --name=turn                 --hostname turn                 --net host                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=turn                 -m 268435456                 --memory-swap -1                 -e CLOUDRON_TURN_SECRET=-REDACTED- -e CLOUDRON_REALM=my.stirchley.coop                 -e CLOUDRON_VERBOSE_LOGS=                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/turn:1.8.2@sha256:9f3609969a5757837505c584c98246a3035a84a273b9be491665ac026423fd5f
                      2026-04-24T17:54:34.526Z services: startMysql: stopping and deleting previous mysql container
                      2026-04-24T17:54:34.526Z docker: stopContainer: stopping container mysql
                      2026-04-24T17:54:34.529Z docker: deleteContainer: deleting mysql
                      2026-04-24T17:54:34.530Z services: startMysql: starting mysql container
                      2026-04-24T17:54:34.530Z shell: services: /bin/bash -c docker run --restart=unless-stopped -d --name=mysql                 --hostname mysql                 --net cloudron                 --net-alias mysql                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=mysql                 --ip xxx                 -e CLOUDRON_MYSQL_TOKEN=xxx                 -e CLOUDRON_MYSQL_ROOT_HOST=xxx                 -e CLOUDRON_MYSQL_ROOT_PASSWORD=xxx -v /home/yellowtent/platformdata/mysql:/var/lib/mysql                 --label isCloudronManaged=true                 --cap-add SYS_NICE                 --read-only -v /tmp -v /run registry.docker.com/cloudron/mysql:3.5.3@sha256:615057dbfeb5d979ab17c3e4cef240f11ae63b95feadbaf95a30e730472980aa
                      2026-04-24T17:54:34.909Z services: Waiting for mysql
                      2026-04-24T17:54:34.914Z services: Attempt 1 failed. Will retry: Network error waiting for mysql: connect ECONNREFUSED 172.18.30.1:3000
                      2026-04-24T17:54:50.061Z services: startPostgresql: stopping and deleting previous postgresql container
                      2026-04-24T17:54:50.061Z docker: stopContainer: stopping container postgresql
                      2026-04-24T17:54:50.063Z docker: deleteContainer: deleting postgresql
                      2026-04-24T17:54:50.063Z services: startPostgresql: starting postgresql container
                      2026-04-24T17:54:50.063Z shell: services: /bin/bash -c docker run --restart=unless-stopped -d --name=postgresql                 --hostname postgresql                 --net cloudron                 --net-alias postgresql                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=postgresql                 --ip 172.18.30.2                 --shm-size=128M                 -e CLOUDRON_POSTGRESQL_ROOT_PASSWORD=xxx                 -e CLOUDRON_POSTGRESQL_TOKEN=xxx                 -v /home/yellowtent/platformdata/postgresql:/var/lib/postgresql                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/postgresql:6.3.1@sha256:95a2e1e298fb88740c6d1d200657dcce993346ba500870e8e885a1aee519dc20
                      2026-04-24T17:54:50.455Z services: Waiting for postgresql
                      2026-04-24T17:54:50.458Z services: Attempt 1 failed. Will retry: Network error waiting for postgresql: connect ECONNREFUSED 172.18.30.2:3000
                      2026-04-24T17:55:05.613Z services: startMongodb: stopping and deleting previous mongodb container
                      2026-04-24T17:55:05.613Z docker: stopContainer: stopping container mongodb
                      2026-04-24T17:55:05.615Z docker: deleteContainer: deleting mongodb
                      2026-04-24T17:55:05.616Z shell: services: grep -q avx /proc/cpuinfo
                      2026-04-24T17:55:05.619Z services: startMongodb: starting mongodb container
                      2026-04-24T17:55:05.619Z shell: services: /bin/bash -c docker run --restart=unless-stopped -d --name=mongodb                 --hostname mongodb                 --net cloudron                 --net-alias mongodb                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=mongodb                 --ip 172.18.30.3                 -e CLOUDRON_MONGODB_ROOT_PASSWORD=xxx                 -e CLOUDRON_MONGODB_TOKEN=xxx                 -v /home/yellowtent/platformdata/mongodb:/var/lib/mongodb                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/mongodb:6.3.0@sha256:8757111970a99fb9a9880f02a2a77fe9cb7368745fcff555bf528471ecb50ec3
                      2026-04-24T17:55:05.995Z services: Waiting for mongodb
                      2026-04-24T17:55:05.998Z services: Attempt 1 failed. Will retry: Network error waiting for mongodb: connect ECONNREFUSED 172.18.30.3:3000
                      2026-04-24T17:55:21.502Z services: Attempt 2 failed. Will retry: Error waiting for mongodb. Status code: 200 message: Not ready yet: uptime=3
                      2026-04-24T17:55:36.979Z services: startRedis: stopping and deleting previous redis container redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d
                      2026-04-24T17:55:36.979Z docker: stopContainer: stopping container redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d
                      2026-04-24T17:55:36.981Z docker: deleteContainer: deleting redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d
                      2026-04-24T17:55:36.982Z services: startRedis: starting redis container redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d
                      2026-04-24T17:55:36.988Z shell: services: /bin/bash -c docker create --restart=unless-stopped --name=redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d                 --hostname redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d                 --label=location=data2.stirchley.coop                 --net cloudron                 --net-alias redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=redis-1502ffae-d38e-4b8a-a75d-c833b1355a4d                 -m 268435456                 --memory-swap -1                 -e CLOUDRON_REDIS_PASSWORD=xxx                 -e CLOUDRON_REDIS_TOKEN=xxx                 -v /home/yellowtent/platformdata/redis/1502ffae-d38e-4b8a-a75d-c833b1355a4d:/var/lib/redis                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/redis:3.8.0@sha256:54a12252edbc326fd4d10e8c00836cc68776f3463f22366279f7cd8d4dafd20f
                      2026-04-24T17:55:37.211Z services: startRedis: stopping and deleting previous redis container redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73
                      2026-04-24T17:55:37.211Z docker: stopContainer: stopping container redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73
                      2026-04-24T17:55:37.213Z docker: deleteContainer: deleting redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73
                      2026-04-24T17:55:37.213Z services: startRedis: starting redis container redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73
                      2026-04-24T17:55:37.217Z shell: services: /bin/bash -c docker run -d --restart=unless-stopped --name=redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73                 --hostname redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73                 --label=location=docs2.stirchley.coop                 --net cloudron                 --net-alias redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73                 --log-driver syslog                 --log-opt syslog-address=unix:///home/yellowtent/platformdata/logs/syslog.sock                 --log-opt syslog-format=rfc5424                 --log-opt tag=redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73                 -m 268435456                 --memory-swap -1                 -e CLOUDRON_REDIS_PASSWORD=                 -e CLOUDRON_REDIS_TOKEN=xxx                 -v /home/yellowtent/platformdata/redis/1aa55af7-48e4-4f6f-816f-46185ef4cf73:/var/lib/redis                 --label isCloudronManaged=true                 --read-only -v /tmp -v /run registry.docker.com/cloudron/redis:3.8.0@sha256:54a12252edbc326fd4d10e8c00836cc68776f3463f22366279f7cd8d4dafd20f
                      2026-04-24T17:55:37.465Z services: Waiting for redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73
                      2026-04-24T17:55:37.468Z services: Attempt 1 failed. Will retry: Network error waiting for redis-1aa55af7-48e4-4f6f-816f-46185ef4cf73: connect ECONNREFUSED 172.18.0.2:3000
                      
                      
                      1 Reply Last reply
                      0
                      • jamesJ Offline
                        jamesJ Offline
                        james
                        Staff
                        wrote last edited by james
                        #16

                        Apologies, I did a typo.

                        systemctl restart box.service
                        

                        But I see you fixed the typo.

                        1 Reply Last reply
                        0
                        • S Offline
                          S Offline
                          Stirchley.coop
                          wrote last edited by
                          #17

                          That's fine I spotted and corrected it

                          1 Reply Last reply
                          0
                          • jamesJ Offline
                            jamesJ Offline
                            james
                            Staff
                            wrote last edited by
                            #18

                            The log looks correct so far.
                            It is recreating the containers due to the update and this can take some time.
                            Can you observe this for maybe 5 minutes and report back?

                            1 Reply Last reply
                            0
                            • S Offline
                              S Offline
                              Stirchley.coop
                              wrote last edited by
                              #19

                              Sure will do

                              1 Reply Last reply
                              1
                              • S Offline
                                S Offline
                                Stirchley.coop
                                wrote last edited by
                                #20

                                It seems to have settled into this state:

                                2026-04-24T18:01:40.032Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:01:50.030Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:02:00.043Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:02:10.027Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:02:20.032Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:02:30.028Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:02:40.034Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:02:50.028Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:03:00.040Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:03:10.027Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:03:20.029Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:03:30.027Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:03:40.030Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:03:50.031Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:04:00.037Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:04:10.029Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:04:20.035Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:04:30.029Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                2026-04-24T18:04:40.037Z apphealthmonitor: app health: 8 running / 5 stopped / 5 unresponsive
                                

                                There are 5 apps in Error state with the same mount error above. I assume they correspond to the 5 unresponsive apps in the logs. There are also 5 other stopped apps

                                1 Reply Last reply
                                1
                                • jamesJ Offline
                                  jamesJ Offline
                                  james
                                  Staff
                                  wrote last edited by james
                                  #21

                                  Hello @stirchley.coop
                                  Can you check in your Cloudron dashboard under Volumes?
                                  If the volume has a red dot, please press the ... button to the right side and then press Remount.
                                  When the remount works signalled by a green dot, you can go to your apps that are unresponsive into the Repair section and press Retry task.
                                  This should repair the unresponsive apps back into a working state.

                                  1 Reply Last reply
                                  0
                                  • S Offline
                                    S Offline
                                    Stirchley.coop
                                    wrote last edited by
                                    #22

                                    The volume has always had a green dot:

                                    6f87b999-d1f4-4329-813e-3a25c51b5741-image.jpeg

                                    Retry task has sorted it thank you (for one app anyway) - it still showed the mount error in the logs, but it carried on past the error this time and the app has started successfully

                                    1 Reply Last reply
                                    1
                                    • jamesJ Offline
                                      jamesJ Offline
                                      james
                                      Staff
                                      wrote last edited by
                                      #23

                                      Hello @stirchley.coop
                                      That is good to hear but also a little odd.
                                      Just make sure that the app is in a functional state and does indeed have its data due to the still printed mount error.

                                      1 Reply Last reply
                                      0
                                      • S Offline
                                        S Offline
                                        Stirchley.coop
                                        wrote last edited by
                                        #24

                                        @james that app is now up and seems to be functioning correctly, all the data is there. Waiting for the rest to start up

                                        1 Reply Last reply
                                        1
                                        • S Offline
                                          S Offline
                                          Stirchley.coop
                                          wrote last edited by Stirchley.coop
                                          #25

                                          @james the other apps seem to be stuck in an error state:

                                          Apr 24 19:17:05 taskworker: Starting task 14154. Logs are at /home/yellowtent/platformdata/logs/74f9b0b7-8fb9-4805-9057-5d3bcf33d36b/apptask.log
                                          Apr 24 19:17:05 taskworker: Running task of type app
                                          Apr 24 19:17:05 apptask: run: startTask installationState: pending_configure runState: running
                                          Apr 24 19:17:05 tasks: updating task 14154 with: {"percent":10,"message":"Deleting old containers"}
                                          Apr 24 19:17:05 shell: reverseproxy: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/restartservice.sh nginx
                                          Apr 24 19:17:05 apptask: deleteContainer: deleting app containers (app, scheduler)
                                          Apr 24 19:17:05 shell: apptask: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/configurelogrotate.sh remove 74f9b0b7-8fb9-4805-9057-5d3bcf33d36b
                                          Apr 24 19:17:05 tasks: updating task 14154 with: {"percent":20,"message":"Downloading icon"}
                                          Apr 24 19:17:05 apptask: downloadIcon: Downloading icon of org.wordpress.cloudronapp@3.16.3
                                          Apr 24 19:17:06 tasks: updating task 14154 with: {"percent":40,"message":"Downloading image"}
                                          Apr 24 19:17:06 shell: df: df -B1 --output=source,fstype,size,used,avail,pcent,target /var/lib/docker
                                          Apr 24 19:17:06 docker: downloadImage: cloudron/org.wordpress.cloudronapp:202603120114210000
                                          Apr 24 19:17:06 tasks: updating task 14154 with: {"percent":50,"message":"Ensuring app data directory"}
                                          Apr 24 19:17:06 tasks: updating task 14154 with: {"percent":55,"message":"Setting up addons"}
                                          Apr 24 19:17:06 services: Setting up mysql
                                          Apr 24 19:17:06 services: setupAddons: Setting up ["mysql","localstorage","sendmail","oidc","scheduler"]
                                          Apr 24 19:17:06 services: setupAddons: setting up addon mysql with options {}
                                          Apr 24 19:17:06 services: Setting mysql addon config to [{"name":"CLOUDRON_MYSQL_USERNAME","value":"xxx"},{"name":"CLOUDRON_MYSQL_PASSWORD","value":"xxx"},{"name":"CLOUDRON_MYSQL_HOST","value":"mysql"},{"name":"CLOUDRON_MYSQL_PORT","value":"3306"},{"name":"CLOUDRON_MYSQL_URL","value":"xxx"},{"name":"CLOUDRON_MYSQL_DATABASE","value":"xxx"}]
                                          Apr 24 19:17:06 services: setupAddons: setting up addon localstorage with options {"ftp":{"uid":33,"uname":"www-data"}}
                                          Apr 24 19:17:06 services: setupLocalStorage
                                          Apr 24 19:17:06 shell: services: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/setupvolume.sh /mnt/volumes/00fd99454f384c91a83326ad3097bb1e/www
                                          Apr 24 19:17:06 services: setupAddons: setting up addon sendmail with options {"optional":true,"supportsDisplayName":true}
                                          Apr 24 19:17:06 services: Setting sendmail addon config to [{"name":"CLOUDRON_MAIL_SMTP_SERVER","value":"mail"},{"name":"CLOUDRON_MAIL_SMTP_PORT","value":"2525"},{"name":"CLOUDRON_MAIL_SMTPS_PORT","value":"2465"},{"name":"CLOUDRON_MAIL_STARTTLS_PORT","value":"2587"},{"name":"CLOUDRON_MAIL_SMTP_USERNAME","value":"xxx"},{"name":"CLOUDRON_MAIL_SMTP_PASSWORD","value":"xxx"},{"name":"CLOUDRON_MAIL_FROM","value":"xxx"},{"name":"CLOUDRON_MAIL_DOMAIN","value":"stirchley.coop"},{"name":"CLOUDRON_MAIL_FROM_DISPLAY_NAME","value":""}]
                                          Apr 24 19:17:06 services: Setting up SendMail
                                          Apr 24 19:17:06 services: setupAddons: setting up addon oidc with options {"loginRedirectUri":"/wp-admin/admin-ajax.php?action=openid-connect-authorize"}
                                          Apr 24 19:17:06 services: Setting up OIDC
                                          Apr 24 19:17:06 services: setupAddons: setting up addon scheduler with options {"wpcron":{"schedule":"*/5 * * * *","command":"/app/pkg/cron.sh"}}
                                          Apr 24 19:17:06 tasks: updating task 14154 with: {"percent":60,"message":"Creating container"}
                                          Apr 24 19:17:06 apptask: createContainer: creating container
                                          Apr 24 19:17:06 shell: mounts: mountpoint -q -- /mnt/volumes/00fd99454f384c91a83326ad3097bb1e
                                          Apr 24 19:17:06 shell: apptask: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/configurelogrotate.sh add 74f9b0b7-8fb9-4805-9057-5d3bcf33d36b /tmp/74f9b0b7-8fb9-4805-9057-5d3bcf33d36b.logrotate
                                          Apr 24 19:17:06 apptask: startApp: starting container
                                          Apr 24 19:17:06 tasks: updating task 14154 with: {"percent":90,"message":"Configuring reverse proxy"}
                                          Apr 24 19:17:06 shell: openssl: openssl x509 -noout -subject -issuer
                                          Apr 24 19:17:06 reverseproxy: providerMatches: subject=CN = *.stirchley.coop domain=*.stirchley.coop issuer=C = US, O = Let's Encrypt, CN = E7 wildcard=true/true prod=true/true issuerMismatch=false wildcardMismatch=false match=true
                                          Apr 24 19:17:06 shell: openssl: openssl x509 -startdate -enddate -subject -noout
                                          Apr 24 19:17:06 openssl: expiryDate: subject=CN = *.stirchley.coop notBefore=Apr  5 18:12:13 2026 GMT notAfter=Jul  4 18:12:12 2026 GMT daysLeft=70.9965897337963
                                          Apr 24 19:17:06 reverseproxy: ensureCertificate: www.stirchley.coop acme cert exists and is up to date
                                          Apr 24 19:17:06 reverseproxy: needsRenewal: false. ARI {"start":"Wed, 03 Jun 2026 20:56:17 GMT","end":"Fri, 05 Jun 2026 16:07:06 GMT","rt":"Thu, 04 Jun 2026 03:54:39 GMT","valid":"Fri, 24 Apr 2026 22:54:51 GMT","url":"https://acme-v02.api.letsencrypt.org/acme/renewal-info","ts":"Fri, 24 Apr 2026 17:57:02 GMT"}
                                          Apr 24 19:17:06 shell: openssl: openssl x509 -noout -subject -issuer
                                          Apr 24 19:17:06 reverseproxy: getRenewalInfo: stirchley.coop refreshing
                                          Apr 24 19:17:06 reverseproxy: providerMatches: subject=CN = stirchley.coop domain=stirchley.coop issuer=C = US, O = Let's Encrypt, CN = E7 wildcard=false/true prod=true/true issuerMismatch=false wildcardMismatch=false match=true
                                          Apr 24 19:17:06 shell: openssl: openssl x509 -noout -text
                                          Apr 24 19:17:06 shell: openssl: openssl x509 -noout -serial
                                          Apr 24 19:17:06 ==> Changing permissions
                                          Apr 24 19:17:07 reverseproxy: getRenewalInfo: stirchley.coop updated: {"start":"Wed, 27 May 2026 20:56:10 GMT","end":"Fri, 29 May 2026 16:06:59 GMT","rt":"Fri, 29 May 2026 01:30:42 GMT","valid":"Fri, 24 Apr 2026 23:46:26 GMT","url":"https://acme-v02.api.letsencrypt.org/acme/renewal-info","ts":"Fri, 24 Apr 2026 18:17:06 GMT"}
                                          Apr 24 19:17:07 shell: openssl: openssl x509 -startdate -enddate -subject -noout
                                          Apr 24 19:17:07 openssl: expiryDate: subject=CN = stirchley.coop notBefore=Mar 29 18:12:06 2026 GMT notAfter=Jun 27 18:12:05 2026 GMT daysLeft=63.99650290509259
                                          Apr 24 19:17:07 reverseproxy: ensureCertificate: stirchley.coop acme cert exists and is up to date
                                          Apr 24 19:17:07 reverseproxy: needsRenewal: false. ARI {"start":"Wed, 27 May 2026 20:56:10 GMT","end":"Fri, 29 May 2026 16:06:59 GMT","rt":"Fri, 29 May 2026 01:30:42 GMT","valid":"Fri, 24 Apr 2026 23:46:26 GMT","url":"https://acme-v02.api.letsencrypt.org/acme/renewal-info","ts":"Fri, 24 Apr 2026 18:17:06 GMT"}
                                          Apr 24 19:17:07 reverseproxy: writeAppLocationNginxConfig: writing config for "www.stirchley.coop" to /home/yellowtent/platformdata/nginx/applications/74f9b0b7-8fb9-4805-9057-5d3bcf33d36b/www.stirchley.coop.conf with options {"sourceDir":"/home/yellowtent/box","vhost":"www.stirchley.coop","hasIPv6":true,"ip":"172.18.16.234","port":80,"endpoint":"app","redirectTo":null,"certFilePath":"/home/yellowtent/platformdata/nginx/cert/_.stirchley.coop.cert","keyFilePath":"/home/yellowtent/platformdata/nginx/cert/_.stirchley.coop.key","robotsTxtQuoted":null,"cspQuoted":null,"hideHeaders":[],"proxyAuth":{"id":"74f9b0b7-8fb9-4805-9057-5d3bcf33d36b","location":"/"},"upstreamUri":"","hstsPreload":false}
                                          Apr 24 19:17:07 reverseproxy: writeAppLocationNginxConfig: writing config for "stirchley.coop" to /home/yellowtent/platformdata/nginx/applications/74f9b0b7-8fb9-4805-9057-5d3bcf33d36b/stirchley.coop.conf with options {"sourceDir":"/home/yellowtent/box","vhost":"stirchley.coop","hasIPv6":true,"ip":null,"port":null,"endpoint":"redirect","redirectTo":"www.stirchley.coop","certFilePath":"/home/yellowtent/platformdata/nginx/cert/stirchley.coop.cert","keyFilePath":"/home/yellowtent/platformdata/nginx/cert/stirchley.coop.key","robotsTxtQuoted":null,"cspQuoted":null,"hideHeaders":[],"proxyAuth":{"enabled":false,"id":"74f9b0b7-8fb9-4805-9057-5d3bcf33d36b","location":"/"},"upstreamUri":"","hstsPreload":false}
                                          Apr 24 19:17:07 shell: reverseproxy: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/restartservice.sh nginx
                                          Apr 24 19:17:07 tasks: updating task 14154 with: {"percent":100,"message":"Done"}
                                          Apr 24 19:17:07 tasks: setCompleted - 14154: {"result":null,"error":null,"percent":100}
                                          Apr 24 19:17:07 tasks: updating task 14154 with: {"completed":true,"result":null,"error":null,"percent":100}
                                          Apr 24 19:17:07 taskworker: Task took 1.755 seconds
                                          Apr 24 19:17:07 Exiting with code 0
                                          Apr 24 19:17:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:17:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:17:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:17:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:17:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:17:50 BoxError: Storage volume "NetCup RS voln639290a1" is not active. Could not determine mount failure reason. 
                                          Apr 24 19:17:50 }
                                          Apr 24 19:17:50 }
                                          Apr 24 19:18:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:18:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:18:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:18:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:18:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:18:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:19:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:19:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:19:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:19:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:19:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:19:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:20:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:20:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:20:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:20:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:20:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:20:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:21:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:21:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:21:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:21:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:21:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:21:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:22:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:22:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:22:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:22:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:22:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:22:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:23:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:23:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:23:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:23:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:23:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:23:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:24:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:24:10 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:24:20 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:24:30 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:24:40 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:24:50 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          Apr 24 19:25:00 => Healthcheck error: Error: connect ECONNREFUSED 172.18.16.234:80
                                          
                                          jamesJ 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