Hi.
Try to use "option verify_ssl '0'"
2018-04-18 15:41 GMT+05:00 Nam Lê :
> Hi all,
>
> I can't connect between openwisp agent and controller.
>
> Log agent show code 77 .
> Wed Apr 18 10:35:49 2018 daemon.err openwisp: Failed to connect to
> controller while getting
In that case the best solution would be to put the self created CA in the
system's trusted CA so the SSL verification would pass.
I haven't tried this yet but when I will do I'll report how to do this.
Disabling SSL verification in a production environment is highly
discouraged in all cases.
Disabling the SSL verification may work, but it's not a good practice for
production environments because it's insecure so it should be used only as
a temporary solution. (c)
May by they use self-signed cert in local network. In this case there is
not big risk.
2018-04-18 19:01 GMT+05:00 Federico
Hi all,
I can't connect between openwisp agent and controller.
Log agent show code 77 .
Wed Apr 18 10:35:49 2018 daemon.err openwisp: Failed to connect to
controller while getting checksum: curl exit code 77
I installed openwisp-config-no-sll on agent and this is
/etc/config/openwisp
config
This line: You may need to add '10.85.18.14' to ALLOWED_HOSTS.
Is a good clue.
Could you paste the contents of your playbook.yml please?
Federico
On Wed, Apr 18, 2018 at 7:38 AM Артур Скок wrote:
> Hello.
> Django's "problem" that you need restart not only nginx but
Arthur, Federico! thanks, it worked right now! after i messed arrown with
the line ALLOWED_HOSTS, i included not only the name of the host but the
ip, i registered the name pointing to the ip in /etc/hosts but i dont know
what happened but ok, it worked now: after including the ip of the host in
Hello.
Django's "problem" that you need restart not only nginx but also uwsgi
which intermediate between nginx and python.
*cd /opt/openwisp2source ./env/bin/activateps aux | grep -i uwsgi | awk
'{print $2}' | xargs sudo kill -9*
*#if UWSGI will not start automatically (check with
>From https://curl.haxx.se/libcurl/c/libcurl-errors.html
CURLE_SSL_CACERT_BADFILE (77)
Problem with reading the SSL CA cert (path? access rights?)
Disabling the SSL verification may work, but it's not a good practice for
production environments because it's insecure so it should be used only as
Glad to know we have a security expert :-)
I just wanted to point that out for the record, so that we avoid that any
people reading this post in the future will think disabling SSL
verification is a valid solution also for production systems, unfortunately
I've seen people doing that a lot..
We've implemented travis-ci build [1] to test ansible-openwisp2 on the
following Linux Distribution:
- CentOS 7
- Ubuntu 16.04
- Debian 8
- Debian 9
Travis-ci build test will be triggered on every push.
[1] https://travis-ci.org/openwisp/ansible-openwisp2
Regards,
--
Marco Giuntini
Thanks a lot for this awesome and much needed contribution Marco!
Fed
Il mer 18 apr 2018, 16:24 Marco Giuntini ha
scritto:
> We've implemented travis-ci build [1] to test ansible-openwisp2 on the
> following Linux Distribution:
>
>- CentOS 7
>- Ubuntu 16.04
>
In case of OpenWRT there is enough to put CA/server cert at
"/etc/ssl/certs". It'll work on the fly.
I think that Nam uses test environment. Imho, if you try any solution then
you don't need troubles with 3rd-party soft.
I know about security issues... cause it is my bread and butter =)
среда,
Hi!
try this:
opkg update
opkg install curl
opkg install
http://downloads.lede-project.org/snapshots/packages/mips_24kc/packages/openwisp-config-openssl_0.4.5-2_mips_24kc.ipk
I'm on Reboot (17.01.4, r3560-79f57e422d).
Let me know!
Il giorno mar 17 apr 2018 alle ore 21:58 amine boubaker <
That's great news to hear Rafael!
Have you edited the settings.py manually? If you did, that's not the best
long term solution because if you run the ansible playbook again to upgrade
openwisp you will lose your manual changes.
If that's the case post please let me know and we'll try to help
14 matches
Mail list logo