certificate issues

[keg4343]

I have installed ubuntu 20.04.1 on a Dell laptop and followed the instructions provided to install the arrow-client. I set up the configuration file in the etc/arrow/ directory. I copied the certificate that was provided (ca.pem) and added it /usr/share/ca-certificates. When I run the application this is the error that appears in the syslog file.

Jun 14 14:11:44 angel-box arrow-client[8705]: [src/client.rs:86] connecting to remote Arrow Service arr-rs.angelcam.com:8900
Jun 14 14:11:44 angel-box arrow-client[8705]: [src/utils/mod.rs:127] unable to save current connection state (No such file or directory (os error 2))
Jun 14 14:11:44 angel-box arrow-client[8705]: [src/client.rs:122] unable to get TLS context: error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('ca.pem','r'), error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:76:, error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib:../crypto/x509/by_file.c:199:

If there is anything else you need let me know.

[operutka]

Hi @keg4343!

You can ignore the log message about saving the connection state. This isn't necessary for proper function of the Arrow client. The second message says that OpenSSL is not able to open your certificate. You need to specify the correct path to your certificate file. It can be either relative from the current working directory or absolute. You can also pass a whole folder. So in your case it'd be something like -c /usr/share/ca-certificates or -c /usr/share/ca-certificates/ca.pem.

[keg4343]

Hello operukta,

I made sure the file and folder was spelled correcetly and still recived the error. I also recived another error this time.

Jun 15 09:02:21 angel-box arrow-client[2494]: [src/client.rs:86] connecting to remote Arrow Service arr-rs.angelcam.com:8900
Jun 15 09:02:21 angel-box arrow-client[2494]: [src/client.rs:122] unable to get TLS context: error:02001002:system library:fopen:No such file or directory:../crypto/bio/bss_file.c:69:fopen('ca.pem','r'), error:2006D080:BIO routines:BIO_new_file:no such file:../crypto/bio/bss_file.c:76:, error:0B084002:x509 certificate routines:X509_load_cert_crl_file:system lib:../crypto/x509/by_file.c:199:
Jun 15 09:02:21 angel-box arrow-client[2494]: [src/client.rs:215] retrying in 59.982 seconds
Jun 15 09:02:21 angel-box arrow-client[15176]: [src/client.rs:114] connection rejected by the remote service arr-rs.angelcam.com:8900; is the client paired?
Jun 15 09:02:21 angel-box arrow-client[15176]: [src/client.rs:215] retrying in 10.000 seconds

To run the client I use
sudo -i
export PATH="$HOME/arrow-client/target/release:$PATH"
arrow-client arr-rs.angelcam.com:8900
-c /usr/share/ca-certificates/ca.pem

The file is called
ca.pem
and is located at
admin:///usr/share/ca-certificates

[operutka]

There are two process IDs in those logs: 2494 and 15176. You probably have there the old instance with incorrect cert. path still running. The new instance with process ID 15176 seems to be working correctly. The log message:

connection rejected by the remote service arr-rs.angelcam.com:8900; is the client paired?"

is OK. It just says that the client haven't been paired with an Angelcam user account and, therefore, it isn't allowed to connect to Angelcam cloud.

BTW you can try to start the client without any arguments to see the usage info.

[keg4343]

I restarted the computer and looked through the logs and noticed there was 8+ processes running so that was a lot of the issue. I ran it again and just the "connection rejected by the remote service arr-rs.angelcam.com:8900; is the client paired?" message, however when I try to pair the device to angelcam it never finds it.

also what the correct way to stop the process? I closed out of the terminal each time but that evidently did not stop the process.

[operutka]

however when I try to pair the device to angelcam it never finds it

How exactly are you trying to pair it?

also what the correct way to stop the process?

As with any other process being run in terminal - SIGINT (or CTR + C), SIGTERM, SIGKILL, ... Make your choice :)