Clash Party installation and configuration guide for major distributions (AppImage recommended)
Quick start
Download AppImage file
chmod +x to grant execution rights
Run directly, import config and connect
System requirements
Modern 64-bit Linux distribution
x86_64 (amd64)
At least 1GB RAM
At least 200MB available space
Step 1: Download and Installation
AppImage (Recommended)
Run Directly without Installation
AppImage advantages: Download and run, no dependencies, compatible with most distributions.
- Download Linux (AppImage) file
-
Grant execution permission:
chmod +x ClashParty-*.AppImage -
Run the program:
./ClashParty-*.AppImage
DEB/RPM Packages
Ubuntu / Debian (DEB)
sudo apt install ./clashparty_*.deb
Fedora / RHEL / openSUSE (RPM)
sudo dnf install clashparty-*.rpm
# Or
sudo zypper install clashparty-*.rpm
Arch Linux
Install via AUR (search for keywords like clash party, mihomo or meta GUI):
Note: Community packages may use third-party maintenance scripts. We recommend prioritizing the official AppImage for consistency and security.
Step 2: Import Subscription
Subscription Link/Clipboard
- Launch Clash Party
- Open the Profiles / Subscription page
- Click "Add Subscription", select import from URL or Clipboard
- Paste the subscription link and save, wait for the node list to load
Step 3: Select Node and Connect
- Latency Test: Perform a latency test in the node list.
- Select Node: Choose a node with lower latency.
- Connect: Click the connect button; success is indicated when the status shows "Connected".
Optional Configuration
Desktop Proxy Settings (Manual)
- GNOME: Settings > Network > Network Proxy > Configure HTTP/HTTPS/SOCKS
- KDE: System Settings > Network Settings > Proxy > Enable and fill in ports
Command Line Proxy (As Needed)
Add to ~/.bashrc or ~/.zshrc:
export http_proxy="http://127.0.0.1:8080"
export https_proxy="http://127.0.0.1:8080"
export all_proxy="socks5://127.0.0.1:1080"
export no_proxy="localhost,127.0.0.1,::1"Common Issues
Cannot Start?
Ensure the AppImage has execution permissions; run in terminal to check error output.
Cannot Connect?
Switch nodes, check subscription status or firewall rules.
TUN Support?
For system-level proxy, ensure the kernel has the tun module loaded (lsmod | grep tun).
Next Steps
- Continue reading Routing Rules
- Check FAQ for more help