Direct answer
Linux users should choose the package that matches their distribution workflow: AppImage for portable use, deb for Debian/Ubuntu families, rpm for Fedora/RHEL families, and manual binaries only when they understand permissions.
What to check first
Installation support checks are usually environmental: the wrong CPU build, an interrupted download, an operating system prompt, or a network that blocks executable packages.
- Confirm the package type matches your operating system and chip.
- Use a trusted source and avoid renamed or incomplete files.
- Check browser, antivirus and network filtering if downloads stop repeatedly.
- After installation, launch the client once before importing a profile.
Recommended handling
Do not repeatedly run partial or questionable installers. Verify the source, choose the correct package, install once, then continue with profile import and basic connectivity testing.
Practical notes
- A prompt is not automatically false; verify the package before bypassing it.
- Change one setting at a time so the result is attributable.
- Use logs and timestamps when asking for provider or community support.