Shadowrocket Linux Installation: DEB, RPM, or AppImage? apt and dnf Commands

1. Check your distribution, architecture, and download source

Debian and Ubuntu users should generally choose DEB; Fedora users should generally choose RPM and use dnf. If you prefer not to register the app in the system package database, consider AppImage. Package format and CPU architecture are separate requirements: a matching file extension does not mean the program inside supports your CPU.

Go to the Linux section on the download page for all platforms and choose from the packages and architectures actually listed there. The Linux version is free. The iPhone / iPad version costs $2.99 as a one-time App Store purchase; the Mac (Apple silicon and Intel), Windows, and Android versions are also free. Check the App Store page for iPhone / iPad system requirements.

1. Identify your distribution

   Open a terminal and run cat /etc/os-release to check ID, ID_LIKE, and PRETTY_NAME. Don’t identify your distribution by desktop appearance alone: the same desktop can run on different package systems.

2. Check your architecture

   Run uname -m. The output x86_64 indicates the common 64-bit Intel / AMD architecture; aarch64 indicates 64-bit ARM. Choose only a file that the download page explicitly lists for your architecture.

3. Choose a package

   Open the Linux section of the download page and select a format supported by your distribution. Using RPM does not mean you should always use dnf. For other RPM-based distributions, follow their package manager’s instructions rather than copying Fedora commands.

4. Locate the downloaded file

   Use your browser’s download history to open the folder containing the file and confirm the download is complete. The commands below assume the file is in $HOME/Downloads. If your system uses another download folder, replace the directory in the commands with the actual path.

cat /etc/os-release
uname -m

2. Debian / Ubuntu: Install a DEB with apt

To install a local DEB with apt install, pass the file as a path. Don’t omit the leading ./ from a relative path, or apt may interpret the input as a package name. apt can fetch dependencies from enabled repositories, but older distributions may not have every library the program requires.

Run the following commands in Bash. They list DEB files in your Downloads folder so you can select the actual file by number, without relying on a fixed filename. The folder may contain installers for other apps, so make sure you select the Shadowrocket file you just downloaded from this site. If no matching file is found, the script won’t run the installation.

