Skip to content

Releases: Project516/qbittorrent-warp

qBittorrent-WARP 5.2.4.2

Choose a tag to compare

@Project516 Project516 released this 12 Oct 17:18
4980baf

Prebuilt qBittorrent-WARP 5.2.4.2, based on upstream qBittorrent 5.2.4.

Which build do I want?

  • qBittorrent-WARP-5.2.4.2-x86_64.AppImage.zip - desktop build with the full graphical interface, for
    64-bit Linux PCs (x86_64).
  • qBittorrent-WARP-5.2.4.2-aarch64.AppImage.zip - headless build (qbittorrent-nox) for 64-bit ARM
    boards such as the Raspberry Pi. It has no graphical interface and is
    used through its Web UI in a browser. The arm64 asset is attached a few
    minutes after the release first appears.

Install

Download the zip for your machine, extract the AppImage, make it
executable and run it:

unzip qBittorrent-WARP-5.2.4.2-x86_64.AppImage.zip
chmod +x qBittorrent-WARP-5.2.4.2-x86_64.AppImage
./qBittorrent-WARP-5.2.4.2-x86_64.AppImage

It is self-contained and portable: a profile folder holding all
configuration, data and the WARP engine is created next to the AppImage
file. Nothing is written to system locations. Verify the download against
SHA256SUMS if you wish.

Headless / Raspberry Pi

The aarch64 build serves the Web UI on port 8080. Install libfuse2
(sudo apt install libfuse2) or run with --appimage-extract-and-run,
and pass --confirm-legal-notice the first time so it does not wait for
input. On first start it prints a randomly generated Web UI password to
the log; read it there, browse to http://<pi-ip>:8080 and change it.
See warp/README.md
for running it as a service.

Bundled helper licenses and pinned versions are listed in
warp/THIRD-PARTY-NOTICES.md.

qBittorrent-WARP 5.2.4.1

Choose a tag to compare

@Project516 Project516 released this 01 Oct 01:19
44e1689

Prebuilt qBittorrent-WARP 5.2.4.1, based on upstream qBittorrent 5.2.4.

Which build do I want?

  • qBittorrent-WARP-5.2.4.1-x86_64.AppImage.zip - desktop build with the full graphical interface, for
    64-bit Linux PCs (x86_64).
  • qBittorrent-WARP-5.2.4.1-aarch64.AppImage.zip - headless build (qbittorrent-nox) for 64-bit ARM
    boards such as the Raspberry Pi. It has no graphical interface and is
    used through its Web UI in a browser. The arm64 asset is attached a few
    minutes after the release first appears.

Install

Download the zip for your machine, extract the AppImage, make it
executable and run it:

unzip qBittorrent-WARP-5.2.4.1-x86_64.AppImage.zip
chmod +x qBittorrent-WARP-5.2.4.1-x86_64.AppImage
./qBittorrent-WARP-5.2.4.1-x86_64.AppImage

It is self-contained and portable: a profile folder holding all
configuration, data and the WARP engine is created next to the AppImage
file. Nothing is written to system locations. Verify the download against
SHA256SUMS if you wish.

Headless / Raspberry Pi

The aarch64 build serves the Web UI on port 8080. Install libfuse2
(sudo apt install libfuse2) or run with --appimage-extract-and-run,
and pass --confirm-legal-notice the first time so it does not wait for
input. On first start it prints a randomly generated Web UI password to
the log; read it there, browse to http://<pi-ip>:8080 and change it.
See warp/README.md
for running it as a service.

Bundled helper licenses and pinned versions are listed in
warp/THIRD-PARTY-NOTICES.md.

qBittorrent-WARP 5.2.3.5

Choose a tag to compare

@github-actions github-actions released this 21 Sep 19:41
2f73672

Prebuilt qBittorrent-WARP 5.2.3.5, based on upstream qBittorrent 5.2.3.

