Connect troubleshooting guide for Linux


Below are some common recommended troubleshooting steps to try if you're experiencing issues with Connect on Linux.

If you still cannot resolve the issue after considering these troubleshooting measures, please contact Aspera Support.


1. Check SELinux

When enabled SELinux can sometimes cause problems for Connect usage. To check if SELinux is enabled, run the following command:

# sestatus

If the status is disabled or enabled on permissive mode, SELinux is not blocking Connect, and you can continue on to the next step.

If the status is enabled on enforcing mode, disabling SELinux should fix the issue.

If you require SELinux to be enabled on your system, your browser will not be able to start Connect for you, but if you start Connect manually it will work as expected. To start Connect manually from the terminal run the following command:

# ~/.aspera/connect/bin/asperaconnect

2. Check AppArmor

On Ubuntu systems, AppArmor is an alternative security system to SELinux which can also cause problems for Connect.

To check the status of AppArmor on your system, run the following command:

# sudo aa-status

You may need to modify your policies if they are enabled on Connect. If you want to disable AppArmor on your system, you can set it to "complain" mode so that security details are logged but programs not blocked:

# sudo aa-complain

3. Check iptables

If you have iptables rules configured, they may be blocking connectivity between your system and your browser.

For Connect version 3.6.2 and later, inbound connections to TCP port 43003-43013 must be allowed. For earlier versions of Connect, inbound connections to TCP port 33003-33013 must be allowed.

To check your iptables rules, run the following:

# iptables -L

4. Check your kernel

OVH Linux kernels have been seen to be incompatible with Connect. If you have an OVH kernel you may need to reinstall your server with a stock kernel.

Powered by Zendesk