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. Discuss
  3. Uptime Monitoring

Uptime Monitoring

Scheduled Pinned Locked Moved Discuss
27 Posts 13 Posters 3.0k Views 15 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.
    • J jagan

      I am actually going to propose uptime-kuma as an app for cloudron. Its brand new.
      Please check it out. https://github.com/louislam/uptime-kuma
      Perhaps you can help package it please? It has a docker version.

      831fcf65-858f-4671-b8bc-6ec5f7979611-image.png

      marcusquinnM Offline
      marcusquinnM Offline
      marcusquinn
      wrote on last edited by
      #16

      @jagan This does look good! Deserves its own post.

      Web Design https://www.evergreen.je
      Development https://brandlight.org
      Life https://marcusquinn.com

      1 Reply Last reply
      1
      • M Offline
        M Offline
        mazarian
        wrote on last edited by
        #17

        This looks like exactly what I've been looking for for a really long time! Thanks for bringing this over to Cloudron. 😃 I tried installing it via Cloudron CLI from my Mac and it's throwing an error when I run cloudron build. It's my first time installing a 3rd party app, so maybe I'm doing it totally wrong.

        I signed into my Cloudon instance in CLI, cloned the repo onto my computer, went into the directory, and typed cloudron build.

        I've made sure my Node instance is up to date (using Homebrew) and I also have Docker installed via Homebrew as well.

        Any help would greatly be appreciated!

        Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f
        
        invalid argument "git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f" for "-t, --tag" flag: invalid reference format: repository name must be lowercase
        See 'docker build --help'.
        node:child_process:903
            throw err;
            ^
        
        Error: Command failed: docker build  -t git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f -f Dockerfile  /Users/michael/Downloads/cloudron-uptime-kuma-app
            at checkExecSyncError (node:child_process:826:11)
            at execSync (node:child_process:900:15)
            at buildLocal (/usr/local/lib/node_modules/cloudron/src/build-actions.js:187:5)
            at Command.build (/usr/local/lib/node_modules/cloudron/src/build-actions.js:349:9)
            at Command.listener [as _actionHandler] (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:426:31)
            at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:1002:14)
            at Command._dispatchSubcommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:953:18)
            at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:970:12)
            at Command.parse (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:801:10)
            at Object.<anonymous> (/usr/local/lib/node_modules/cloudron/bin/cloudron:261:9) {
          status: 125,
          signal: null,
          output: [ null, null, null ],
          pid: 9877,
          stdout: null,
          stderr: null
        }
        
        ? timconsidineT girishG 3 Replies Last reply
        0
        • M mazarian

          This looks like exactly what I've been looking for for a really long time! Thanks for bringing this over to Cloudron. 😃 I tried installing it via Cloudron CLI from my Mac and it's throwing an error when I run cloudron build. It's my first time installing a 3rd party app, so maybe I'm doing it totally wrong.

          I signed into my Cloudon instance in CLI, cloned the repo onto my computer, went into the directory, and typed cloudron build.

          I've made sure my Node instance is up to date (using Homebrew) and I also have Docker installed via Homebrew as well.

          Any help would greatly be appreciated!

          Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f
          
          invalid argument "git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f" for "-t, --tag" flag: invalid reference format: repository name must be lowercase
          See 'docker build --help'.
          node:child_process:903
              throw err;
              ^
          
          Error: Command failed: docker build  -t git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f -f Dockerfile  /Users/michael/Downloads/cloudron-uptime-kuma-app
              at checkExecSyncError (node:child_process:826:11)
              at execSync (node:child_process:900:15)
              at buildLocal (/usr/local/lib/node_modules/cloudron/src/build-actions.js:187:5)
              at Command.build (/usr/local/lib/node_modules/cloudron/src/build-actions.js:349:9)
              at Command.listener [as _actionHandler] (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:426:31)
              at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:1002:14)
              at Command._dispatchSubcommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:953:18)
              at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:970:12)
              at Command.parse (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:801:10)
              at Object.<anonymous> (/usr/local/lib/node_modules/cloudron/bin/cloudron:261:9) {
            status: 125,
            signal: null,
            output: [ null, null, null ],
            pid: 9877,
            stdout: null,
            stderr: null
          }
          
          ? Offline
          ? Offline
          A Former User
          wrote on last edited by
          #18

          @mazarian Oh weird... not sure why its just default trying to use my docker registry... O_O

          Any docker wizards here who might have some insight?

          1 Reply Last reply
          0
          • M mazarian

            This looks like exactly what I've been looking for for a really long time! Thanks for bringing this over to Cloudron. 😃 I tried installing it via Cloudron CLI from my Mac and it's throwing an error when I run cloudron build. It's my first time installing a 3rd party app, so maybe I'm doing it totally wrong.

            I signed into my Cloudon instance in CLI, cloned the repo onto my computer, went into the directory, and typed cloudron build.

            I've made sure my Node instance is up to date (using Homebrew) and I also have Docker installed via Homebrew as well.

            Any help would greatly be appreciated!

            Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f
            
            invalid argument "git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f" for "-t, --tag" flag: invalid reference format: repository name must be lowercase
            See 'docker build --help'.
            node:child_process:903
                throw err;
                ^
            
            Error: Command failed: docker build  -t git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f -f Dockerfile  /Users/michael/Downloads/cloudron-uptime-kuma-app
                at checkExecSyncError (node:child_process:826:11)
                at execSync (node:child_process:900:15)
                at buildLocal (/usr/local/lib/node_modules/cloudron/src/build-actions.js:187:5)
                at Command.build (/usr/local/lib/node_modules/cloudron/src/build-actions.js:349:9)
                at Command.listener [as _actionHandler] (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:426:31)
                at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:1002:14)
                at Command._dispatchSubcommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:953:18)
                at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:970:12)
                at Command.parse (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:801:10)
                at Object.<anonymous> (/usr/local/lib/node_modules/cloudron/bin/cloudron:261:9) {
              status: 125,
              signal: null,
              output: [ null, null, null ],
              pid: 9877,
              stdout: null,
              stderr: null
            }
            
            timconsidineT Offline
            timconsidineT Offline
            timconsidine
            App Dev
            wrote on last edited by
            #19

            @mazarian just to provide some some other experience, I downloaded @atridad repo files, but I did not use cloudron build. I went "the long way".

            docker build -t <myrepo>/<appname>:<tag> .  
            docker push <myrepo>/<appname>:<tag>
            cloudron install --image <myrepo>/<appname>:<tag>
            

            NB the trailing dot on 1st line
            With this the build/install was seamless
            Kuma now working brilliantly and I have deleted my UptimeRobot account.

            thanks again @atridad

            ? M 2 Replies Last reply
            0
            • timconsidineT timconsidine

              @mazarian just to provide some some other experience, I downloaded @atridad repo files, but I did not use cloudron build. I went "the long way".

              docker build -t <myrepo>/<appname>:<tag> .  
              docker push <myrepo>/<appname>:<tag>
              cloudron install --image <myrepo>/<appname>:<tag>
              

              NB the trailing dot on 1st line
              With this the build/install was seamless
              Kuma now working brilliantly and I have deleted my UptimeRobot account.

              thanks again @atridad

              ? Offline
              ? Offline
              A Former User
              wrote on last edited by
              #20

              @timconsidine Perhaps I should change my instructions? @staff does the cloudron build command do some extra stuff that would be causing this?

              timconsidineT 1 Reply Last reply
              0
              • timconsidineT timconsidine

                @mazarian just to provide some some other experience, I downloaded @atridad repo files, but I did not use cloudron build. I went "the long way".

                docker build -t <myrepo>/<appname>:<tag> .  
                docker push <myrepo>/<appname>:<tag>
                cloudron install --image <myrepo>/<appname>:<tag>
                

                NB the trailing dot on 1st line
                With this the build/install was seamless
                Kuma now working brilliantly and I have deleted my UptimeRobot account.

                thanks again @atridad

                M Offline
                M Offline
                mazarian
                wrote on last edited by
                #21

                @timconsidine Thanks for this! I'm not sure how much of my issue had to do with my Mac environment but I was able to get it all setup using Ubuntu using your method and it worked like a charm!

                timconsidineT 1 Reply Last reply
                1
                • M mazarian

                  @timconsidine Thanks for this! I'm not sure how much of my issue had to do with my Mac environment but I was able to get it all setup using Ubuntu using your method and it worked like a charm!

                  timconsidineT Offline
                  timconsidineT Offline
                  timconsidine
                  App Dev
                  wrote on last edited by timconsidine
                  #22

                  @mazarian Great
                  I should have mentioned that I am a Mac user, and was doing this on a Mac Mini running Big Sur and Docker Desktop. Maybe too late to be helpful, sorry.

                  1 Reply Last reply
                  0
                  • ? A Former User

                    @timconsidine Perhaps I should change my instructions? @staff does the cloudron build command do some extra stuff that would be causing this?

                    timconsidineT Offline
                    timconsidineT Offline
                    timconsidine
                    App Dev
                    wrote on last edited by
                    #23

                    @atridad said in Uptime Monitoring:

                    @timconsidine Perhaps I should change my instructions?

                    errr, I'm not qualified on that !
                    I blunder about, find what works for me and tend to stick to that.

                    ? 1 Reply Last reply
                    0
                    • timconsidineT timconsidine

                      @atridad said in Uptime Monitoring:

                      @timconsidine Perhaps I should change my instructions?

                      errr, I'm not qualified on that !
                      I blunder about, find what works for me and tend to stick to that.

                      ? Offline
                      ? Offline
                      A Former User
                      wrote on last edited by
                      #24

                      @timconsidine lol with packaging I'm the same way tbh. Cloudron was my first time editing or making a Dockerfile

                      1 Reply Last reply
                      0
                      • M mazarian

                        This looks like exactly what I've been looking for for a really long time! Thanks for bringing this over to Cloudron. 😃 I tried installing it via Cloudron CLI from my Mac and it's throwing an error when I run cloudron build. It's my first time installing a 3rd party app, so maybe I'm doing it totally wrong.

                        I signed into my Cloudon instance in CLI, cloned the repo onto my computer, went into the directory, and typed cloudron build.

                        I've made sure my Node instance is up to date (using Homebrew) and I also have Docker installed via Homebrew as well.

                        Any help would greatly be appreciated!

                        Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f
                        
                        invalid argument "git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f" for "-t, --tag" flag: invalid reference format: repository name must be lowercase
                        See 'docker build --help'.
                        node:child_process:903
                            throw err;
                            ^
                        
                        Error: Command failed: docker build  -t git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f -f Dockerfile  /Users/michael/Downloads/cloudron-uptime-kuma-app
                            at checkExecSyncError (node:child_process:826:11)
                            at execSync (node:child_process:900:15)
                            at buildLocal (/usr/local/lib/node_modules/cloudron/src/build-actions.js:187:5)
                            at Command.build (/usr/local/lib/node_modules/cloudron/src/build-actions.js:349:9)
                            at Command.listener [as _actionHandler] (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:426:31)
                            at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:1002:14)
                            at Command._dispatchSubcommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:953:18)
                            at Command._parseCommand (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:970:12)
                            at Command.parse (/usr/local/lib/node_modules/cloudron/node_modules/commander/index.js:801:10)
                            at Object.<anonymous> (/usr/local/lib/node_modules/cloudron/bin/cloudron:261:9) {
                          status: 125,
                          signal: null,
                          output: [ null, null, null ],
                          pid: 9877,
                          stdout: null,
                          stderr: null
                        }
                        
                        girishG Offline
                        girishG Offline
                        girish
                        Staff
                        wrote on last edited by
                        #25

                        @mazarian said in Uptime Monitoring:

                        Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f

                        I think this happenned because the docker repository was specified incorrectly when you did cloudron build. You can always cloudron build --set-repository again and it will ask you again for the repository name. The repo name should like girish/cloudron-uptime-kuma or something like that. The first part is your handle on docker hub (or equivalent). The second part is the repository name. In docker terminology, a repo is something that holds many images.

                        mehdiM M 2 Replies Last reply
                        1
                        • girishG girish

                          @mazarian said in Uptime Monitoring:

                          Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f

                          I think this happenned because the docker repository was specified incorrectly when you did cloudron build. You can always cloudron build --set-repository again and it will ask you again for the repository name. The repo name should like girish/cloudron-uptime-kuma or something like that. The first part is your handle on docker hub (or equivalent). The second part is the repository name. In docker terminology, a repo is something that holds many images.

                          mehdiM Offline
                          mehdiM Offline
                          mehdi
                          App Dev
                          wrote on last edited by
                          #26
                          This post is deleted!
                          1 Reply Last reply
                          0
                          • girishG girish

                            @mazarian said in Uptime Monitoring:

                            Building locally as git.atridad.dev/CTPR/cloudron-uptime-kuma-app:20210714-143642-23560f15f

                            I think this happenned because the docker repository was specified incorrectly when you did cloudron build. You can always cloudron build --set-repository again and it will ask you again for the repository name. The repo name should like girish/cloudron-uptime-kuma or something like that. The first part is your handle on docker hub (or equivalent). The second part is the repository name. In docker terminology, a repo is something that holds many images.

                            M Offline
                            M Offline
                            mazarian
                            wrote on last edited by
                            #27

                            @girish You are 100% right. I'm new to a lot of this. Thank you again for all of your help!

                            1 Reply Last reply
                            0
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes


                              • Login

                              • Don't have an account? Register

                              • Login or register to search.
                              • First post
                                Last post
                              0
                              • Categories
                              • Recent
                              • Tags
                              • Popular
                              • Bookmarks
                              • Search