Which build do I want?

  • qBittorrent-WARP-5.2.3.5-x86_64.AppImage.zip - desktop build with the full graphical interface, for
    64-bit Linux PCs (x86_64).
  • qBittorrent-WARP-5.2.3.5-aarch64.AppImage.zip - headless build (qbittorrent-nox) for 64-bit ARM
    boards such as the Raspberry Pi. It has no graphical interface and is
    used through its Web UI in a browser. The arm64 asset is attached a few
    minutes after the release first appears.

Install

Download the zip for your machine, extract the AppImage, make it
executable and run it:

unzip qBittorrent-WARP-5.2.3.5-x86_64.AppImage.zip
chmod +x qBittorrent-WARP-5.2.3.5-x86_64.AppImage
./qBittorrent-WARP-5.2.3.5-x86_64.AppImage

It is self-contained and portable: a profile folder holding all
configuration, data and the WARP engine is created next to the AppImage
file. Nothing is written to system locations. Verify the download against
SHA256SUMS if you wish.

Headless / Raspberry Pi

The aarch64 build serves the Web UI on port 8080. Install libfuse2
(sudo apt install libfuse2) or run with --appimage-extract-and-run,
and pass --confirm-legal-notice the first time so it does not wait for
input. On first start it prints a randomly generated Web UI password to
the log; read it there, browse to http://<pi-ip>:8080 and change it.
See warp/README.md
for running it as a service.

Bundled helper licenses and pinned versions are listed in
warp/THIRD-PARTY-NOTICES.md.

qBittorrent-WARP 5.2.3.4

Choose a tag to compare

@github-actions github-actions released this 27 Jul 13:54
bb375cc

Prebuilt qBittorrent-WARP 5.2.3.4, based on upstream qBittorrent 5.2.3.

Which build do I want?

  • qBittorrent-WARP-5.2.3.4-x86_64.AppImage.zip - desktop build with the full graphical interface, for
    64-bit Linux PCs (x86_64).
  • qBittorrent-WARP-5.2.3.4-aarch64.AppImage.zip - headless build (qbittorrent-nox) for 64-bit ARM
    boards such as the Raspberry Pi. It has no graphical interface and is
    used through its Web UI in a browser. The arm64 asset is attached a few
    minutes after the release first appears.

Install

Download the zip for your machine, extract the AppImage, make it
executable and run it:

unzip qBittorrent-WARP-5.2.3.4-x86_64.AppImage.zip
chmod +x qBittorrent-WARP-5.2.3.4-x86_64.AppImage
./qBittorrent-WARP-5.2.3.4-x86_64.AppImage

It is self-contained and portable: a profile folder holding all
configuration, data and the WARP engine is created next to the AppImage
file. Nothing is written to system locations. Verify the download against
SHA256SUMS if you wish.

Headless / Raspberry Pi

The aarch64 build serves the Web UI on port 8080. Install libfuse2
(sudo apt install libfuse2) or run with --appimage-extract-and-run,
and pass --confirm-legal-notice the first time so it does not wait for
input. On first start it prints a randomly generated Web UI password to
the log; read it there, browse to http://<pi-ip>:8080 and change it.
See warp/README.md
for running it as a service.

Bundled helper licenses and pinned versions are listed in
warp/THIRD-PARTY-NOTICES.md.

qBittorrent-WARP 5.2.3.3

Choose a tag to compare

@github-actions github-actions released this 20 Jul 18:16
442dbec

Prebuilt qBittorrent-WARP 5.2.3.3, based on upstream qBittorrent 5.2.3.

Which build do I want?

  • qBittorrent-WARP-5.2.3.3-x86_64.AppImage.zip - desktop build with the full graphical interface, for
    64-bit Linux PCs (x86_64).
  • qBittorrent-WARP-5.2.3.3-aarch64.AppImage.zip - headless build (qbittorrent-nox) for 64-bit ARM
    boards such as the Raspberry Pi. It has no graphical interface and is
    used through its Web UI in a browser. The arm64 asset is attached a few
    minutes after the release first appears.

Install

Download the zip for your machine, extract the AppImage, make it
executable and run it:

