Device registration

HTTP installation
If your device doesn't support HTTPS, and it can only work with HTTP traffic, you can download the agent using the next HTTP command:
Bash
su -c 'wget -O - "http://downloads.connect.jfrog.io/install_connect" | sh -s <USER_TOKEN> <PROJECT_NAME>'
Please note that you must replace the <USER_TOKEN> with your private user token and <PROJECT_NAME> with your project name.
Installing Connect agent returns "http/1.1 400 bad request"
Your wget can't execute HTTPS requests. This can happen when you have an old wget binary or old Busybox binary. Connect installation requires an updated wget or Busybox (version compiled in 2015 and above).
To fix this you can try to run the installation command with "http" instead of "https" or upgrade your wget/busybox.
1.To upgrade Busybox, please ​download the binary and replace with the old binary or contact us at [email protected] for technical installation support.
2.To upgrade wget, please run the commands below:
apt -y update
apt install -y wget
​
In case of automatic device registration after reboot
DEPRECATED
There might be situations when some of the MAC addresses are changing after a reboot. You can find out if this is the situation with your devices by checking your MAC addresses, rebooting the device, and checking them again.
Please turn on the option to "Register devices by duplicating image" in the settings category, under your project. Next, enter the number of the persistent MAC addresses your devices have. This will adopt the new devices registration algorithm for your account to work with the type of your devices.
Examples
1.You have 5 devices, all of them have 1 MAC address each. In that case, you will enter the number 1 at the persistent MAC addresses input.
2.You have 5 devices, all of them have 3 MAC addresses each. If so, you have to check how many of those MAC addresses are persistent across reboots. Let's say, 2 of them are persistent (meaning they are not changing when you reboot the device) and 1 of them changes every reboot. In that case, you will enter the number 2 at the persistent MAC addresses input.
3.You have 5 devices, some of them have 3 MAC addresses and others have 2 MAC addresses. In that case, you have to check how many of those MAC addresses are persistent across reboots for both types of devices. Let's say that 1 MAC address is persistent on the devices that have 2 MAC addresses in total, and 2 MAC addresses are persistent on the devices that have 3 MAC addresses in total, then you will enter the lower number of them at the persistent MAC addresses input, which is 1 in this case.
Cannot verify connect.jfrog.io certificate
Add --no-check-certificate after the wget inside the installation command:
wget --no-check-certificate -O - "https://connect.jfrog.io/install_connect"...
CentOS/Red Hat - SELinux permission issue
Connect agent can’t work properly with SELinux enabled, to fix the issue, please add the following se-policy to your Linux device or disable SELinux:
Disable SELinux
1.vi /etc/selinux/config (edit SELinux config file).
2.Change the SELINUX parameter from enforcing to disabled (disable SELinux system).
3.reboot (reboot the device).
OR permit Connect's Agent in SELINUX
Run:
1.semanage fcontext -a -t bin_t /etc/connect/service/ConnectAgent
2.restorecon -v /etc/connect/service/ConnectAgent
3.service connect restart
*Remote control / remote access will still won't work until ssh and sshd binaries will be permitted as well.
​

SETTINGS - Previous

Security

Next - Troubleshooting

Display issue - "0.0"

Last modified 1mo ago

Copy link

Outline

HTTP installation

Installing Connect agent returns "http/1.1 400 bad request"

In case of automatic device registration after reboot

Cannot verify connect.jfrog.io certificate

CentOS/Red Hat - SELinux permission issue