Is there anything else below the output you showed? It doesn’t look complete.
Did you install anything else from Remote.It on this device such as the Remote.It CLI, Remote.It Desktop or connectd?
Can you run the following and provide the output?
sh -c "$(curl -sL https://downloads.remote.it/remoteit/distributiontest.sh)"
And just to get some general information about the system:
The output doesn’t show that you have an incompatible device.
Can you please confirm if you had tried to install any other Remote.It product before such as the Remote.It CLI or Desktop? These are incompatible with the device package. If you have we will likely need to start over.
You can run the following command line to verify that there is not CLI installed:
sudo remoteit status
If you get any other output other than something that indicates it doesn’t know remoteit, then you did install the Desktop or CLI and you shouldn’t need to install the device package as well. You can just register the device to accept connections.
Hello ,
noticed Miguel’s issue and realised I’m going through the same problem ! I tried installing both the Ubuntu and Rasberry Pi version using the command from the dashboard, but the device never comes alive. I also created a 3rd Ubuntu instance and installed the CLI version and went through the steps ( logging in, registerding device, adding service etc ) but when looking at the device, it is still in ‘connecting’ state ( it also shows offline on the dashboard ).
If you need to only support inbound connections, then you only need the device package and not the CLI.
If you have installed both you should uninstall both and start over since they are not compatible.
To uninstall the device package you can use the package manager on the device to do so, below is the apt version:
sudo apt purge remoteit
If you also installed connectd you should remove that too
sudo apt purge connectd
Then finally to uninstall the CLI,
sudo remoteit uninstall
Once you have uninstalled then you should choose the right product and install that.
If you still are having issues with the device coming online, do you have a super restrictive firewall that blocks outbound traffic?