ERR_CONNECTION_REFUSED

[100Stress]

Good afternoon everyone,

I have qBittorrent installed on trueNas Core, and suddenly I can't ccess web interface.

Is there any way to fix this error?

 

[mindfields]

got the same problem here..
I had an alert that there's update available, when the process was done I got message that there was no update and I get what you get since then

 

[lilomaster]

Same deal, here. I uninstalled QBittorrent and installed it again, I haven't setup SSL yet, but it seems that when SSL is active it causes that error. But if I add a torrent file and it starts checking or downloading, it stops receiving connections from the WebUI, that's an strange behavior I have experienced.

 

[lilomaster]

I started experiencing another problem. I could reinstall QBittorrent, and as soon as it starts downloading data it losses connection through the Web UI. Reviewing the log, it says that qbittorrent closed the connection in whatever IP address and port it is using because the IP address is already in use and cannot be bound. I tried binding interface instead of IP address, but I got the same behavior. I start thinking it is a bug in the latest update. I stopped using qbittorrent in the meantime and started using Transmission, instead. I definitely love the file management and torrent categorization features QBittorrent has, but I can live without them for a few days until a solution is found. Hopefully, a new version of the plugin with the latest qbittorrent 4.4.3 will be released within a few days. Until then, I will use Transmission.

 

[GordeyGordeich]

Hi all!
I have the same problem after updating to 4.4.2_1
After returning to version 4.4.2, the problem remained.
The WEB UI has been pinged but is not available. Torrents are not downloading.
In the next step, the plugin was removed and reinstalled.
Problem was solved, the WEB UI has appeared.
…But after a few moments, the problem returned again.

 

[mindfields]

I used a snapshot of the jail before updating it and it fixed the problem.
I will wait for the next update to see if it works

 

[lilomaster]

Hi all!
I have the same problem after updating to 4.4.2_1
After returning to version 4.4.2, the problem remained.
The WEB UI has been pinged but is not available. Torrents are not downloading.
In the next step, the plugin was removed and reinstalled.
Problem was solved, the WEB UI has appeared.
…But after a few moments, the problem returned again.

Exactly the same behavior. I couldn't use a snapshot to downgrade, because, for some strange reason, in TrueNAS 13 the snapshot dates are not properly displayed, and it is quite confusing to figure out which is the right snapshot to use.

 

[Volts]

I think libtorrent-rasterbar 1.2.14_1,1 is the breakage.

See the PRs linked here.

FreshPorts -- net-p2p/libtorrent-rasterbar: C++ library implementing a BitTorrent client

libtorrent is an open source C++ library implementing the BitTorrent protocol, along with most popular extensions, making it suitable for real world deployment. It is configurable to be able to fit both servers and embedded devices. The main goals of libtorrent are to be efficient and easy to...

www.freshports.org

The quickest solution might be to go back from the latest to quarterly pkg repo, remove and reinstall libtorrent-rasterbar and qbittorrent.

 

[mindfields]

Exactly the same behavior. I couldn't use a snapshot to downgrade, because, for some strange reason, in TrueNAS 13 the snapshot dates are not properly displayed, and it is quite confusing to figure out which is the right snapshot to use.

Using snapshot was quite easy.
I noticed the dates were not in order but I scrolled until I found it.

 

[lilomaster]

I think libtorrent-rasterbar 1.2.14_1,1 is the breakage.

See the PRs linked here.

FreshPorts -- net-p2p/libtorrent-rasterbar: C++ library implementing a BitTorrent client

libtorrent is an open source C++ library implementing the BitTorrent protocol, along with most popular extensions, making it suitable for real world deployment. It is configurable to be able to fit both servers and embedded devices. The main goals of libtorrent are to be efficient and easy to...

www.freshports.org

The quickest solution might be to go back from the latest to quarterly pkg repo, remove and reinstall libtorrent-rasterbar and qbittorrent.

This solution seemed to work for me. I changed the repo within the cage, uninstalled those two packages, and reinstalled them. Now it is downloading and fully accessible through the webUI.

 

[GordeyGordeich]

This solution seemed to work for me. I changed the repo within the cage, uninstalled those two packages, and reinstalled them. Now it is downloading and fully accessible through the webUI.

Can you write detailed manual for newbies?

 

[100Stress]

This solution seemed to work for me. I changed the repo within the cage, uninstalled those two packages, and reinstalled them. Now it is downloading and fully accessible through the webUI.

Can you make a tutorial on how to do that please.


I'm not a newbie,......I'm a huge newbie

 

[GordeyGordeich]

Manual-tutorial

1. Need started qbittorent plugin.

2. Start Shell in jail (Jails -> qbittorent -> Shell)

Type: ls /usr/local/etc/pkg/repos​

Will see two files: FreeBSD.conf, iocage-plugins.conf​

3. Modify the file iocage-plugins.conf by Easy Editor (see ee manual).

