Upswift
HomePricingDashboardRegister Now
Search…
Upswift.io
Getting started
Connecting a device
Connecting devices at scale
Add Upswift to Yocto image
PLATFORM
Features
Settings
API
REST API
Guides
How-to guides
Environment variables
Running Commands as User
Upswift Architecture
Platform design
Upswift Agent
Security
Non-Linux Agent
Agent API
Troubleshooting
Device registration
Display issue - "0.0"
Micro update
Remote control
FAQ
Frequent questions
Billing
Deprecated
Send Logs
Powered By GitBook
Device registration

Installing Upswift 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. Upswift 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. 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. 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, reboot the device, and check 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. 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. 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. 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 dashboard.upswift.io certificate

Add --no-check-certificate after the wget inside the installation command:
1
wget --no-check-certificate -O - "https://dashboard.upswift.io/install_upswift"...
Copied!

CentOS/Red Hat - SELinux permission issue

Upswift 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:
Add Upswift to the device se-policy
  1. 1.
    Run the next Bash command as a root user:
wget https://upswift1.s3.eu-central-1.amazonaws.com/general/agents/sepolicy/upswift.pp | semodule -i upswift.pp
2. Reboot the device.
OR
Disable SELinux
  1. 1.
    vi /etc/selinux/config (edit SELinux config file).
  2. 2.
    Change the SELINUX parameter from enforcing to disabled (disable SELinux system).
  3. 3.
    reboot (reboot the device).
Non-Linux Agent - Previous
Agent API
Next - Troubleshooting
Display issue - "0.0"
Last modified 9mo ago
Copy link
Contents
Installing Upswift agent returns "http/1.1 400 bad request"
In case of automatic device registration after reboot
Cannot verify dashboard.upswift.io certificate
CentOS/Red Hat - SELinux permission issue