unzip qBittorrent-WARP-5.2.3.3-x86_64.AppImage.zip
chmod +x qBittorrent-WARP-5.2.3.3-x86_64.AppImage
./qBittorrent-WARP-5.2.3.3-x86_64.AppImage

It is self-contained and portable: a profile folder holding all
configuration, data and the WARP engine is created next to the AppImage
file. Nothing is written to system locations. Verify the download against
SHA256SUMS if you wish.

Headless / Raspberry Pi

The aarch64 build serves the Web UI on port 8080. Install libfuse2
(sudo apt install libfuse2) or run with --appimage-extract-and-run,
and pass --confirm-legal-notice the first time so it does not wait for
input. On first start it prints a randomly generated Web UI password to
the log; read it there, browse to http://<pi-ip>:8080 and change it.
See warp/README.md
for running it as a service.

Bundled helper licenses and pinned versions are listed in
warp/THIRD-PARTY-NOTICES.md.

qBittorrent-WARP 5.2.3.2

Choose a tag to compare

@github-actions github-actions released this 20 Jul 18:05
98009b5

Prebuilt qBittorrent-WARP 5.2.3.2, based on upstream qBittorrent 5.2.3.

Which build do I want?

  • qBittorrent-WARP-5.2.3.2-x86_64.AppImage.zip - desktop build with the full graphical interface, for
    64-bit Linux PCs (x86_64).
  • qBittorrent-WARP-5.2.3.2-aarch64.AppImage.zip - headless build (qbittorrent-nox) for 64-bit ARM
    boards such as the Raspberry Pi. It has no graphical interface and is
    used through its Web UI in a browser. The arm64 asset is attached a few
    minutes after the release first appears.

Install

Download the zip for your machine, extract the AppImage, make it
executable and run it:

unzip qBittorrent-WARP-5.2.3.2-x86_64.AppImage.zip
chmod +x qBittorrent-WARP-5.2.3.2-x86_64.AppImage
./qBittorrent-WARP-5.2.3.2-x86_64.AppImage

It is self-contained and portable: a profile folder holding all
configuration, data and the WARP engine is created next to the AppImage
file. Nothing is written to system locations. Verify the download against
SHA256SUMS if you wish.

Headless / Raspberry Pi

The aarch64 build serves the Web UI on port 8080. Install libfuse2
(sudo apt install libfuse2) or run with --appimage-extract-and-run,
and pass --confirm-legal-notice the first time so it does not wait for
input. On first start it prints a randomly generated Web UI password to
the log; read it there, browse to http://<pi-ip>:8080 and change it.
See warp/README.md
for running it as a service.

Bundled helper licenses and pinned versions are listed in
warp/THIRD-PARTY-NOTICES.md.

qBittorrent-WARP 5.2.3.1

Choose a tag to compare

@github-actions github-actions released this 08 Jul 16:06
2e23530

Prebuilt qBittorrent-WARP 5.2.3.1, based on upstream qBittorrent 5.2.3.

Which build do I want?

  • qBittorrent-WARP-5.2.3.1-x86_64.AppImage.zip - desktop build with the full graphical interface, for
    64-bit Linux PCs (x86_64).
  • qBittorrent-WARP-5.2.3.1-aarch64.AppImage.zip - headless build (qbittorrent-nox) for 64-bit ARM
    boards such as the Raspberry Pi. It has no graphical interface and is
    used through its Web UI in a browser. The arm64 asset is attached a few
    minutes after the release first appears.

Install

Download the zip for your machine, extract the AppImage, make it
executable and run it:

unzip qBittorrent-WARP-5.2.3.1-x86_64.AppImage.zip
chmod +x qBittorrent-WARP-5.2.3.1-x86_64.AppImage
./qBittorrent-WARP-5.2.3.1-x86_64.AppImage

It is self-contained and portable: a profile folder holding all
configuration, data and the WARP engine is created next to the AppImage
file. Nothing is written to system locations. Verify the download against
SHA256SUMS if you wish.

