The CURL docs <https://curl.haxx.se/libcurl/c/libcurl-errors.html> cites:
CURLE_PEER_FAILED_VERIFICATION (51) The remote server's SSL certificate or SSH md5 fingerprint was deemed not OK. Please read SSL certificates gotchas <https://github.com/openwisp/ansible-openwisp2#ssl-certificate-gotchas> section in the ansible-openwisp2 README. Is it clear? General suggestions: every time you get an error on the log, look for the most significant part on google. Federico On Fri, Feb 3, 2017 at 4:56 PM Federico Capoano <[email protected]> wrote: Google "curl exit code 51" On Fri, Feb 3, 2017 at 4:52 PM SKapoor <[email protected]> wrote: Federico, Why I am getting these logs that AP is not able to register? logread -f Fri Feb 3 15:49:34 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/controller/openwisp/actions.lua:12: attempt to call global 'post' (a nil value) Fri Feb 3 15:49:34 2017 daemon.err uhttpd[1175]: stack traceback: Fri Feb 3 15:49:34 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/controller/openwisp/actions.lua:12: in function 'v' Fri Feb 3 15:49:34 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/dispatcher.lua:536: in function 'createtree' Fri Feb 3 15:49:34 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/dispatcher.lua:201: in function 'dispatch' Fri Feb 3 15:49:34 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/dispatcher.lua:168: in function </usr/lib/lua/luci/dispatcher.lua:167> Fri Feb 3 15:49:39 2017 daemon.err openwisp: Failed to connect to controller during registration: curl exit code 51 Fri Feb 3 15:49:55 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/controller/openwisp/actions.lua:12: attempt to call global 'post' (a nil value) Fri Feb 3 15:49:55 2017 daemon.err uhttpd[1175]: stack traceback: Fri Feb 3 15:49:55 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/controller/openwisp/actions.lua:12: in function 'v' Fri Feb 3 15:49:55 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/dispatcher.lua:536: in function 'createtree' Fri Feb 3 15:49:55 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/dispatcher.lua:201: in function 'dispatch' Fri Feb 3 15:49:55 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/dispatcher.lua:168: in function </usr/lib/lua/luci/dispatcher.lua:167> Fri Feb 3 15:50:01 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/controller/openwisp/actions.lua:12: attempt to call global 'post' (a nil value) Fri Feb 3 15:50:01 2017 daemon.err uhttpd[1175]: stack traceback: Fri Feb 3 15:50:01 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/controller/openwisp/actions.lua:12: in function 'v' Fri Feb 3 15:50:01 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/dispatcher.lua:536: in function 'createtree' Fri Feb 3 15:50:01 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/dispatcher.lua:201: in function 'dispatch' Fri Feb 3 15:50:01 2017 daemon.err uhttpd[1175]: /usr/lib/lua/luci/dispatcher.lua:168: in function </usr/lib/lua/luci/dispatcher.lua:167> Fri Feb 3 15:50:10 2017 daemon.info openwisp: Registering device... Fri Feb 3 15:50:16 2017 daemon.err openwisp: Failed to connect to controller during registration: curl exit code 51 Fri Feb 3 15:50:46 2017 daemon.info openwisp: Registering device... Fri Feb 3 15:50:51 2017 daemon.err openwisp: Failed to connect to controller during registration: curl exit code 51 Fri Feb 3 15:51:21 2017 daemon.info openwisp: Registering device... On Friday, 3 February 2017 20:38:37 UTC+5:30, SKapoor wrote: Thanks for helping out, I have already started on firmware side procedures. Will update you the progress soon. One question I have wrt group ap firmware upgrade!! Is that supported with openwisp2? Thanks in advance, On Fri, 3 Feb 2017 at 7:50 PM, Federico Capoano <[email protected]> wrote: Well, it could be you were trying the wrong user/password combination or any other information to connect via SSH was not correct. Anyway, the important thing is that you made it. To compile an OpenWRT image with openwisp-config, I suggest you to follow the instructions in "Compiling a custom OpenWRT/LEDE image" <https://github.com/openwisp/openwisp-config#compiling-a-custom-openwrtlede-image> On Fri, Feb 3, 2017 at 1:34 PM SKapoor <[email protected]> wrote: Hi Federico I did it locally on my vmware machine. I am able to bring up openWISP-2 manager. What I did different from README is instead of ansible-playbook -i hosts playbook.yml -u ubunthu -k --ask-sudo-pass I used this ansible-playbook -i hosts playbook.yml -c local -k --ask-sudo-pass and it worked for me, curious to know why -u ubunthu didnt work for me? Step-2 will try to bring up openwisp-2 firmware. thanks so much federico :) regards On Thursday, 2 February 2017 15:05:54 UTC+5:30, Federico Capoano wrote: Find out how to login via ssh into your server. Bytheway, are you using a server or are you trying this on a desktop pc? If you are using a server, you may ask to your hosting support or a friend that knows a bit of system administration. If you are using your own pc you can run the playbook locally, consult the ansible documentation and look on google for "running ansible playbook locally". For any question regarding ubuntu, their support channels are very active. Il gio 2 feb 2017, 03:55 sonia kapoor <[email protected]> ha scritto: I tried doing ssh but no luck.. In the wisp-2 readme : Create a new file hosts on your local machine with the following contents: [openwisp2]openwisp2.mydomain.com Substitute openwisp2.mydomain.com with your hostname (ip addresses are allowed as well). This tells whatever IP I m getting for local machine I have to put in host file replacing openwisp2.myfomain.com So , if I m not wrong ping will always work but whn I try doing ssh it is not working... I m using ubunthu-14.04 ..Is there any limitations on the Ansible version to be used ? What is going wrong ? Regards On Wed, 1 Feb 2017 at 9:37 PM, Federico Capoano <[email protected]> wrote: It seems ansible cannot log in via SSH into your machine. Can you ping 192.168.6.244? Eg: ping 192.168.6.244 Can you log in via ssh with the user admin? Eg: ssh [email protected] Are you sure the password is correct? The first thing you have to get sorted is to be able to SSH into 192.168.6.244 via ansible. Federico On Wednesday, February 1, 2017 at 4:31:15 PM UTC+1, SKapoor wrote: Federico, Installing openWISP-2 finally facing this issue while loading manager-2 sudo ansible-playbook -i hosts playbook.yml -u admin -k --ask-sudo-pass SSH password: SUDO password[defaults to SSH password]: PLAY [openwisp2] *************************************************************** TASK [setup] ******************************************************************* fatal: [192.168.6.244]: UNREACHABLE! => {"changed": false, "msg": "Authentication failure.", "unreachable": true} to retry, use: --limit @/home/zbtdell02/openwisp2-ansible-playbook/playbook.retry PLAY RECAP ********************************************************************* 192.168.6.244 : ok=0 changed=0 unreachable=1 failed=0 Need your help Regards -- You received this message because you are subscribed to a topic in the Google Groups "OpenWISP" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/openwisp/siqqAoIxnK4/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- 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]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups "OpenWISP" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/openwisp/siqqAoIxnK4/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- 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]. For more options, visit https://groups.google.com/d/optout. -- 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]. For more options, visit https://groups.google.com/d/optout.
