Install Shadowrocket on Linux: Choose deb, rpm, or AppImage; apt/dnf commands and execute permissions

Choose a package by distro: deb for Debian/Ubuntu, rpm for Fedora/RHEL, or AppImage for other distros. Includes local apt and dnf install commands and how to make an AppImage executable.

At a glance

To install Shadowrocket on a Linux desktop, first check your distribution and system architecture, then choose a package format. Install deb and rpm packages with your system package manager. Save AppImage to a user-writable location, make it executable, and launch it directly. This guide also explains how to tell a wrong path from unmet dependencies or an execution failure.

01 · Check your distribution and architecture

  1. Identify your distribution

    Open a terminal and run cat /etc/os-release. Check ID to identify your distribution. If it’s unfamiliar, use ID_LIKE to see which distro family it belongs to. ID_LIKE describes relationships between distributions; it does not guarantee package compatibility.

  2. Check your architecture

    Run uname -m to check the kernel architecture. The common value x86_64 corresponds to amd64 in deb packages, while aarch64 corresponds to arm64. On Debian or Ubuntu, also run dpkg --print-architecture to check the architecture used by the package manager. Download only a package actually offered on the download page that matches your system.

  3. Choose a package format

    For Debian and Ubuntu, choose .deb; for Fedora and RHEL, choose .rpm. For other distributions, first check whether an .AppImage is available for your architecture and runtime environment. Don’t install a package built for another distro family just because your system has a particular package manager.

  4. Get the package

    Go to Download and select the matching format in the Linux section. Once downloaded, locate the file in your file manager and note its full path and extension. The commands below use the local path to the downloaded file, not a download URL.

02 · Install a local package with apt or dnf

The commands below apply to systems with apt or dnf. Run only the set that matches your downloaded package format. When prompted for a path in the terminal, enter the full path starting with /, without adding quotes. "$pkg" in the command preserves spaces in the path.

Debian / Ubuntu: Install a deb package

printf 'Enter the full path to the deb file: '
> 
printf 'Enter the full path to the deb file: '
IFS= read -r pkg
if [ -f "$pkg" ]; then
  sudo apt install "$pkg"
else
  printf '%s\n' 'File not found. Check the full path.'
fi

Fedora / RHEL: Install an rpm package

printf 'Enter the full path to the rpm file: '
IFS= read -r pkg
if [ -f "$pkg" ]; then
  sudo dnf install "$pkg"
else
  printf '%s\n' 'File not found. Check the full path.'
fi

apt install arguments

Local file input
A .deb path starting with /
Dependency source
Enabled apt repositories
View package information
dpkg-deb -f "$pkg" Package Architecture Depends

If you enter only a filename without a path, apt may treat it as the name of a package in a repository.

dnf install arguments

Local file input
An .rpm path starting with /
Dependency source
Currently enabled DNF repositories
View package information
rpm -qpi "$pkg"

Review the transaction summary before installing. If it lists unexpected removals, cancel and check for dependency conflicts.

Installing a local package doesn’t mean installing offline. If dependencies are missing, the package manager may still connect to enabled repositories. If it reports a missing dependency or says no package provides it, note the package name in the error and check your distribution, architecture, and repository status. Don’t add repositories for another distribution just to install a local package.

03 · Make an AppImage executable

AppImage doesn’t use apt install or dnf install. Move the downloaded file to a user directory where you plan to keep it, then run it as a regular user. chmod u+x is a restricted form of chmod +x that adds execute permission for the file owner only.

printf 'Enter the full path to the AppImage file: '
IFS= read -r app
if [ -f "$app" ]; then
  chmod u+x -- "$app" && "$app"
else
  printf '%s\n' 'File not found. Check the full path.'
fi

04 · Check Global Routing after installation

Opening the app confirms only that it starts; it doesn’t mean a proxy service is available. Configure it with your own service details first. If Global Routing is available under Home in your current interface, choose a mode based on what you want to test. Change one setting at a time and use the same reachable test URL to compare results, so you don’t mistake a rule difference for an installation problem.

Config

Recommended

Use the rules in the current Config to determine how each request is routed. Rules are matched from top to bottom. If FINAL is configured, requests that don’t match an earlier rule use its specified policy; they don’t automatically connect directly.

Best for: Applying established routing rules after confirming the service is available.

Direct

Connect requests handled by the client directly. Use this to check whether the same destination is reachable without a proxy. This doesn’t confirm that your configured proxy service is working.

Best for: Establishing a direct-connection baseline to distinguish an unreachable destination from a proxy-path issue.

Proxy

Route requests handled by the client through the selected proxy service, without applying Config rules. If Proxy works but Config doesn’t, return to Config and check the rule and policy matching that destination.

Best for: Briefly testing the proxy route, then restoring the previous setting.

05 · Common Linux installation questions

The download finished. Why does the terminal say the file can’t be found?

When you download the same file more than once, the filename may include a number. Check the actual filename and folder in your file manager, then enter the full path again. If the path contains spaces, enter it exactly as prompted above. Don’t use the file:// address shown by the file manager as a path.

AppImage reports “Exec format error.” Is this still a permissions issue?

Run file -- "$app" to check the file type and architecture. If the output identifies HTML or plain text, download the package again from the download page. If the executable architecture doesn’t match your system, choose a compatible package. Adding execute permission can’t change a file’s format or architecture.

The deb or rpm installed, but the app doesn’t appear in the application menu. What now?

First, use the package information command to find the actual package name. Then run dpkg -l or rpm -q with that name to confirm it’s installed. If it is, use dpkg -L or rpm -ql with the package name to list its installed files. Check for a .desktop launcher entry and note its directory. Missing from the menu doesn’t necessarily mean the installation failed.

Can I just replace the existing file when updating?

For deb and rpm, use a new package with the same architecture and update it with the original package manager. Review the transaction summary. For AppImage, close the running app first, make the new file executable, and test it. If a custom launcher points to the old path, update it to the new one. Keeping the old file isn’t the same as backing up your settings, so save any configuration you want to keep separately before updating.

Download Shadowrocket

Two ways to get Shadowrocket: The iPhone / iPad version is available on the App Store for a one-time payment of $2.99; check the App Store listing for system requirements. Versions for Mac (Apple silicon and Intel), Windows, Android, and Linux are free, with installers distributed from this site.

Download Shadowrocket