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. Wallos
  3. Notifications not working?

Notifications not working?

Scheduled Pinned Locked Moved Solved Wallos
14 Posts 4 Posters 734 Views 3 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 joseph

    @odie said in Notifications not working?:

    but I don't receive notifications on my phone.

    Wanted to test this but are you referring to some mobile app here? I can't seem to find a mobile app for Wallos .

    O Offline
    O Offline
    odie
    wrote on last edited by
    #3

    @joseph said in Notifications not working?:

    @odie said in Notifications not working?:

    but I don't receive notifications on my phone.

    Wanted to test this but are you referring to some mobile app here? I can't seem to find a mobile app for Wallos .

    No, the Phone app I'm referring to is the ntfy app. My ntfy server works ok and sends notifications to my ntfy app on my phone, but Wallos can't seem to send notifications to my ntfy server (and consequently, I don't receive Wallos notifications sent through my nfty server to my phone's ntfy app)

    1 Reply Last reply
    0
    • J Offline
      J Offline
      joseph
      Staff
      wrote on last edited by
      #4

      @odie see https://github.com/ellite/Wallos/issues/524 and https://github.com/ellite/Wallos/issues/560 . Maybe something to do with how you have provide the tokens, I am not sure. I haven't read those issues in detail

      O 1 Reply Last reply
      0
      • J joseph

        @odie see https://github.com/ellite/Wallos/issues/524 and https://github.com/ellite/Wallos/issues/560 . Maybe something to do with how you have provide the tokens, I am not sure. I haven't read those issues in detail

        O Offline
        O Offline
        odie
        wrote on last edited by
        #5

        @joseph said in Notifications not working?:

        @odie see https://github.com/ellite/Wallos/issues/524 and https://github.com/ellite/Wallos/issues/560 . Maybe something to do with how you have provide the tokens, I am not sure. I haven't read those issues in detail

        Thanks for the link. The following header now sends test notifications from Wallos to ntfy ok (issue 524 as you linked above):

        {
          "Authorization": "Bearer tk_(removed)",
          "Title": "Subscription Notice",
          "Tags": "repeat"
        }
        

        However, Wallos still doesn't send subscription end notifications via email, and probably not via ntfy either (I assume, since the email test worked and my wallos doesn't send email notifications).

        1 Reply Last reply
        0
        • J Offline
          J Offline
          joseph
          Staff
          wrote on last edited by
          #6

          @odie I found another one - https://github.com/ellite/Wallos/issues/717

          It seems there is a cron job that sends these. /app/pkg/cron.sh sendnotifications . Does that throw anything for you in the web terminal? This notification on Cloudron runs only once a day btw - https://git.cloudron.io/packages/wallos-app/-/blob/master/CloudronManifest.json?ref_type=heads#L46

          O 1 Reply Last reply
          0
          • J joseph

            @odie I found another one - https://github.com/ellite/Wallos/issues/717

            It seems there is a cron job that sends these. /app/pkg/cron.sh sendnotifications . Does that throw anything for you in the web terminal? This notification on Cloudron runs only once a day btw - https://git.cloudron.io/packages/wallos-app/-/blob/master/CloudronManifest.json?ref_type=heads#L46

            O Offline
            O Offline
            odie
            wrote on last edited by odie
            #7

            @joseph said in Notifications not working?:

            /app/pkg/cron.sh sendnotifications

            When I run this command in terminal, it gives the following output:

            root@(redacted):/app/code# /app/pkg/cron.sh sendnotifications
            => Run cron job ''
            Could not open input file: /app/code/endpoints/cronjobs/.php
            

            Also, in my log files, I get these error messages every 2nd minute:

            Feb 26 11:02:02 => Run cron job ''
            Feb 26 11:02:02 Could not open input file: /app/code/endpoints/cronjobs/.php
            Feb 26 11:02:10 - - - [26/Feb/2025:10:02:10 +0000] "GET / HTTP/1.1" 302 - "-" "Mozilla (CloudronHealth)"
            Feb 26 11:02:14 => Run cron job ''
            Feb 26 11:02:14 Could not open input file: /app/code/endpoints/cronjobs/.php
            

            This behaviour is consistent on both my main app installation and my test app installation.

            However, if I go to the Wallos app, to the (username)->admin menu, there is an option to run Cronjobs from the GUI of the Wallos app. When I click the "send notifications" button, it sends notifications - both via email and via the ntfy service.

            J 1 Reply Last reply
            1
            • O odie

              @joseph said in Notifications not working?:

              /app/pkg/cron.sh sendnotifications

              When I run this command in terminal, it gives the following output:

              root@(redacted):/app/code# /app/pkg/cron.sh sendnotifications
              => Run cron job ''
              Could not open input file: /app/code/endpoints/cronjobs/.php
              

              Also, in my log files, I get these error messages every 2nd minute:

              Feb 26 11:02:02 => Run cron job ''
              Feb 26 11:02:02 Could not open input file: /app/code/endpoints/cronjobs/.php
              Feb 26 11:02:10 - - - [26/Feb/2025:10:02:10 +0000] "GET / HTTP/1.1" 302 - "-" "Mozilla (CloudronHealth)"
              Feb 26 11:02:14 => Run cron job ''
              Feb 26 11:02:14 Could not open input file: /app/code/endpoints/cronjobs/.php
              

              This behaviour is consistent on both my main app installation and my test app installation.

              However, if I go to the Wallos app, to the (username)->admin menu, there is an option to run Cronjobs from the GUI of the Wallos app. When I click the "send notifications" button, it sends notifications - both via email and via the ntfy service.

              J Offline
              J Offline
              joseph
              Staff
              wrote on last edited by
              #8

              @odie ha! the code is wrong and is not running cronjobs correctly .

              cc @girish

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

                I pushed a fix but didn't test it . Can you test?

                O 1 Reply Last reply
                1
                • girishG girish

                  I pushed a fix but didn't test it . Can you test?

                  O Offline
                  O Offline
                  odie
                  wrote on last edited by
                  #10

                  @girish said in Notifications not working?:

                  I pushed a fix but didn't test it . Can you test?

                  Apologies for the delay - work stuff. I updated now and tested. Notifications fires perfectly when issuing (from cli) the following command:

                  /app/pkg/cron.sh sendnotifications
                  

                  Output:

                  2025-02-26 17:36:25<br />
                  Next payment date: 2025-02-27<br />Current date: 2025-02-26<br />Difference: 1<br />Email Notifications sent<br />Ntfy Notifications sent<br /
                  

                  Also, Cloudron logs now show (every 2 mins):

                  Feb 26 18:38:03 => Run cron job 'sendverificationemails'
                  Feb 26 18:38:10 - - - [26/Feb/2025:17:38:10 +0000] "GET / HTTP/1.1" 302 - "-" "Mozilla (CloudronHealth)"
                  Feb 26 18:38:20 - - - [26/Feb/2025:17:38:20 +0000] "GET / HTTP/1.1" 302 - "-" "Mozilla (CloudronHealth)"
                  Feb 26 18:38:30 - - - [26/Feb/2025:17:38:30 +0000] "GET / HTTP/1.1" 302 - "-" "Mozilla (CloudronHealth)"
                  Feb 26 18:38:39 => Run cron job 'sendresetpasswordemails'
                  F
                  

                  I will post back if notifications fail to fire on subscriptions (when the service is running "by itself")

                  Another idea: Maybe these instructions could be added to the Cloudron docs. It wasn't easy to find out how to set custom headers when using a Cloudron hosted nfty-instance (ie with access restrictions and access tokens: https://forum.cloudron.io/post/102335

                  J 1 Reply Last reply
                  2
                  • O odie

                    @girish said in Notifications not working?:

                    I pushed a fix but didn't test it . Can you test?

                    Apologies for the delay - work stuff. I updated now and tested. Notifications fires perfectly when issuing (from cli) the following command:

                    /app/pkg/cron.sh sendnotifications
                    

                    Output:

                    2025-02-26 17:36:25<br />
                    Next payment date: 2025-02-27<br />Current date: 2025-02-26<br />Difference: 1<br />Email Notifications sent<br />Ntfy Notifications sent<br /
                    

                    Also, Cloudron logs now show (every 2 mins):

                    Feb 26 18:38:03 => Run cron job 'sendverificationemails'
                    Feb 26 18:38:10 - - - [26/Feb/2025:17:38:10 +0000] "GET / HTTP/1.1" 302 - "-" "Mozilla (CloudronHealth)"
                    Feb 26 18:38:20 - - - [26/Feb/2025:17:38:20 +0000] "GET / HTTP/1.1" 302 - "-" "Mozilla (CloudronHealth)"
                    Feb 26 18:38:30 - - - [26/Feb/2025:17:38:30 +0000] "GET / HTTP/1.1" 302 - "-" "Mozilla (CloudronHealth)"
                    Feb 26 18:38:39 => Run cron job 'sendresetpasswordemails'
                    F
                    

                    I will post back if notifications fail to fire on subscriptions (when the service is running "by itself")

                    Another idea: Maybe these instructions could be added to the Cloudron docs. It wasn't easy to find out how to set custom headers when using a Cloudron hosted nfty-instance (ie with access restrictions and access tokens: https://forum.cloudron.io/post/102335

                    J Offline
                    J Offline
                    joseph
                    Staff
                    wrote on last edited by
                    #11

                    @odie said in Notifications not working?:

                    Another idea: Maybe these instructions could be added to the Cloudron docs

                    We try to avoid putting app specific docs into Cloudron docs. These get out of date since they are not actively monitored. Best to suggest the docs upstream where it belongs.

                    1 Reply Last reply
                    1
                    • L Offline
                      L Offline
                      lucidfox
                      wrote on last edited by
                      #12

                      I'm facing the same issue that @odie described. Test Ntfy notifications are working properly, but not any of the actual subscription notifications.

                      When I try the /app/pkg/cron.sh sendnotifications command I only get this response -

                      2025-04-02 16:06:56<br />

                      I can see this repeatedely in the logs as well -
                      Run cron job 'sendresetpasswordemails'
                      Run cron job 'sendverificationemails'

                      Has the issue been resolved for anyone else or am I missing something?

                      Also, in case it matters, none of the subscription notifications I've setup are from the admin user account.

                      O 1 Reply Last reply
                      0
                      • L lucidfox

                        I'm facing the same issue that @odie described. Test Ntfy notifications are working properly, but not any of the actual subscription notifications.

                        When I try the /app/pkg/cron.sh sendnotifications command I only get this response -

                        2025-04-02 16:06:56<br />

                        I can see this repeatedely in the logs as well -
                        Run cron job 'sendresetpasswordemails'
                        Run cron job 'sendverificationemails'

                        Has the issue been resolved for anyone else or am I missing something?

                        Also, in case it matters, none of the subscription notifications I've setup are from the admin user account.

                        O Offline
                        O Offline
                        odie
                        wrote on last edited by
                        #13

                        @lucidfox Did you follow the procedure described in this post above? Post 102335 in this thread

                        Wallos needs these custom headers to fire its notifications (refer to Wallos github support issue 524 in that post).

                        L 1 Reply Last reply
                        1
                        • O odie

                          @lucidfox Did you follow the procedure described in this post above? Post 102335 in this thread

                          Wallos needs these custom headers to fire its notifications (refer to Wallos github support issue 524 in that post).

                          L Offline
                          L Offline
                          lucidfox
                          wrote on last edited by
                          #14

                          Thanks a lot @odie, I totally missed the custom headers post for some reason 🙄. The notifications are firing as expected now.

                          1 Reply Last reply
                          2
                          • J joseph marked this topic as a question on
                          • J joseph 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