This article is provided to demonstrate several things that can “go wrong” with installing remote.it, and how to deal with them.
The OS image used for this exercise is the Debian 10 V3.0.11 for Tinkerboard S, as found here: Tinker Board
#1 Update ca-certificates
If at any time you see an error similar to:
curl: (60) SSL certificate problem:
then update your ca-certificates which are used by remoteit to make secure calls to our API servers.
sudo -i
update-ca-certificates --fresh
exit
#2 Install the Device Package
At the moment, the 1-line installer and “streamlined” installers do not properly detect the armhf Debian OS. So you’ll need to download the file directly from our downloads page at https://docs.remote.it/software/device-package/supported-platforms .
wget https://downloads.remote.it/remoteit/v4.14.1/remoteit-4.14.1.armhf.rpi.deb
sudo apt update
sudo apt install ./remoteit-4.14.1.armhf.rpi.deb
When the installation completes you will be shown a claim code.
If you DON’T see a claim code it could mean:
- your ca-certificates need updating.
- you’ve already configured the device
If you need to start over, run
sudo dpkg --purge remoteit
3. Configure a remote.it Device and Services
You’ll need to have the Desktop application installed, or log in at https://beta.remote.it. The procedure and UI are the same for both in this scenario.
Follow these instructions (starting with “Enter the Claim Code”) to register your Device and add Services to it.
4. Remove the dependency on rc.local
If your Services are getting registered (that is, they show up in your account) but they never come online, the startup unit files that control the daemons used for connections may need to be edited. In Debian, this is accomplished by making a copy of the supplied files and placing them in /etc/systemd/system. When the OS boots, these will be read in preference over the files installed by the remoteit package. Placing these files into /etc prevents them from being overwritten in the event you re-install or update the remoteit Device Package.
Run the following commands:
sudo cp /usr/lib/systemd/system/remoteit@.service /etc/systemd/system
sudo cp /usr/lib/systemd/system/connectd.service /etc/systemd/system
sudo cp /usr/lib/systemd/system/schannel.service /etc/systemd/system
Next, edit each of the 3 files you copied (in /etc/systemd/system) to remove the dependency on rc.local.
e.g.
Before:
After:
Now, if you reboot, your remoteit Services should start up.
remote.it thinks this system is a Raspberry Pi. This issue is cosmetic and has no impact on the functionality.