Hey Daniel, correct, there's a part missing, since this is still a work-in-progress, but I forgot to tell you.
You have to create a template (flag it as default and assign it to your devices): the content of the template is here: https://gist.github.com/nemesisdesign/cb005dc80a75536cf8537105c3038a71 In the future we should make this an openwrt package like openwisp-config, but now I'm doing it this way in order to move faster and the other contributors are just following along. For now, we are iterating and improving the "netjson-monitoring" script in this repo: https://github.com/openwisp/lua-monitoring/ We update it often to add new features (eg: https://github.com/openwisp/lua-monitoring/pull/17). Regarding the monitoring system and notifications module, we have a lot of improvements that will be soon merged in the master branch (the playbook will have to be updated too), now available in the dev branches of openwisp-monitoring <https://github.com/openwisp/openwisp-monitoring> and openwisp-notifications <https://github.com/openwisp/openwisp-notifications/>, so I suggest to stay tuned for updates, I don't really suggest you to try these yet, since I'm doing it and I'm finding a some rough edges that we're working to fix, it may be too frustrating for you to try that now. Let me know if you can make it work! Federico On Sun, Aug 2, 2020 at 4:31 AM Daniel <[email protected]> wrote: > > Hi Federico, > > Here is another question. > > After running the playbook successfully, I cannot see any chart or device > status. > > I can only see that there is a check method ping. And the health status is > always unknown even I have successfully changed some configuration and > applied to my AP. > > Is there something about settings.py or other things missing in the > playbook? Or is there something to be added in the openwisp-config of AP? > > Sorry for asking so many questions so far. > > Best regards, > Daniel > Daniel 在 2020年8月1日 星期六下午9:38:41 [UTC+8] 的信中寫道： > >> It works now! Thank you so much! >> >> Best regards, >> Daniel >> >> Federico Capoano <[email protected]>於 2020年7月31日 週五，下午11:35寫道： >> >>> The playbook looks good. >>> The problem seems to be in a line that has been changed recently in a >>> data migration, which is causing that issue. >>> It should be fixed >>> <https://github.com/openwisp/openwisp-monitoring/commit/7c363175684ace42edbcdb9a06a309e382d74011>, >>> can you run the playbook again, ensuring the latest master of >>> openwisp-monitoring <https://github.com/openwisp/openwisp-monitoring> >>> is installed and let me know please? >>> >>> Thanks >>> Federico >>> >>> On Fri, Jul 31, 2020 at 5:15 AM Daniel <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> Here are still also several error messages. >>>> >>>> [image: screenshot.png] >>>> >>>> And the attached file is my playbook. >>>> >>>> Thanks, >>>> Daniel >>>> [email protected] 在 2020年7月31日 星期五上午7:03:25 [UTC+8] 的信中寫道： >>>> >>>>> Try to remove openwisp_monitoring.notifications from INSTALLED_APPS >>>>> but ensure openwisp_notifications is present in INSTALLED_APPS and also >>>>> installed as a dependency as Hardik pointed out. >>>>> >>>>> If it doesn't work, share the playbook with us please (removing >>>>> sensitive info) so we can have better insight. >>>>> >>>>> F. >>>>> >>>>> On Thu, Jul 30, 2020 at 5:58 PM Hardik Jain <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Daniel, >>>>>> I think openwisp-notifications needs to be installed. >>>>>> https://github.com/openwisp/openwisp-notifications/tarball/master >>>>>> >>>>>> It is now a permanent dependency of openwisp-monitoring. At the time >>>>>> of sharing the above playbook, that wasn't the case. Hence, missed out I >>>>>> think. >>>>>> >>>>>> Regards >>>>>> Hardik >>>>>> >>>>>> On Thu, 30 Jul 2020, 20:41 Daniel, <[email protected]> wrote: >>>>>> >>>>>>> Hi Federico, >>>>>>> >>>>>>> Sorry for bothering you again. >>>>>>> >>>>>>> I have tried to use the development version of the other openwisp >>>>>>> modules, but there is still an error message when migration. >>>>>>> >>>>>>> Here is the error message. >>>>>>> >>>>>>> [image: screenshot.png] >>>>>>> >>>>>>> Thanks! >>>>>>> Daniel >>>>>>> [email protected] 在 2020年7月30日 星期四上午12:57:20 [UTC+8] 的信中寫道： >>>>>>> >>>>>>>> That question is not related to OpenWISP but to iptables, I suggest >>>>>>>> you to ask on superuser/stackexchange >>>>>>>> <https://superuser.com/questions/tagged/iptables>. >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Jul 29, 2020 at 10:13 AM Daniel <[email protected]> wrote: >>>>>>>> >>>>>>>>> Hi Ajay and Federico, >>>>>>>>> >>>>>>>>> Thank you for yours answer. I will try it. >>>>>>>>> >>>>>>>>> Here is another question I want to ask. Though it may be more >>>>>>>>> related to nginx and certification problems. >>>>>>>>> >>>>>>>>> Now I deploy my openwisp with a private ip, said 192.168.1.X, and >>>>>>>>> I want to connect to the website from a public ip, said 140.X.X.X >>>>>>>>> >>>>>>>>> I use a laptop based on ubuntu as the gateway with public(also >>>>>>>>> 140.X.X.X) and private ip simultaneously, and use iptables to set NAT >>>>>>>>> on it. >>>>>>>>> >>>>>>>>> I set a PREROUTING rule with port 5000 to 192.168.1.X:443. And set >>>>>>>>> a POSTROUTING rule for all traffic. >>>>>>>>> >>>>>>>>> But when I type https://140.X.X.X:5000 in my broswer, it shows >>>>>>>>> 404 not found, and it shows TLSv1.2 Alert 73, Level Fatal, >>>>>>>>> Description: >>>>>>>>> Certificate Unknown in wireshark. >>>>>>>>> >>>>>>>>> I want to know how to solve it. Sorry for that this question is >>>>>>>>> not related to openwisp and I am not familiar with nginx and >>>>>>>>> certification. >>>>>>>>> >>>>>>>>> Thanks! >>>>>>>>> Daniel >>>>>>>>> [email protected] 在 2020年7月29日 星期三下午10:05:38 [UTC+8] 的信中寫道： >>>>>>>>> >>>>>>>>>> Disregard my earlier mail, on closer inspection, that doesn't >>>>>>>>>> seem to be the reason. >>>>>>>>>> >>>>>>>>>> I haven't used openwisp-notifications with ansible yet, but it >>>>>>>>>> seems a development version of a dependency is used in >>>>>>>>>> openwisp-notification which is causing this. >>>>>>>>>> >>>>>>>>>> I can't say with certainty without testing, but most likely >>>>>>>>>> adding the following in your playbook should work: >>>>>>>>>> openwisp2_controller_pip: >>>>>>>>>> https://github.com/openwisp/openwisp-controller/tarball/master >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Ajay >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>> You received this message because you are subscribed to the Google >>>>>>>>> Groups "OpenWISP" group. >>>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>>> send an email to [email protected]. >>>>>>>>> >>>>>>>> To view this discussion on the web, visit >>>>>>>>> https://groups.google.com/d/msgid/openwisp/555df5ec-1ecc-47d3-9d65-b97d8c1616c7n%40googlegroups.com >>>>>>>>> <https://groups.google.com/d/msgid/openwisp/555df5ec-1ecc-47d3-9d65-b97d8c1616c7n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>> . >>>>>>>>> >>>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "OpenWISP" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected]. >>>>>>> To view this discussion on the web, visit >>>>>>> https://groups.google.com/d/msgid/openwisp/433cff40-67d3-4355-bb1c-4d8f05561fdbn%40googlegroups.com >>>>>>> <https://groups.google.com/d/msgid/openwisp/433cff40-67d3-4355-bb1c-4d8f05561fdbn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "OpenWISP" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to [email protected]. >>>>>> >>>>> To view this discussion on the web, visit >>>>>> https://groups.google.com/d/msgid/openwisp/CAEnke%3DtJDuSPsosu_bOpD5KS32ejipn_D2kx%2ByF9q2E2QEmVRA%40mail.gmail.com >>>>>> <https://groups.google.com/d/msgid/openwisp/CAEnke%3DtJDuSPsosu_bOpD5KS32ejipn_D2kx%2ByF9q2E2QEmVRA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "OpenWISP" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web, visit >>>> https://groups.google.com/d/msgid/openwisp/9b8e832e-a64e-4f51-bc2c-e00671618ffdn%40googlegroups.com >>>> <https://groups.google.com/d/msgid/openwisp/9b8e832e-a64e-4f51-bc2c-e00671618ffdn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "OpenWISP" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> >> To view this discussion on the web, visit >>> https://groups.google.com/d/msgid/openwisp/CAERYH6V%2ByB9zS5s_R398KEDeOpK6%2BMWErWc8KysVLpg9_SV2aA%40mail.gmail.com >>> <https://groups.google.com/d/msgid/openwisp/CAERYH6V%2ByB9zS5s_R398KEDeOpK6%2BMWErWc8KysVLpg9_SV2aA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/openwisp/c1b5f64d-686c-431a-9e36-b3d613134a40n%40googlegroups.com > <https://groups.google.com/d/msgid/openwisp/c1b5f64d-686c-431a-9e36-b3d613134a40n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/CAERYH6UVnBTaKOy3seBC-kYiNoSaP%2BmTAYAJDwcwGG4sfVpJfg%40mail.gmail.com.
