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. Loomio
  3. some first findings

some first findings

Scheduled Pinned Locked Moved Solved Loomio
16 Posts 5 Posters 2.0k Views 5 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.
    • luckowL Offline
      luckowL Offline
      luckow
      translator
      wrote on last edited by
      #1

      Adding a group does not work. It seems that something works (like reserving the namespace), but there is an "infinite loop" in the "Add Group" dialog.

      Here is some initial information from the logs (but it looks like possible other issues).:

      Mar 17 18:40:20 2023/03/17 17:40:20 [error] 28#28: *596 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.example.org"
      
      Mar 17 18:43:25 I, [2023-03-17T17:43:25.290160 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
      

      Pronouns: he/him | Primary language: German

      1 Reply Last reply
      3
      • nebulonN nebulon marked this topic as a question on
      • girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #2

        @vladimir-d can you please take a look at this?

        1 Reply Last reply
        1
        • vladimir.dV Offline
          vladimir.dV Offline
          vladimir.d
          wrote on last edited by
          #3

          @luckow I've installed the Loomio app from the app store using the default domains: loomio.mydomain.com and channels.loomio.mydomain.com. Everything went smoothly, I haven't got any errors on user signing up or creating new groups.
          Could you explain steps to reproduce it? Does it happen for you at the user sign-up? What did you try to specify as the group name?
          Could you also check if /app/data/storage folder belongs to cloudron user?
          Does the app restart resolve the issue?

          IMAP related notice is related to an incomplete IMAP configuration, which will be removed from the app in the future version for a while IMAP pooling is being refactored.

          jdaviescoatesJ 1 Reply Last reply
          0
          • vladimir.dV vladimir.d

            @luckow I've installed the Loomio app from the app store using the default domains: loomio.mydomain.com and channels.loomio.mydomain.com. Everything went smoothly, I haven't got any errors on user signing up or creating new groups.
            Could you explain steps to reproduce it? Does it happen for you at the user sign-up? What did you try to specify as the group name?
            Could you also check if /app/data/storage folder belongs to cloudron user?
            Does the app restart resolve the issue?

            IMAP related notice is related to an incomplete IMAP configuration, which will be removed from the app in the future version for a while IMAP pooling is being refactored.

            jdaviescoatesJ Offline
            jdaviescoatesJ Offline
            jdaviescoates
            wrote on last edited by jdaviescoates
            #4

            @vladimir-d said in some first findings:

            @luckow I've installed the Loomio app from the app store using the default domains: loomio.mydomain.com and channels.loomio.mydomain.com. Everything went smoothly, I haven't got any errors on user signing up or creating new groups.

            I just did the same and got the same errors as @luckow

            When I tried to create the first group, it also failed, i.e. I hit the Start Group button and it did something, but then I was just back where I was as is nothing happened:

            612b06e5-d04c-409e-a05a-6d30e4a830dc-image.png

            Hitting the button a second time seemingly worked:

            cec21b77-a4d3-4b61-aff0-8502905a712e-image.png

            But it is still regularly generating those errors every 10-30 seconds or so:

            Mar 20 12:53:10 2023/03/20 12:53:10 [error] 23#23: *366 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
            Mar 20 12:53:10 2023/03/20 12:53:10 [warn] 23#23: *366 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
            Mar 20 12:53:10 [20/Mar/2023:12:53:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.004 0.004
            Mar 20 12:53:12 I, [2023-03-20T12:53:12.385731 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
            Mar 20 12:53:20 [20/Mar/2023:12:53:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
            Mar 20 12:53:30 [20/Mar/2023:12:53:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
            Mar 20 12:53:40 [20/Mar/2023:12:53:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.004
            Mar 20 12:53:50 2023/03/20 12:53:50 [error] 23#23: *375 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
            Mar 20 12:53:50 2023/03/20 12:53:50 [warn] 23#23: *375 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
            Mar 20 12:53:50 [20/Mar/2023:12:53:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.048, 0.108 0.154
            Mar 20 12:54:00 [20/Mar/2023:12:54:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.036 0.039
            Mar 20 12:54:06 13:M 20 Mar 2023 12:54:06.059 * 10 changes in 300 seconds. Saving...
            Mar 20 12:54:06 13:M 20 Mar 2023 12:54:06.059 * Background saving started by pid 32
            Mar 20 12:54:06 32:C 20 Mar 2023 12:54:06.077 * DB saved on disk
            Mar 20 12:54:06 32:C 20 Mar 2023 12:54:06.078 * RDB: 0 MB of memory used by copy-on-write
            Mar 20 12:54:06 13:M 20 Mar 2023 12:54:06.159 * Background saving terminated with success
            Mar 20 12:54:10 [20/Mar/2023:12:54:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.052 0.053
            Mar 20 12:54:12 I, [2023-03-20T12:54:12.381389 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
            Mar 20 12:54:20 [20/Mar/2023:12:54:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.004
            Mar 20 12:54:30 2023/03/20 12:54:30 [error] 23#23: *384 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
            Mar 20 12:54:30 2023/03/20 12:54:30 [warn] 23#23: *384 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
            Mar 20 12:54:30 [20/Mar/2023:12:54:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.004 0.007
            Mar 20 12:54:40 [20/Mar/2023:12:54:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.001
            Mar 20 12:54:50 [20/Mar/2023:12:54:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.003
            Mar 20 12:55:00 [20/Mar/2023:12:55:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.002
            Mar 20 12:55:10 2023/03/20 12:55:10 [error] 23#23: *393 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
            Mar 20 12:55:10 2023/03/20 12:55:10 [warn] 23#23: *393 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
            Mar 20 12:55:10 [20/Mar/2023:12:55:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.012 0.008
            Mar 20 12:55:12 I, [2023-03-20T12:55:12.435068 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
            Mar 20 12:55:20 [20/Mar/2023:12:55:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.148 0.149
            Mar 20 12:55:30 [20/Mar/2023:12:55:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.024 0.024
            Mar 20 12:55:40 [20/Mar/2023:12:55:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.004
            Mar 20 12:55:40 2023/03/20 12:55:40 [error] 23#23: *402 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET /api/v1/boot/version?version=2.17.0&release=1678246381&now=1679316940928 HTTP/1.1", upstream: "http://[::1]:3000/api/v1/boot/version?version=2.17.0&release=1678246381&now=1679316940928", host: "loomio.uniteddiversity.coop", referrer: "https://loomio.uniteddiversity.coop/g/WPrYQ0MH"
            Mar 20 12:55:40 2023/03/20 12:55:40 [warn] 23#23: *402 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET /api/v1/boot/version?version=2.17.0&release=1678246381&now=1679316940928 HTTP/1.1", upstream: "http://[::1]:3000/api/v1/boot/version?version=2.17.0&release=1678246381&now=1679316940928", host: "loomio.uniteddiversity.coop", referrer: "https://loomio.uniteddiversity.coop/g/WPrYQ0MH"
            Mar 20 12:55:41 fatal: not a git repository (or any of the parent directories): .git
            Mar 20 12:55:41 [20/Mar/2023:12:55:41 +0000] 172.18.0.1 "GET /api/v1/boot/version?version=2.17.0&release=1678246381&now=1679316940928 HTTP/1.1" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/110.0" 200 1423 "https://loomio.uniteddiversity.coop/g/WPrYQ0MH" 0.000, 0.068 0.068
            Mar 20 12:55:50 [20/Mar/2023:12:55:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
            Mar 20 12:56:00 [20/Mar/2023:12:56:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.002
            Mar 20 12:56:10 [20/Mar/2023:12:56:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
            Mar 20 12:56:12 I, [2023-03-20T12:56:12.673183 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
            Mar 20 12:56:20 2023/03/20 12:56:20 [error] 23#23: *411 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
            Mar 20 12:56:20 2023/03/20 12:56:20 [warn] 23#23: *411 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
            
            

            I also note that instead of being able to login using Cloudron credentials I was prompted to create an account with an email address (as opposed to a username).

            I use Cloudron with Gandi & Hetzner

            jdaviescoatesJ 1 Reply Last reply
            0
            • jdaviescoatesJ jdaviescoates

              @vladimir-d said in some first findings:

              @luckow I've installed the Loomio app from the app store using the default domains: loomio.mydomain.com and channels.loomio.mydomain.com. Everything went smoothly, I haven't got any errors on user signing up or creating new groups.

              I just did the same and got the same errors as @luckow

              When I tried to create the first group, it also failed, i.e. I hit the Start Group button and it did something, but then I was just back where I was as is nothing happened:

              612b06e5-d04c-409e-a05a-6d30e4a830dc-image.png

              Hitting the button a second time seemingly worked:

              cec21b77-a4d3-4b61-aff0-8502905a712e-image.png

              But it is still regularly generating those errors every 10-30 seconds or so:

              Mar 20 12:53:10 2023/03/20 12:53:10 [error] 23#23: *366 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 12:53:10 2023/03/20 12:53:10 [warn] 23#23: *366 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 12:53:10 [20/Mar/2023:12:53:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.004 0.004
              Mar 20 12:53:12 I, [2023-03-20T12:53:12.385731 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
              Mar 20 12:53:20 [20/Mar/2023:12:53:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
              Mar 20 12:53:30 [20/Mar/2023:12:53:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
              Mar 20 12:53:40 [20/Mar/2023:12:53:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.004
              Mar 20 12:53:50 2023/03/20 12:53:50 [error] 23#23: *375 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 12:53:50 2023/03/20 12:53:50 [warn] 23#23: *375 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 12:53:50 [20/Mar/2023:12:53:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.048, 0.108 0.154
              Mar 20 12:54:00 [20/Mar/2023:12:54:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.036 0.039
              Mar 20 12:54:06 13:M 20 Mar 2023 12:54:06.059 * 10 changes in 300 seconds. Saving...
              Mar 20 12:54:06 13:M 20 Mar 2023 12:54:06.059 * Background saving started by pid 32
              Mar 20 12:54:06 32:C 20 Mar 2023 12:54:06.077 * DB saved on disk
              Mar 20 12:54:06 32:C 20 Mar 2023 12:54:06.078 * RDB: 0 MB of memory used by copy-on-write
              Mar 20 12:54:06 13:M 20 Mar 2023 12:54:06.159 * Background saving terminated with success
              Mar 20 12:54:10 [20/Mar/2023:12:54:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.052 0.053
              Mar 20 12:54:12 I, [2023-03-20T12:54:12.381389 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
              Mar 20 12:54:20 [20/Mar/2023:12:54:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.004
              Mar 20 12:54:30 2023/03/20 12:54:30 [error] 23#23: *384 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 12:54:30 2023/03/20 12:54:30 [warn] 23#23: *384 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 12:54:30 [20/Mar/2023:12:54:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.004 0.007
              Mar 20 12:54:40 [20/Mar/2023:12:54:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.001
              Mar 20 12:54:50 [20/Mar/2023:12:54:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.003
              Mar 20 12:55:00 [20/Mar/2023:12:55:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.002
              Mar 20 12:55:10 2023/03/20 12:55:10 [error] 23#23: *393 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 12:55:10 2023/03/20 12:55:10 [warn] 23#23: *393 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 12:55:10 [20/Mar/2023:12:55:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.012 0.008
              Mar 20 12:55:12 I, [2023-03-20T12:55:12.435068 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
              Mar 20 12:55:20 [20/Mar/2023:12:55:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.148 0.149
              Mar 20 12:55:30 [20/Mar/2023:12:55:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.024 0.024
              Mar 20 12:55:40 [20/Mar/2023:12:55:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.004
              Mar 20 12:55:40 2023/03/20 12:55:40 [error] 23#23: *402 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET /api/v1/boot/version?version=2.17.0&release=1678246381&now=1679316940928 HTTP/1.1", upstream: "http://[::1]:3000/api/v1/boot/version?version=2.17.0&release=1678246381&now=1679316940928", host: "loomio.uniteddiversity.coop", referrer: "https://loomio.uniteddiversity.coop/g/WPrYQ0MH"
              Mar 20 12:55:40 2023/03/20 12:55:40 [warn] 23#23: *402 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET /api/v1/boot/version?version=2.17.0&release=1678246381&now=1679316940928 HTTP/1.1", upstream: "http://[::1]:3000/api/v1/boot/version?version=2.17.0&release=1678246381&now=1679316940928", host: "loomio.uniteddiversity.coop", referrer: "https://loomio.uniteddiversity.coop/g/WPrYQ0MH"
              Mar 20 12:55:41 fatal: not a git repository (or any of the parent directories): .git
              Mar 20 12:55:41 [20/Mar/2023:12:55:41 +0000] 172.18.0.1 "GET /api/v1/boot/version?version=2.17.0&release=1678246381&now=1679316940928 HTTP/1.1" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/110.0" 200 1423 "https://loomio.uniteddiversity.coop/g/WPrYQ0MH" 0.000, 0.068 0.068
              Mar 20 12:55:50 [20/Mar/2023:12:55:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
              Mar 20 12:56:00 [20/Mar/2023:12:56:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.002
              Mar 20 12:56:10 [20/Mar/2023:12:56:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
              Mar 20 12:56:12 I, [2023-03-20T12:56:12.673183 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
              Mar 20 12:56:20 2023/03/20 12:56:20 [error] 23#23: *411 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 12:56:20 2023/03/20 12:56:20 [warn] 23#23: *411 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              
              

              I also note that instead of being able to login using Cloudron credentials I was prompted to create an account with an email address (as opposed to a username).

              jdaviescoatesJ Offline
              jdaviescoatesJ Offline
              jdaviescoates
              wrote on last edited by
              #5

              @jdaviescoates said in some first findings:

              When I tried to create the first group, it also failed, i.e. I hit the Start Group button and it did something, but then I was just back where I was as is nothing happened:

              Ah, it seemingly ran out of memory, so that'd explain why it didn't work the first time:

              ec46ff30-e0c1-4fcb-8a4e-c3bb528e81f9-image.png

              To be fair, Cloudron did warn me that my server was running low of memory when I installed it but I proceeded anyway!

              But I just uninstalled and then reinstalled after stopping a couple of installed by unused Discourse forums (which are memory hogs). Didn't get the RAM warning when installed.

              Looked at the logs as soon as it said the app was running (i.e. before even clicking on the link) and those errors and warnings are already there (looks to me like they are present during the start-up process):

              Mar 20 13:23:58 ==> Starting app
              Mar 20 13:23:58 2023-03-20 13:23:58,502 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
              Mar 20 13:23:58 2023-03-20 13:23:58,502 INFO Included extra file "/etc/supervisor/conf.d/loomio-channels.conf" during parsing
              Mar 20 13:23:58 2023-03-20 13:23:58,502 INFO Included extra file "/etc/supervisor/conf.d/loomio-sidekiq.conf" during parsing
              Mar 20 13:23:58 2023-03-20 13:23:58,502 INFO Included extra file "/etc/supervisor/conf.d/loomio.conf" during parsing
              Mar 20 13:23:58 2023-03-20 13:23:58,502 INFO Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
              Mar 20 13:23:58 2023-03-20 13:23:58,506 INFO RPC interface 'supervisor' initialized
              Mar 20 13:23:58 2023-03-20 13:23:58,506 CRIT Server 'unix_http_server' running without any HTTP authentication checking
              Mar 20 13:23:58 2023-03-20 13:23:58,507 INFO supervisord started with pid 1
              Mar 20 13:23:59 2023-03-20 13:23:59,510 INFO spawned: 'loomio' with pid 18
              Mar 20 13:23:59 2023-03-20 13:23:59,513 INFO spawned: 'loomio-sidekiq' with pid 19
              Mar 20 13:23:59 2023-03-20 13:23:59,515 INFO spawned: 'loomio-channels' with pid 20
              Mar 20 13:23:59 2023-03-20 13:23:59,518 INFO spawned: 'nginx' with pid 21
              Mar 20 13:23:59
              Mar 20 13:23:59 > loomio_channel_server@0.0.1 start
              Mar 20 13:23:59 > node --harmony index.js
              Mar 20 13:23:59
              Mar 20 13:24:00 2023/03/20 13:24:00 [error] 28#28: *1 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:24:00 2023/03/20 13:24:00 [warn] 28#28: *1 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:24:00 2023/03/20 13:24:00 [error] 28#28: *1 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:24:00 2023/03/20 13:24:00 [warn] 28#28: *1 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:24:00 [20/Mar/2023:13:24:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 502 295 "-" 0.000, 0.008 0.009
              Healtheck error got response status 5022023-03-20T13:24:00.000Z [18] Puma starting in cluster mode...
              Mar 20 13:24:00 [18] * Puma version: 6.1.1 (ruby 2.7.6-p219) ("The Way Up")
              Mar 20 13:24:00 [18] * Min threads: 12
              Mar 20 13:24:00 [18] * Max threads: 12
              Mar 20 13:24:00 [18] * Environment: production
              Mar 20 13:24:00 [18] * Master PID: 18
              Mar 20 13:24:00 [18] * Workers: 10
              Mar 20 13:24:00 [18] * Restarts: (✔) hot (✖) phased
              Mar 20 13:24:00 [18] * Preloading application
              Mar 20 13:24:00 Allowed origin https://loomio.uniteddiversity.coop
              Mar 20 13:24:00 2023-03-20 13:24:00,641 INFO success: loomio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
              Mar 20 13:24:00 2023-03-20 13:24:00,641 INFO success: loomio-sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
              Mar 20 13:24:00 2023-03-20 13:24:00,641 INFO success: loomio-channels entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
              Mar 20 13:24:00 2023-03-20 13:24:00,641 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
              Mar 20 13:24:00 booting bots!
              Mar 20 13:24:01 bot redis connected
              Mar 20 13:24:01 /usr/local/lib/ruby/2.7.0/net/protocol.rb:66: warning: already initialized constant Net::ProtocRetryError
              Mar 20 13:24:01 /app/code/loomio/vendor/gems/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:68: warning: previous definition of ProtocRetryError was here
              Mar 20 13:24:01 /usr/local/lib/ruby/2.7.0/net/protocol.rb:206: warning: already initialized constant Net::BufferedIO::BUFSIZE
              Mar 20 13:24:01 /app/code/loomio/vendor/gems/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:208: warning: previous definition of BUFSIZE was here
              Mar 20 13:24:01 /usr/local/lib/ruby/2.7.0/net/protocol.rb:503: warning: already initialized constant Net::NetPrivate::Socket
              Mar 20 13:24:01 /app/code/loomio/vendor/gems/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:504: warning: previous definition of Socket was here
              Mar 20 13:24:01 /usr/local/lib/ruby/2.7.0/net/protocol.rb:66: warning: already initialized constant Net::ProtocRetryError
              Mar 20 13:24:01 /app/code/loomio/vendor/gems/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:68: warning: previous definition of ProtocRetryError was here
              Mar 20 13:24:01 /usr/local/lib/ruby/2.7.0/net/protocol.rb:206: warning: already initialized constant Net::BufferedIO::BUFSIZE
              Mar 20 13:24:01 /app/code/loomio/vendor/gems/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:208: warning: previous definition of BUFSIZE was here
              Mar 20 13:24:01 /usr/local/lib/ruby/2.7.0/net/protocol.rb:503: warning: already initialized constant Net::NetPrivate::Socket
              Mar 20 13:24:01 /app/code/loomio/vendor/gems/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:504: warning: previous definition of Socket was here
              Mar 20 13:24:01 /app/code/loomio/config/initializers/sidekiq.rb:2: warning: Sidekiq's Delayed Extensions will be removed in Sidekiq 7.0
              Mar 20 13:24:01 `Redis#exists(key)` will return an Integer by default in redis-rb 4.3. The option to explicitly disable this behaviour via `Redis.exists_returns_integer` will be removed in 5.0. You should use `exists?` instead.
              Mar 20 13:24:02 /app/code/loomio/config/initializers/sidekiq.rb:2: warning: Sidekiq's Delayed Extensions will be removed in Sidekiq 7.0
              Mar 20 13:24:02 `Redis#exists(key)` will return an Integer by default in redis-rb 4.3. The option to explicitly disable this behaviour via `Redis.exists_returns_integer` will be removed in 5.0. You should use `exists?` instead.
              Mar 20 13:24:05 [18] * Listening on http://0.0.0.0:3000
              Mar 20 13:24:05 [18] Use Ctrl-C to stop
              Mar 20 13:24:05 [18] - Worker 0 (PID: 59) booted in 0.14s, phase: 0
              Mar 20 13:24:05 [18] - Worker 1 (PID: 66) booted in 0.13s, phase: 0
              Mar 20 13:24:05 [18] - Worker 2 (PID: 77) booted in 0.12s, phase: 0
              Mar 20 13:24:05 [18] - Worker 3 (PID: 90) booted in 0.1s, phase: 0
              Mar 20 13:24:05 [18] - Worker 4 (PID: 100) booted in 0.09s, phase: 0
              Mar 20 13:24:05 [18] - Worker 5 (PID: 113) booted in 0.08s, phase: 0
              Mar 20 13:24:05 [18] - Worker 6 (PID: 129) booted in 0.06s, phase: 0
              Mar 20 13:24:05 [18] - Worker 7 (PID: 152) booted in 0.05s, phase: 0
              Mar 20 13:24:05 [18] - Worker 8 (PID: 180) booted in 0.04s, phase: 0
              Mar 20 13:24:05 [18] - Worker 9 (PID: 212) booted in 0.0s, phase: 0
              Mar 20 13:24:05 2023-03-20T13:24:05.696Z pid=19 tid=877 INFO: Booted Rails 6.1.7.2 application in production environment
              Mar 20 13:24:05 2023-03-20T13:24:05.696Z pid=19 tid=877 INFO: Running in ruby 2.7.6p219 (2022-04-12 revision c9c2245c0a) [x86_64-linux]
              Mar 20 13:24:05 2023-03-20T13:24:05.697Z pid=19 tid=877 INFO: See LICENSE and the LGPL-3.0 for licensing details.
              Mar 20 13:24:05 2023-03-20T13:24:05.697Z pid=19 tid=877 INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org
              Mar 20 13:24:05 2023-03-20T13:24:05.699Z pid=19 tid=877 WARN:
              Mar 20 13:24:05
              Mar 20 13:24:05 WARNING: Your Redis instance will evict Sidekiq data under heavy load.
              Mar 20 13:24:05 The 'noeviction' maxmemory policy is recommended (current policy: 'allkeys-lru').
              Mar 20 13:24:05 See: https://github.com/mperham/sidekiq/wiki/Using-Redis#memory
              Mar 20 13:24:05
              Mar 20 13:24:05
              Mar 20 13:24:10 2023/03/20 13:24:10 [error] 28#28: *4 no live upstreams while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://localhost/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:24:10 [20/Mar/2023:13:24:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 502 295 "-" 0.000 0.000
              Healtheck error got response status 5022023-03-20T13:24:20.000Z [20/Mar/2023:13:24:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.002
              Mar 20 13:24:30 [20/Mar/2023:13:24:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.004
              Mar 20 13:23:27 Starting supervisor
              Mar 20 13:23:27 2023-03-20 13:23:27,417 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
              Mar 20 13:23:27 2023-03-20 13:23:27,417 INFO Included extra file "/etc/supervisor/conf.d/redis-service.conf" during parsing
              Mar 20 13:23:27 2023-03-20 13:23:27,417 INFO Included extra file "/etc/supervisor/conf.d/redis.conf" during parsing
              Mar 20 13:23:27 2023-03-20 13:23:27,427 INFO RPC interface 'supervisor' initialized
              Mar 20 13:23:27 2023-03-20 13:23:27,427 CRIT Server 'inet_http_server' running without any HTTP authentication checking
              Mar 20 13:23:27 2023-03-20 13:23:27,427 INFO RPC interface 'supervisor' initialized
              Mar 20 13:23:27 2023-03-20 13:23:27,427 CRIT Server 'unix_http_server' running without any HTTP authentication checking
              Mar 20 13:23:27 2023-03-20 13:23:27,427 INFO supervisord started with pid 1
              Mar 20 13:23:28 2023-03-20 13:23:28,431 INFO spawned: 'redis' with pid 13
              Mar 20 13:23:28 2023-03-20 13:23:28,434 INFO spawned: 'redis-service' with pid 14
              Mar 20 13:23:28 13:C 20 Mar 2023 13:23:28.465 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
              Mar 20 13:23:28 13:C 20 Mar 2023 13:23:28.465 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=13, just started
              Mar 20 13:23:28 13:C 20 Mar 2023 13:23:28.465 # Configuration loaded
              Mar 20 13:23:28 13:M 20 Mar 2023 13:23:28.478 * Running mode=standalone, port=6379.
              Mar 20 13:23:28 13:M 20 Mar 2023 13:23:28.478 # Server initialized
              Mar 20 13:23:28 13:M 20 Mar 2023 13:23:28.478 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
              Mar 20 13:23:28 13:M 20 Mar 2023 13:23:28.478 * Ready to accept connections
              Mar 20 13:23:28 Redis service endpoint listening on http://:::3000
              Mar 20 13:23:29 2023-03-20 13:23:29,865 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
              Mar 20 13:23:29 2023-03-20 13:23:29,865 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
              Mar 20 13:23:42 [GET] /healthcheck
              Mar 20 13:24:40 2023/03/20 13:24:40 [error] 28#28: *9 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:24:40 2023/03/20 13:24:40 [warn] 28#28: *9 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:24:40 [20/Mar/2023:13:24:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.004 0.004
              Mar 20 13:24:50 [20/Mar/2023:13:24:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.008 0.007
              Mar 20 13:25:00 [20/Mar/2023:13:25:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.012 0.012
              Mar 20 13:25:10 [20/Mar/2023:13:25:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
              Mar 20 13:25:11 I, [2023-03-20T13:25:11.289976 #8] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
              Mar 20 13:25:20 2023/03/20 13:25:20 [error] 28#28: *18 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:25:20 2023/03/20 13:25:20 [warn] 28#28: *18 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:25:20 [20/Mar/2023:13:25:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.012 0.011
              Mar 20 13:25:30 [20/Mar/2023:13:25:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
              Mar 20 13:25:40 [20/Mar/2023:13:25:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.032 0.030
              Mar 20 13:25:50 [20/Mar/2023:13:25:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.003
              Mar 20 13:26:00 2023/03/20 13:26:00 [error] 28#28: *27 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:26:00 2023/03/20 13:26:00 [warn] 28#28: *27 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:26:00 [20/Mar/2023:13:26:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.008 0.009
              Mar 20 13:26:10 [20/Mar/2023:13:26:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.016 0.016
              Mar 20 13:26:11 I, [2023-03-20T13:26:11.263038 #8] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
              Mar 20 13:26:20 [20/Mar/2023:13:26:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.012 0.012
              Mar 20 13:26:30 [20/Mar/2023:13:26:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.003
              Mar 20 13:26:40 2023/03/20 13:26:40 [error] 28#28: *36 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:26:40 2023/03/20 13:26:40 [warn] 28#28: *36 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:26:40 [20/Mar/2023:13:26:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.008 0.008
              Mar 20 13:26:50 [20/Mar/2023:13:26:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.012 0.011
              Mar 20 13:27:00 [20/Mar/2023:13:27:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.012 0.013
              Mar 20 13:27:10 [20/Mar/2023:13:27:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.005
              Mar 20 13:27:11 I, [2023-03-20T13:27:11.274329 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
              Mar 20 13:27:20 2023/03/20 13:27:20 [error] 28#28: *45 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:27:20 2023/03/20 13:27:20 [warn] 28#28: *45 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:27:20 [20/Mar/2023:13:27:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.000 0.003
              Mar 20 13:27:30 [20/Mar/2023:13:27:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.004
              Mar 20 13:27:40 [20/Mar/2023:13:27:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.003
              Mar 20 13:27:50 [20/Mar/2023:13:27:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
              Mar 20 13:28:00 2023/03/20 13:28:00 [error] 28#28: *54 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:28:00 2023/03/20 13:28:00 [warn] 28#28: *54 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:28:00 [20/Mar/2023:13:28:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.000 0.003
              Mar 20 13:28:10 [20/Mar/2023:13:28:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
              Mar 20 13:28:11 I, [2023-03-20T13:28:11.283751 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
              Mar 20 13:28:20 [20/Mar/2023:13:28:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.008 0.007
              Mar 20 13:28:29 13:M 20 Mar 2023 13:28:29.017 * 10 changes in 300 seconds. Saving...
              Mar 20 13:28:29 13:M 20 Mar 2023 13:28:29.017 * Background saving started by pid 29
              Mar 20 13:28:29 29:C 20 Mar 2023 13:28:29.019 * DB saved on disk
              Mar 20 13:28:29 29:C 20 Mar 2023 13:28:29.020 * RDB: 0 MB of memory used by copy-on-write
              Mar 20 13:28:29 13:M 20 Mar 2023 13:28:29.118 * Background saving terminated with success
              Mar 20 13:28:30 [20/Mar/2023:13:28:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
              Mar 20 13:28:40 2023/03/20 13:28:40 [error] 28#28: *63 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:28:40 2023/03/20 13:28:40 [warn] 28#28: *63 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:28:40 [20/Mar/2023:13:28:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.000 0.006
              Mar 20 13:28:50 [20/Mar/2023:13:28:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
              Mar 20 13:29:00 [20/Mar/2023:13:29:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
              Mar 20 13:29:10 [20/Mar/2023:13:29:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
              Mar 20 13:29:11 I, [2023-03-20T13:29:11.284618 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
              Mar 20 13:29:20 2023/03/20 13:29:20 [error] 28#28: *72 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:29:20 2023/03/20 13:29:20 [warn] 28#28: *72 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
              Mar 20 13:29:20 [20/Mar/2023:13:29:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.000 0.001
              Mar 20 13:29:30 [20/Mar/2023:13:29:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.008 0.010
              Mar 20 13:29:40 [20/Mar/2023:13:29:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.001
              

              I use Cloudron with Gandi & Hetzner

              jdaviescoatesJ 1 Reply Last reply
              0
              • jdaviescoatesJ jdaviescoates

                @jdaviescoates said in some first findings:

                When I tried to create the first group, it also failed, i.e. I hit the Start Group button and it did something, but then I was just back where I was as is nothing happened:

                Ah, it seemingly ran out of memory, so that'd explain why it didn't work the first time:

                ec46ff30-e0c1-4fcb-8a4e-c3bb528e81f9-image.png

                To be fair, Cloudron did warn me that my server was running low of memory when I installed it but I proceeded anyway!

                But I just uninstalled and then reinstalled after stopping a couple of installed by unused Discourse forums (which are memory hogs). Didn't get the RAM warning when installed.

                Looked at the logs as soon as it said the app was running (i.e. before even clicking on the link) and those errors and warnings are already there (looks to me like they are present during the start-up process):

                Mar 20 13:23:58 ==> Starting app
                Mar 20 13:23:58 2023-03-20 13:23:58,502 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
                Mar 20 13:23:58 2023-03-20 13:23:58,502 INFO Included extra file "/etc/supervisor/conf.d/loomio-channels.conf" during parsing
                Mar 20 13:23:58 2023-03-20 13:23:58,502 INFO Included extra file "/etc/supervisor/conf.d/loomio-sidekiq.conf" during parsing
                Mar 20 13:23:58 2023-03-20 13:23:58,502 INFO Included extra file "/etc/supervisor/conf.d/loomio.conf" during parsing
                Mar 20 13:23:58 2023-03-20 13:23:58,502 INFO Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
                Mar 20 13:23:58 2023-03-20 13:23:58,506 INFO RPC interface 'supervisor' initialized
                Mar 20 13:23:58 2023-03-20 13:23:58,506 CRIT Server 'unix_http_server' running without any HTTP authentication checking
                Mar 20 13:23:58 2023-03-20 13:23:58,507 INFO supervisord started with pid 1
                Mar 20 13:23:59 2023-03-20 13:23:59,510 INFO spawned: 'loomio' with pid 18
                Mar 20 13:23:59 2023-03-20 13:23:59,513 INFO spawned: 'loomio-sidekiq' with pid 19
                Mar 20 13:23:59 2023-03-20 13:23:59,515 INFO spawned: 'loomio-channels' with pid 20
                Mar 20 13:23:59 2023-03-20 13:23:59,518 INFO spawned: 'nginx' with pid 21
                Mar 20 13:23:59
                Mar 20 13:23:59 > loomio_channel_server@0.0.1 start
                Mar 20 13:23:59 > node --harmony index.js
                Mar 20 13:23:59
                Mar 20 13:24:00 2023/03/20 13:24:00 [error] 28#28: *1 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:24:00 2023/03/20 13:24:00 [warn] 28#28: *1 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:24:00 2023/03/20 13:24:00 [error] 28#28: *1 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:24:00 2023/03/20 13:24:00 [warn] 28#28: *1 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:24:00 [20/Mar/2023:13:24:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 502 295 "-" 0.000, 0.008 0.009
                Healtheck error got response status 5022023-03-20T13:24:00.000Z [18] Puma starting in cluster mode...
                Mar 20 13:24:00 [18] * Puma version: 6.1.1 (ruby 2.7.6-p219) ("The Way Up")
                Mar 20 13:24:00 [18] * Min threads: 12
                Mar 20 13:24:00 [18] * Max threads: 12
                Mar 20 13:24:00 [18] * Environment: production
                Mar 20 13:24:00 [18] * Master PID: 18
                Mar 20 13:24:00 [18] * Workers: 10
                Mar 20 13:24:00 [18] * Restarts: (✔) hot (✖) phased
                Mar 20 13:24:00 [18] * Preloading application
                Mar 20 13:24:00 Allowed origin https://loomio.uniteddiversity.coop
                Mar 20 13:24:00 2023-03-20 13:24:00,641 INFO success: loomio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
                Mar 20 13:24:00 2023-03-20 13:24:00,641 INFO success: loomio-sidekiq entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
                Mar 20 13:24:00 2023-03-20 13:24:00,641 INFO success: loomio-channels entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
                Mar 20 13:24:00 2023-03-20 13:24:00,641 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
                Mar 20 13:24:00 booting bots!
                Mar 20 13:24:01 bot redis connected
                Mar 20 13:24:01 /usr/local/lib/ruby/2.7.0/net/protocol.rb:66: warning: already initialized constant Net::ProtocRetryError
                Mar 20 13:24:01 /app/code/loomio/vendor/gems/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:68: warning: previous definition of ProtocRetryError was here
                Mar 20 13:24:01 /usr/local/lib/ruby/2.7.0/net/protocol.rb:206: warning: already initialized constant Net::BufferedIO::BUFSIZE
                Mar 20 13:24:01 /app/code/loomio/vendor/gems/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:208: warning: previous definition of BUFSIZE was here
                Mar 20 13:24:01 /usr/local/lib/ruby/2.7.0/net/protocol.rb:503: warning: already initialized constant Net::NetPrivate::Socket
                Mar 20 13:24:01 /app/code/loomio/vendor/gems/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:504: warning: previous definition of Socket was here
                Mar 20 13:24:01 /usr/local/lib/ruby/2.7.0/net/protocol.rb:66: warning: already initialized constant Net::ProtocRetryError
                Mar 20 13:24:01 /app/code/loomio/vendor/gems/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:68: warning: previous definition of ProtocRetryError was here
                Mar 20 13:24:01 /usr/local/lib/ruby/2.7.0/net/protocol.rb:206: warning: already initialized constant Net::BufferedIO::BUFSIZE
                Mar 20 13:24:01 /app/code/loomio/vendor/gems/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:208: warning: previous definition of BUFSIZE was here
                Mar 20 13:24:01 /usr/local/lib/ruby/2.7.0/net/protocol.rb:503: warning: already initialized constant Net::NetPrivate::Socket
                Mar 20 13:24:01 /app/code/loomio/vendor/gems/ruby/2.7.0/gems/net-protocol-0.1.3/lib/net/protocol.rb:504: warning: previous definition of Socket was here
                Mar 20 13:24:01 /app/code/loomio/config/initializers/sidekiq.rb:2: warning: Sidekiq's Delayed Extensions will be removed in Sidekiq 7.0
                Mar 20 13:24:01 `Redis#exists(key)` will return an Integer by default in redis-rb 4.3. The option to explicitly disable this behaviour via `Redis.exists_returns_integer` will be removed in 5.0. You should use `exists?` instead.
                Mar 20 13:24:02 /app/code/loomio/config/initializers/sidekiq.rb:2: warning: Sidekiq's Delayed Extensions will be removed in Sidekiq 7.0
                Mar 20 13:24:02 `Redis#exists(key)` will return an Integer by default in redis-rb 4.3. The option to explicitly disable this behaviour via `Redis.exists_returns_integer` will be removed in 5.0. You should use `exists?` instead.
                Mar 20 13:24:05 [18] * Listening on http://0.0.0.0:3000
                Mar 20 13:24:05 [18] Use Ctrl-C to stop
                Mar 20 13:24:05 [18] - Worker 0 (PID: 59) booted in 0.14s, phase: 0
                Mar 20 13:24:05 [18] - Worker 1 (PID: 66) booted in 0.13s, phase: 0
                Mar 20 13:24:05 [18] - Worker 2 (PID: 77) booted in 0.12s, phase: 0
                Mar 20 13:24:05 [18] - Worker 3 (PID: 90) booted in 0.1s, phase: 0
                Mar 20 13:24:05 [18] - Worker 4 (PID: 100) booted in 0.09s, phase: 0
                Mar 20 13:24:05 [18] - Worker 5 (PID: 113) booted in 0.08s, phase: 0
                Mar 20 13:24:05 [18] - Worker 6 (PID: 129) booted in 0.06s, phase: 0
                Mar 20 13:24:05 [18] - Worker 7 (PID: 152) booted in 0.05s, phase: 0
                Mar 20 13:24:05 [18] - Worker 8 (PID: 180) booted in 0.04s, phase: 0
                Mar 20 13:24:05 [18] - Worker 9 (PID: 212) booted in 0.0s, phase: 0
                Mar 20 13:24:05 2023-03-20T13:24:05.696Z pid=19 tid=877 INFO: Booted Rails 6.1.7.2 application in production environment
                Mar 20 13:24:05 2023-03-20T13:24:05.696Z pid=19 tid=877 INFO: Running in ruby 2.7.6p219 (2022-04-12 revision c9c2245c0a) [x86_64-linux]
                Mar 20 13:24:05 2023-03-20T13:24:05.697Z pid=19 tid=877 INFO: See LICENSE and the LGPL-3.0 for licensing details.
                Mar 20 13:24:05 2023-03-20T13:24:05.697Z pid=19 tid=877 INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org
                Mar 20 13:24:05 2023-03-20T13:24:05.699Z pid=19 tid=877 WARN:
                Mar 20 13:24:05
                Mar 20 13:24:05 WARNING: Your Redis instance will evict Sidekiq data under heavy load.
                Mar 20 13:24:05 The 'noeviction' maxmemory policy is recommended (current policy: 'allkeys-lru').
                Mar 20 13:24:05 See: https://github.com/mperham/sidekiq/wiki/Using-Redis#memory
                Mar 20 13:24:05
                Mar 20 13:24:05
                Mar 20 13:24:10 2023/03/20 13:24:10 [error] 28#28: *4 no live upstreams while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://localhost/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:24:10 [20/Mar/2023:13:24:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 502 295 "-" 0.000 0.000
                Healtheck error got response status 5022023-03-20T13:24:20.000Z [20/Mar/2023:13:24:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.002
                Mar 20 13:24:30 [20/Mar/2023:13:24:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.004
                Mar 20 13:23:27 Starting supervisor
                Mar 20 13:23:27 2023-03-20 13:23:27,417 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
                Mar 20 13:23:27 2023-03-20 13:23:27,417 INFO Included extra file "/etc/supervisor/conf.d/redis-service.conf" during parsing
                Mar 20 13:23:27 2023-03-20 13:23:27,417 INFO Included extra file "/etc/supervisor/conf.d/redis.conf" during parsing
                Mar 20 13:23:27 2023-03-20 13:23:27,427 INFO RPC interface 'supervisor' initialized
                Mar 20 13:23:27 2023-03-20 13:23:27,427 CRIT Server 'inet_http_server' running without any HTTP authentication checking
                Mar 20 13:23:27 2023-03-20 13:23:27,427 INFO RPC interface 'supervisor' initialized
                Mar 20 13:23:27 2023-03-20 13:23:27,427 CRIT Server 'unix_http_server' running without any HTTP authentication checking
                Mar 20 13:23:27 2023-03-20 13:23:27,427 INFO supervisord started with pid 1
                Mar 20 13:23:28 2023-03-20 13:23:28,431 INFO spawned: 'redis' with pid 13
                Mar 20 13:23:28 2023-03-20 13:23:28,434 INFO spawned: 'redis-service' with pid 14
                Mar 20 13:23:28 13:C 20 Mar 2023 13:23:28.465 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
                Mar 20 13:23:28 13:C 20 Mar 2023 13:23:28.465 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=13, just started
                Mar 20 13:23:28 13:C 20 Mar 2023 13:23:28.465 # Configuration loaded
                Mar 20 13:23:28 13:M 20 Mar 2023 13:23:28.478 * Running mode=standalone, port=6379.
                Mar 20 13:23:28 13:M 20 Mar 2023 13:23:28.478 # Server initialized
                Mar 20 13:23:28 13:M 20 Mar 2023 13:23:28.478 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
                Mar 20 13:23:28 13:M 20 Mar 2023 13:23:28.478 * Ready to accept connections
                Mar 20 13:23:28 Redis service endpoint listening on http://:::3000
                Mar 20 13:23:29 2023-03-20 13:23:29,865 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
                Mar 20 13:23:29 2023-03-20 13:23:29,865 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
                Mar 20 13:23:42 [GET] /healthcheck
                Mar 20 13:24:40 2023/03/20 13:24:40 [error] 28#28: *9 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:24:40 2023/03/20 13:24:40 [warn] 28#28: *9 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:24:40 [20/Mar/2023:13:24:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.004 0.004
                Mar 20 13:24:50 [20/Mar/2023:13:24:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.008 0.007
                Mar 20 13:25:00 [20/Mar/2023:13:25:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.012 0.012
                Mar 20 13:25:10 [20/Mar/2023:13:25:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
                Mar 20 13:25:11 I, [2023-03-20T13:25:11.289976 #8] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
                Mar 20 13:25:20 2023/03/20 13:25:20 [error] 28#28: *18 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:25:20 2023/03/20 13:25:20 [warn] 28#28: *18 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:25:20 [20/Mar/2023:13:25:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.012 0.011
                Mar 20 13:25:30 [20/Mar/2023:13:25:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
                Mar 20 13:25:40 [20/Mar/2023:13:25:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.032 0.030
                Mar 20 13:25:50 [20/Mar/2023:13:25:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.003
                Mar 20 13:26:00 2023/03/20 13:26:00 [error] 28#28: *27 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:26:00 2023/03/20 13:26:00 [warn] 28#28: *27 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:26:00 [20/Mar/2023:13:26:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.008 0.009
                Mar 20 13:26:10 [20/Mar/2023:13:26:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.016 0.016
                Mar 20 13:26:11 I, [2023-03-20T13:26:11.263038 #8] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
                Mar 20 13:26:20 [20/Mar/2023:13:26:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.012 0.012
                Mar 20 13:26:30 [20/Mar/2023:13:26:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.003
                Mar 20 13:26:40 2023/03/20 13:26:40 [error] 28#28: *36 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:26:40 2023/03/20 13:26:40 [warn] 28#28: *36 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:26:40 [20/Mar/2023:13:26:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.008 0.008
                Mar 20 13:26:50 [20/Mar/2023:13:26:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.012 0.011
                Mar 20 13:27:00 [20/Mar/2023:13:27:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.012 0.013
                Mar 20 13:27:10 [20/Mar/2023:13:27:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.005
                Mar 20 13:27:11 I, [2023-03-20T13:27:11.274329 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
                Mar 20 13:27:20 2023/03/20 13:27:20 [error] 28#28: *45 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:27:20 2023/03/20 13:27:20 [warn] 28#28: *45 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:27:20 [20/Mar/2023:13:27:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.000 0.003
                Mar 20 13:27:30 [20/Mar/2023:13:27:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.004
                Mar 20 13:27:40 [20/Mar/2023:13:27:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.003
                Mar 20 13:27:50 [20/Mar/2023:13:27:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
                Mar 20 13:28:00 2023/03/20 13:28:00 [error] 28#28: *54 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:28:00 2023/03/20 13:28:00 [warn] 28#28: *54 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:28:00 [20/Mar/2023:13:28:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.000 0.003
                Mar 20 13:28:10 [20/Mar/2023:13:28:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
                Mar 20 13:28:11 I, [2023-03-20T13:28:11.283751 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
                Mar 20 13:28:20 [20/Mar/2023:13:28:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.008 0.007
                Mar 20 13:28:29 13:M 20 Mar 2023 13:28:29.017 * 10 changes in 300 seconds. Saving...
                Mar 20 13:28:29 13:M 20 Mar 2023 13:28:29.017 * Background saving started by pid 29
                Mar 20 13:28:29 29:C 20 Mar 2023 13:28:29.019 * DB saved on disk
                Mar 20 13:28:29 29:C 20 Mar 2023 13:28:29.020 * RDB: 0 MB of memory used by copy-on-write
                Mar 20 13:28:29 13:M 20 Mar 2023 13:28:29.118 * Background saving terminated with success
                Mar 20 13:28:30 [20/Mar/2023:13:28:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
                Mar 20 13:28:40 2023/03/20 13:28:40 [error] 28#28: *63 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:28:40 2023/03/20 13:28:40 [warn] 28#28: *63 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:28:40 [20/Mar/2023:13:28:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.000 0.006
                Mar 20 13:28:50 [20/Mar/2023:13:28:50 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
                Mar 20 13:29:00 [20/Mar/2023:13:29:00 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
                Mar 20 13:29:10 [20/Mar/2023:13:29:10 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000 0.001
                Mar 20 13:29:11 I, [2023-03-20T13:29:11.284618 #7] INFO -- imap_poller/loomio_relay: Loomio IMAP Polling: CLOUDRON_MAIL_IMAP_SERVER env variable hasn't been set, exiting...
                Mar 20 13:29:20 2023/03/20 13:29:20 [error] 28#28: *72 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:29:20 2023/03/20 13:29:20 [warn] 28#28: *72 upstream server temporarily disabled while connecting to upstream, client: 172.18.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://[::1]:3000/", host: "loomio.uniteddiversity.coop"
                Mar 20 13:29:20 [20/Mar/2023:13:29:20 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.000, 0.000 0.001
                Mar 20 13:29:30 [20/Mar/2023:13:29:30 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.008 0.010
                Mar 20 13:29:40 [20/Mar/2023:13:29:40 +0000] 172.18.0.1 "GET / HTTP/1.1" "Mozilla (CloudronHealth)" 301 197 "-" 0.004 0.001
                
                jdaviescoatesJ Offline
                jdaviescoatesJ Offline
                jdaviescoates
                wrote on last edited by jdaviescoates
                #6

                But, with enough memory available, creating the first user and groups seemed to go smoothly (in spite of those errors and warnings).

                I use Cloudron with Gandi & Hetzner

                luckowL 1 Reply Last reply
                1
                • jdaviescoatesJ jdaviescoates

                  But, with enough memory available, creating the first user and groups seemed to go smoothly (in spite of those errors and warnings).

                  luckowL Offline
                  luckowL Offline
                  luckow
                  translator
                  wrote on last edited by
                  #7

                  @jdaviescoates same here. Now with 4 GB RAM

                  Pronouns: he/him | Primary language: German

                  jdaviescoatesJ 1 Reply Last reply
                  1
                  • luckowL luckow

                    @jdaviescoates same here. Now with 4 GB RAM

                    jdaviescoatesJ Offline
                    jdaviescoatesJ Offline
                    jdaviescoates
                    wrote on last edited by
                    #8

                    @luckow said in some first findings:

                    @jdaviescoates same here. Now with 4 GB RAM

                    I didn't actually increase the memory available for Loomio, just reduced how much memory my server was using.

                    I use Cloudron with Gandi & Hetzner

                    1 Reply Last reply
                    0
                    • jdaviescoatesJ Offline
                      jdaviescoatesJ Offline
                      jdaviescoates
                      wrote on last edited by jdaviescoates
                      #9

                      More thoughts:

                      • LDAP doesn't seem to be enabled (even though during the install process it implies that it is). It seems the only way to login is by creating a new account via email.

                      • Whenever you create a new account you instantly land on the screen where you start a new group. This is a bit confusing (but perhaps this is just how self-hosted Loomio works?).

                      I use Cloudron with Gandi & Hetzner

                      girishG 1 Reply Last reply
                      0
                      • vladimir.dV Offline
                        vladimir.dV Offline
                        vladimir.d
                        wrote on last edited by vladimir.d
                        #10
                        • There is no LDAP support in Loomio so LDAP will be also disabled in the next version of the cloudron app.
                          They seem to be supporting OAuth, SAML providers but there is a lack of details in the documentation how to set it up. It needs some further research. As far as I can see some environment variables need to be setup and /app/data/.env can be used for that.

                        • Yes, it redirects to a new group creating form when a new account created. This is how it works and there seems no way to amend it for now.

                        1 Reply Last reply
                        2
                        • vladimir.dV Offline
                          vladimir.dV Offline
                          vladimir.d
                          wrote on last edited by
                          #11

                          A new Loomio app version 0.3.0 has been released.
                          It has websockets connection issue fixed and switched ldap and IMAP polling off as it hasn't been implemented in Loomio yet.

                          1 Reply Last reply
                          4
                          • nebulonN nebulon marked this topic as a regular topic on
                          • jdaviescoatesJ jdaviescoates

                            More thoughts:

                            • LDAP doesn't seem to be enabled (even though during the install process it implies that it is). It seems the only way to login is by creating a new account via email.

                            • Whenever you create a new account you instantly land on the screen where you start a new group. This is a bit confusing (but perhaps this is just how self-hosted Loomio works?).

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

                            @jdaviescoates said in some first findings:

                            Whenever you create a new account you instantly land on the screen where you start a new group. This is a bit confusing (but perhaps this is just how self-hosted Loomio works?).

                            Just played around with the app a bit. You sign up first and create groups. The groups can have a friendly URL like https://loomio.example.com/my-community . You can then disable group creation and then even maybe user registration - https://docs.cloudron.io/apps/loomio/#registration . You then just pass around the community link directly instead of the app's base domain link. People can register and network.

                            1 Reply Last reply
                            2
                            • Sam_ukS Offline
                              Sam_ukS Offline
                              Sam_uk
                              wrote on last edited by
                              #13

                              4Gb of memory allocated. I'm still unable to create a group.

                              As an aside here's some SSO info https://www.loomio.com/d/CL8Xr5kW/is-sso-compatible-with-selfhosted-loomio-/15

                              girishG 2 Replies Last reply
                              1
                              • Sam_ukS Sam_uk

                                4Gb of memory allocated. I'm still unable to create a group.

                                As an aside here's some SSO info https://www.loomio.com/d/CL8Xr5kW/is-sso-compatible-with-selfhosted-loomio-/15

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

                                @Sam_uk I can reproduce the group creation issue. Investigating.

                                19:27:44 - source=rack-timeout id=25868553-6852-4fba-af24-66b22494e20c wait=1ms timeout=15000ms state=ready
                                19:27:44 - method=POST path=/api/v1/groups format=json controller=API::V1::GroupsController action=create status=500 error='OpenURI::HTTPError: 403 Forbidden' duration=431.19 view=0.00 db=1.66
                                19:27:44 - 
                                19:27:44 - OpenURI::HTTPError (403 Forbidden):
                                19:27:44 - 
                                19:27:44 - app/services/group_service.rb:78:in `create'
                                19:27:44 - app/controllers/api/v1/snorlax_base.rb:47:in `create_action'
                                19:27:44 - app/controllers/api/v1/snorlax_base.rb:20:in `create'
                                19:27:44 - app/helpers/locales_helper.rb:8:in `use_preferred_locale'
                                19:27:44 - source=rack-timeout id=25868553-6852-4fba-af24-66b22494e20c wait=1ms timeout=15000ms service=436ms state=completed
                                
                                
                                1 Reply Last reply
                                1
                                • Sam_ukS Sam_uk

                                  4Gb of memory allocated. I'm still unable to create a group.

                                  As an aside here's some SSO info https://www.loomio.com/d/CL8Xr5kW/is-sso-compatible-with-selfhosted-loomio-/15

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

                                  @Sam_uk this should be fixed now.

                                  1 Reply Last reply
                                  1
                                  • nebulonN nebulon marked this topic as a question on
                                  • Sam_ukS Offline
                                    Sam_ukS Offline
                                    Sam_uk
                                    wrote on last edited by
                                    #16

                                    Yes it's now working. Thanks.

                                    1 Reply Last reply
                                    2
                                    • girishG girish 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