Change latest to quarterly in url: line and save file.​

Type: ee /usr/local/etc/pkg/repos/iocage-plugins.conf​

Original file:​

Code:

iocage-plugins: {
            url: "http://pkg.FreeBSD.org/${ABI}/latest",
            signature_type: "fingerprints",
            fingerprints: "/usr/local/etc/pkg/fingerprints/iocage-plugins",
            enabled: true
            }

4. Update repositories

Type: pkg update​

​

5. Delete packages qbittorent-nox and libtorrent-rasterbar

type: pkg delete libtorrent-rasterbar​

type: pkg delete qbittorrent-nox​

​

6. Then install packages qbittorent-nox and libtorrent-rasterbar.

type: pkg install libtorrent-rasterbar​

type: pkg install qbittorrent-nox​

​

7. Restart plugin, if needed…

 

[lilomaster]

Manual-tutorial

1. Need started qbittorent plugin.

2. Start Shell in jail (Jails -> qbittorent -> Shell)

Type: ls /usr/local/etc/pkg/repos​

Will see two files: FreeBSD.conf, iocage-plugins.conf​

3.Modify the file iocage-plugins.conf by Easy Editor (see ee manual).

Change latest to quarterly in url: line and save file.​

Type: ee /usr/local/etc/pkg/repos/iocage-plugins.conf​

Original file:​

Code:

iocage-plugins: {
            url: "http://pkg.FreeBSD.org/${ABI}/latest",
            signature_type: "fingerprints",
            fingerprints: "/usr/local/etc/pkg/fingerprints/iocage-plugins",
            enabled: true
            }

4. Delete packages qbittorent-nox and libtorrent-rasterbar

type: pkg delete libtorrent-rasterbar​

type: pkg delete qbittorent-nox​

​

5. Then install packages qbittorent-nox and libtorrent-rasterbar.

type: pkg install libtorrent-rasterbar​

type: pkg install qbittorent-nox​

​

6. Restart plugin, if needed…

Sorry. I saw this request too late, but indeed, that is. Now, after modifying the file, it is convenient to run pkg update, for the repos to update. Then, continue with the process as described above. Now, when a new version of the plugin is released (hopefully with this problem solved), do we have to change that setting back, or it will be back when updating the plugin and the jail?

 

[GordeyGordeich]

…Then, continue with the process as described above. Now, when a new version of the plugin is released (hopefully with this problem solved), do we have to change that setting back, or it will be back when updating the plugin and the jail?

I'll leave these settings for now, because I'm interested in more stability.
Perhaps I will update packages directly in the jail manually.
Thanks for the idea of updating repositories. This step has been added to the manual.

 

[NicholasJS]

I think libtorrent-rasterbar 1.2.14_1,1 is the breakage.

See the PRs linked here.

FreshPorts -- net-p2p/libtorrent-rasterbar: C++ library implementing a BitTorrent client

libtorrent is an open source C++ library implementing the BitTorrent protocol, along with most popular extensions, making it suitable for real world deployment. It is configurable to be able to fit both servers and embedded devices. The main goals of libtorrent are to be efficient and easy to...

www.freshports.org

The quickest solution might be to go back from the latest to quarterly pkg repo, remove and reinstall libtorrent-rasterbar and qbittorrent.

I'm pretty sure you're right. The same behavior happens with deluge if I use that version of libtorrent.

 

[Volts]

The pkg builds for latest with libtorrent-rasterbar 2.0.6.27,1 are available now.

There's been a bunch of back-and-forth between the qbittorrent and libtorrent teams about memory management behavior. I'm optimistic, but it also might make sense to just stay on quarterly anyway.

---

Edit: I'm not having good luck with the updated qbittorrent and libtorrent-rasterbar 2.0.6.27,1. qBittorrent has crashed several times, and the whole system just crashed from memory pressure.

I'm going back to the versions from the quarterly pkg repo and locking them for the time being:

pkg lock qbittorrent-nox libtorrent-rasterbar

These had been very stable for me:

• qbittorrent-nox-4.4.2
• libtorrent-rasterbar-1.2.14,1

 

[mindfields]

It is not fixed yet?
I see a new update for the plugin...
Should I update it? Or it will break the plugin again?

 

[Volts]

I think you should wait at least until qBittorrent 4.4.3 is available, because it will have a new setting "Physical memory (RAM) usage limit".

The maintainer just updated the port yesterday. It will take a few days for the next pkg builds to become available.

Until that happens I think you should stay on those older versions I mentioned.

 

[mindfields]

I think you should wait at least until qBittorrent 4.4.3 is available, because it will have a new setting "Physical memory (RAM) usage limit".

The maintainer just updated the port yesterday. It will take a few days for the next pkg builds to become available.

Until that happens I think you should stay on those older versions I mentioned.

Thanks.

It will be great if you can update us when it's OK to update the plugin.
Thanks