(
  cd "$HOME/Downloads" || exit 1
  shopt -s nullglob
  packages=(./*.deb)
  if ((${#packages[@]} == 0)); then
    printf '%s\n' 'No DEB files in this directory. Check the download location.'
    exit 1
  fi
  PS3='Enter the number for the Shadowrocket DEB file: '
  select pkg in "${packages[@]}"; do
    if [[ -n "$pkg" ]]; then
      sudo apt install "$pkg"
      break
    fi
    printf '%s\n' 'Enter a valid number from the list.'
  done
)

• Review the transaction summary first: Check which packages will be installed, upgraded, or removed. If many unexpected packages are set to be removed, enter n to cancel and check distribution compatibility before proceeding.
• If dependency downloads fail: Check that your system repositories are available. If needed, run sudo apt update to refresh the package index, then retry with the same file. Refreshing the index does not make an incompatible package compatible.
• If dependencies cannot be satisfied: Note the exact dependency names and requirements, then check whether the download page supports your distribution. Don’t add repositories for another distribution or force the installation past dependency checks.
• After installation succeeds: Search for Shadowrocket in your desktop’s applications menu. A successful installation command and a program that launches successfully are separate checks; verify both.

3. Fedora: Install an RPM with dnf

On Fedora, dnf can install a local RPM and check dependencies and conflicts in the same transaction. Don’t assume an RPM built for another distribution will work just because it has the same file extension. Library names, dependency requirements, and desktop integration can all differ.

(
  cd "$HOME/Downloads" || exit 1
  shopt -s nullglob
  packages=(./*.rpm)
  if ((${#packages[@]} == 0)); then
    printf '%s\n' 'No RPM files in this directory. Check the download location.'
    exit 1
  fi
  PS3='Enter the number for the Shadowrocket RPM file: '
  select pkg in "${packages[@]}"; do
    if [[ -n "$pkg" ]]; then
      sudo dnf install "$pkg"
      break
    fi
    printf '%s\n' 'Enter a valid number from the list.'
  done
)

If you see an architecture mismatch, dependency conflict, or package verification error, stop the transaction and save the full message. Don’t add options to skip verification or force file replacement. If the terminal says the same package is already installed, check its current status first; repeatedly running the install command won’t fix connection problems.

4. AppImage: Add execute permission and launch

An AppImage typically runs as a single executable file, without the package installation transaction required by DEB or RPM. That doesn’t mean it has no system dependencies. CPU architecture, the graphical environment, runtime libraries, and mount options can all affect startup. Move the file to a location where you plan to keep it so it won’t be lost when you clear your Downloads folder.

These Bash commands add execute permission only to the selected file for the current user, then launch it as that user. Don’t recursively change permissions for your entire Downloads folder, and don’t use sudo to launch the graphical app.

(
  cd "$HOME/Downloads" || exit 1
  shopt -s nullglob
  packages=(./*.AppImage)
  if ((${#packages[@]} == 0)); then
    printf '%s\n' 'No AppImage files in this directory. Check the download location.'
    exit 1
  fi
  PS3='Enter the number for the Shadowrocket AppImage file: '
  select pkg in "${packages[@]}"; do
    if [[ -n "$pkg" ]]; then
      chmod u+x -- "$pkg" && "$pkg"
      break
    fi
    printf '%s\n' 'Enter a valid number from the list.'
  done
)

• If you see Permission denied: Check the file’s execute permission and the filesystem it’s on. Even after running chmod u+x, a filesystem mounted with the noexec option may still block execution. Move the file to a personal directory that allows execution and try again.
• If you see an error mentioning libfuse.so.2: The FUSE 2 compatibility library is likely missing. On Debian / Ubuntu, run apt-cache policy libfuse2 libfuse2t64 to see which packages are available for your distribution, then follow its guidance. Don’t blindly copy a library name from another system.
• If you see Exec format error: First compare the output of uname -m with the architecture listed on the download page. Adding execute permission won’t fix an architecture mismatch.
• If double-clicking opens no window: Run the file from a terminal to see the error. If you launched it from a remote terminal without a graphical session, check it from the local desktop session instead of repeatedly changing permissions.

5. First launch: Check startup and connectivity separately

If the window opens, the app has passed the startup check. Establishing a connection also depends on your existing configuration, network, name resolution, and selected policy. This site does not provide, sell, or recommend nodes or subscriptions. A connection timeout by itself does not indicate an installation problem.

1. Launch as a regular user: Open Shadowrocket from the applications menu or launch the AppImage. If the app requests necessary system permissions, read each prompt carefully. Don’t launch the entire client as root preemptively.
2. Have your own connection details ready: Check the address, port, protocol, and authentication details provided by your service provider. Treat subscription links as credentials and don’t post them in public support requests.
3. Check where settings are: Review existing connection entries in Home, the configuration you plan to use in Config, and relevant options in Settings. Available options vary by platform; refer to what your current interface shows.
4. Check the routing mode: If the interface offers Global Routing, first check whether it is set to Config, Proxy, or Direct. Direct is not a suitable way to determine whether a proxy connection is working.
5. Test one thing at a time: Start with the same destination and change only one variable at a time. Note whether the connection times out, whether name resolution fails, and whether only certain destinations are affected. Don’t change the protocol, rules, and DNS all at once.

To test rule behavior, use this minimal example in Config to understand the order. example.com is a documentation domain, not a server address; PROXY must match a policy available in your current configuration. Don’t replace an existing complete configuration with this snippet.

[Rule]
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,PROXY

Rules are evaluated from top to bottom; the policy on the first matching line is applied. Put FINAL last to handle requests that don’t match earlier rules. The example uses 192.168.0.0/16 to demonstrate direct access to a local network; it does not cover all private addresses. no-resolve means the app won’t actively resolve a domain for that IP rule. It is not a switch that fixes every DNS problem.

6. Global Routing: Choose a mode for your test

During installation troubleshooting, routing mode helps narrow down the cause; no single mode is always better. These comparisons cover Shadowrocket’s own settings only. The traffic it can handle still depends on platform permissions and the current network connection method; they do not imply unconditional handling of all system traffic.

7. Common issues: Troubleshoot by stage

Before asking for help, identify whether the issue occurs during download, package installation, app startup, or connection. Include the full error message, distribution name, and CPU architecture; these are more useful than simply saying “it won’t open.” Before sharing logs, remove authentication details, subscription links, and personal addresses.