search

facebookarchive / CommunityCellularManager

Tool for deploying, managing and controlling your Community Cellular Networks
Other
87 stars 36 forks source link

CCM client not registering with cloud instances #29

Closed mferland closed 7 years ago

mferland commented 7 years ago

I've followed both cloud and client READMEs and so far everything seems to be running OK. The only issue which remains is that I cannot get the client to send status updates to the cloud.

Looking at the /var/log/endagad logs I see things like:

Unable to verify client cert against CA bundle

Similarly in /var/log/endaga:

[CRITICAL] endaga: system_utilities.py:260:verify_cert: Unable to verify client cert against CA bundle:#012/etc/openvpn/endaga-client.crt

What did I do wrong?

Any help would be appreciated!

kheimerl commented 7 years ago

Did you update the bundle to the one you generated? The one in the package is for our cloud. To check, find the bundle in your client build directory and diff it with the one in /etc/endaga/

On Wed, Feb 22, 2017 at 1:23 PM, Marc Ferland notifications@github.com wrote:

I've followed both cloud and client READMEs and so far everything seems to be running OK. The only issue which remains is that I cannot get the client to send status updates to the cloud.

Looking at the /var/log/endagad logs I see things like:

Unable to verify client cert against CA bundle

Similarly in /var/log/endaga:

[CRITICAL] endaga: system_utilities.py:260:verify_cert: Unable to verify client cert against CA bundle:#012/etc/openvpn/endaga-client.crt

What did I do wrong?

Any help would be appreciated!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/facebookincubator/CommunityCellularManager/issues/29, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_rnyas0OIZ2CAVuuOg2bYJIudJssxQks5rfKdBgaJpZM4MJNJY .

9muir commented 7 years ago

The error indicates that the root CA that was used to sign the client certificate is not the same as the root cert installed in the client. You need to ensure that etage-bundle.crt in the certifier VM is the same as etage-bundle in the client (in /etc/openvpn).

mferland commented 7 years ago

Ah! I did forgot to update the bundle. Thanks for pointing that out.