Device Registration Troubleshooting

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_http" | 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

   ​

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.