Headless / Raspberry Pi

The aarch64 build serves the Web UI on port 8080. Install libfuse2
(sudo apt install libfuse2) or run with --appimage-extract-and-run,
and pass --confirm-legal-notice the first time so it does not wait for
input. On first start it prints a randomly generated Web UI password to
the log; read it there, browse to http://<pi-ip>:8080 and change it.
See warp/README.md
for running it as a service.

Bundled helper licenses and pinned versions are listed in
warp/THIRD-PARTY-NOTICES.md.

qBittorrent-WARP 5.2.2.5

Choose a tag to compare

@github-actions github-actions released this 24 Jun 01:22

Prebuilt qBittorrent-WARP 5.2.2.5, based on upstream qBittorrent 5.2.2.

Which build do I want?

  • qBittorrent-WARP-5.2.2.5-x86_64.AppImage.zip - desktop build with the full graphical interface, for
    64-bit Linux PCs (x86_64).
  • qBittorrent-WARP-5.2.2.5-aarch64.AppImage.zip - headless build (qbittorrent-nox) for 64-bit ARM
    boards such as the Raspberry Pi. It has no graphical interface and is
    used through its Web UI in a browser. The arm64 asset is attached a few
    minutes after the release first appears.

Install

Download the zip for your machine, extract the AppImage, make it
executable and run it:

unzip qBittorrent-WARP-5.2.2.5-x86_64.AppImage.zip
chmod +x qBittorrent-WARP-5.2.2.5-x86_64.AppImage
./qBittorrent-WARP-5.2.2.5-x86_64.AppImage

It is self-contained and portable: a profile folder holding all
configuration, data and the WARP engine is created next to the AppImage
file. Nothing is written to system locations. Verify the download against
SHA256SUMS if you wish.

Headless / Raspberry Pi

The aarch64 build serves the Web UI on port 8080. Install libfuse2
(sudo apt install libfuse2) or run with --appimage-extract-and-run,
and pass --confirm-legal-notice the first time so it does not wait for
input. On first start it prints a randomly generated Web UI password to
the log; read it there, browse to http://<pi-ip>:8080 and change it.
See warp/README.md
for running it as a service.

Bundled helper licenses and pinned versions are listed in
warp/THIRD-PARTY-NOTICES.md.

qBittorrent-WARP 5.2.2.1

Choose a tag to compare

@github-actions github-actions released this 16 Jun 21:40
75eb9cc

Prebuilt qBittorrent-WARP 5.2.2.1, based on upstream qBittorrent 5.2.2.

Install

Download the zip, extract the AppImage, make it executable and run it:

unzip qBittorrent-WARP-5.2.2.1-x86_64.AppImage.zip
chmod +x qBittorrent-WARP-5.2.2.1-x86_64.AppImage
./qBittorrent-WARP-5.2.2.1-x86_64.AppImage

It is self-contained and portable: a profile folder holding all
configuration, data and the WARP engine is created next to the AppImage
file. Nothing is written to system locations. Verify the download against
SHA256SUMS if you wish.

Bundled helper licenses and pinned versions are listed in
warp/THIRD-PARTY-NOTICES.md.

qBittorrent-WARP 5.2.1.11

Choose a tag to compare

@github-actions github-actions released this 16 Jun 21:23

Prebuilt qBittorrent-WARP 5.2.1.11, based on upstream qBittorrent 5.2.1.

Install

Download the zip, extract the AppImage, make it executable and run it:

unzip qBittorrent-WARP-5.2.1.11-x86_64.AppImage.zip
chmod +x qBittorrent-WARP-5.2.1.11-x86_64.AppImage
./qBittorrent-WARP-5.2.1.11-x86_64.AppImage

It is self-contained and portable: a profile folder holding all
configuration, data and the WARP engine is created next to the AppImage
file. Nothing is written to system locations. Verify the download against
SHA256SUMS if you wish.

Bundled helper licenses and pinned versions are listed in
warp/THIRD-PARTY-NOTICES.md.