19 hours ago, akhisyahmi said:

Hi, I read the FAQ and I can't seem to find the problem here. Im using unraid and one day qbit choose to break down on me.

 

Let me know if I accidently put my username and pass in there. I already edit it.

 

supervisord.log 4.33 MB · 2 downloads

you are connecting to a faulty endpoint, try connecting to another.

On 12/1/2023 at 1:08 AM, practicing-haunch2956 said:

I'm wondering if that recently changed? I didn't have that added before and I had been using qbittorrent just fine until that last update. Strange.

 

Anyway, that did the trick. Thank you so much.

nope, this has been the way for literally years.

2 hours ago, binhex said:

you are connecting to a faulty endpoint, try connecting to another.

Sorry but I don't have knowledge about this but I tried to Google around and even tried changing this IP to 0.1 but that doesn't fix it. What do you mean by faulty endpoint?

 

- Tried reset VPN credentials

- Tried deleting config

- Tried changing LAN_NETWORK

- Change VPN UDP to TCP

Edited December 6, 20232 yr by akhisyahmi

14 minutes ago, akhisyahmi said:

What do you mean by faulty endpoint?

i mean the remote host you are connecting to, which in your case (from your log) is 'my-kul.prod.surfshark.com' is not functioning correctly or is misconfigured by your vpn provider, connect to another endpoint.

16 minutes ago, akhisyahmi said:

Tried changing LAN_NETWORK

from your screenshot it looks incorrectly configured, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

1 hour ago, binhex said:

from your screenshot it looks incorrectly configured, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Ya I tried to change that to the same IP my modem is using. Doesn't work so I just revert it back to 192.168.1.0/24

 

UPDATE : Seems that my VPN is not working. I tried turn off the VPN and it works. I will contact my VPN for now. Sorry for the trouble @binhex

Edited December 6, 20232 yr by akhisyahmi

Is there a way to reset the webui password somehow?

 

My arr programs became unable to connect to the downloader the other day (week?). So I went to login and see what was up and it said my password is incorrect. I was sloppily using the adminadmin password since I only access it locally, wondering if an update possibly updated that since I had been negligent?

Anyway I'm locked out of my downloader, I can get into the conf file for it but that just lets me change the webui username. Is there another way for me to get this working again without doing a reinstall with fresh settings (I'm fairly attached to my settings)?

 

Thanks in advance.

 

 

2 hours ago, IamBrock said:

Is there a way to reset the webui password somehow?

 

My arr programs became unable to connect to the downloader the other day (week?). So I went to login and see what was up and it said my password is incorrect. I was sloppily using the adminadmin password since I only access it locally, wondering if an update possibly updated that since I had been negligent?

Anyway I'm locked out of my downloader, I can get into the conf file for it but that just lets me change the webui username. Is there another way for me to get this working again without doing a reinstall with fresh settings (I'm fairly attached to my settings)?

 

Thanks in advance.

 

 

You aren’t the only one. Go back through the last two or three pages and you’ll see several solutions.

3 hours ago, wgstarks said:

You aren’t the only one. Go back through the last two or three pages and you’ll see several solutions.

Thank you very much

On 11/26/2023 at 10:23 AM, nraygun said:

FWIW, I found this method in Reddit that seemed to work for me until they fix the log bug. But note if you have qbittorrent internet facing, it's a risk.

 

Adding this line under [Preferences], in the config file, works, for setting the default password manually to: adminadmin

WebUI\Password_PBKDF2="@ByteArray(ARQ77eY1NUZaQsuDHbIMCA==:0WMRkYTUWVT9wVvdDtHAjU9b3b7uB8NR1Gur2hmQCvCDpm39Q+PsJRJPaCU51dEiz+dTzh8qbPsL8WkFljQYFQ==)"

 

This worked for me!! Thanks!

Container is running as previously configured, but still cannot get into the WebUI even after changing password. Was working for a bit, then WebUI on LAN stopped working, radarr/sonarr can see it and still working well.

 

Tried reading up a bit more on the documents posted to fix the LAN_NETWORK to correct values for my server living on 192.168.50.220 but still not getting to WebUI. Port is default 8080, made sure to update the PIA OpenVPN folder as well.

 

Any thoughts?

 

1 hour ago, deeveeance said:

 

Any thoughts?

Attach your supervisord.log to your next post. Be sure to redact users/passwords.

Suddenly having issues reaching the WebUI (again). I fixed it recently due to the update requiring password etc, but now out of the blue I can't reach it. It's running fine and talking to *arr apps. Trying to reach locally from 192.167.1.57, and thought this was the correct setting for it.

1 hour ago, Nimrad said:

Suddenly having issues reaching the WebUI (again). I fixed it recently due to the update requiring password etc, but now out of the blue I can't reach it. It's running fine and talking to *arr apps. Trying to reach locally from 192.167.1.57, and thought this was the correct setting for it.

I’m not sure what your fix was but you don’t have 192.167.1.0/24 whitelisted. You can revert to an earlier version and make changes.

14 minutes ago, LogicalMadness said:

I'm having the same issue and it doesn't look like anyone ever answered this user's question.

Different question.

2 hours ago, wgstarks said:

I’m not sure what your fix was but you don’t have 192.167.1.0/24 whitelisted. You can revert to an earlier version and make changes.

Sorry, that was a typo. I meant that my local IP is 192.168.1.57.

My previous fix was rolling back, making a personal password and white listing my IP ranges before updating again.

Edited December 9, 20232 yr by Nimrad

On 12/9/2023 at 9:23 PM, Nimrad said:

Sorry, that was a typo. I meant that my local IP is 192.168.1.57.

My previous fix was rolling back, making a personal password and white listing my IP ranges before updating again.

I found my own issue. Without my knowledge I was connected over wireguard so my IP was not in fact whitelisted.

I'm not sure whether this is an issue with the docker container and the vpn (proton) or something about qbittorrent itself. But I'm experiencing two issues, which have to do with download speeds. They may be related though I'm not sure.

 

First, my download speed limits don't seem to be getting respected (though that seems like more of a qbittorrent problem than something with the way the container and vpn are configured). I have a limit of 10000 KiB/s and my downloads routinely go over that. I have checked all the options to apply the rate limits to all types of connections.

 

Second, and much more importantly, is that the overall bandwidth usage is much much higher than the application itself reports. Even when the application reports something like 15 MiB/s down, I can see in a network monitor that it ends up using  something like 120 MiB/s. Is that to be expected, either from qbittorrent's end or from the container/VPN configuration? 

 

Thanks, and please let me know what other information would be useful in helping me understand why this may be happening. 

On 12/8/2023 at 4:05 PM, wgstarks said:

Attach your supervisord.log to your next post. Be sure to redact users/passwords.

supervisord.log

 

Here ya go. 

 

Again, was able to get to it via LAN, but not from any external routing using port Forwarding or via OpenVPN Client (hosted within my Asus Router).

23 minutes ago, deeveeance said:

supervisord.log 294.04 kB · 0 downloads

 

Here ya go. 

 

Again, was able to get to it via LAN, but not from any external routing using port Forwarding or via OpenVPN Client (hosted within my Asus Router).

It is unlikely you would be able to access the webui using port forwarding, that would be very insecure anyway. You should be able to access it via openvpn though as long as you have entered the lan network (used by openvpn running on your asus router to assign addresses to openvpn clients) into the docker configuration. You currently have 192.168.1.0/24,192.168.50.0/24.

Hello,

I'm having trouble logging in to the WebUI. I am using PIA and using OpenVPN. Once I got everything setup (I was following Ibracorp Youtube video) I ran into this issue. I have tried doing the login in Firefox & Edge/Chrome, still can't login.

 

I then went and uninstalled the application and reinstalled, but kept everything default. I also turned off the vpn portion. Just to see if I can get into the UI. I have the same issue.

 

Any assistance would be appreciated.

I was able to get this fixed. I guess there is a bug in the current version of qbittorrent. I reverted back to a previous version, logged in, changed the password. I then reverted to the most current version and am able to login without issue.

I've been beating my head trying to troubleshoot this issue and I can't for the life of me find a solution.

I'm trying to get cross-seed to automatically run on torrent completion. I have the following in "run external programs" in qBit: curl -XPOST http://192.168.0.115:2468/api/webhook?apikey=[redacted] --data-urlencode "infoHash=[redacted]" and I have port 2468 set as VPN output port in the QBitVPN container.  I'm certain my APIkey is correct (I have it running correctly in Autobrr). 

 

 I'm seeing the following in the qbit logs:

2023-12-13T12:38:34 - Torrent download finished. Torrent: "Varsity.Blues.1999.1080p.BluRay.x264-nikt0"

2023-12-13T12:38:34 - Running external program. Torrent: "Varsity.Blues.1999.1080p.BluRay.x264-nikt0". Command: `curl -XPOST http://192.168.0.115:2468/api/webhook?apikey=[redacted] --data-urlencode "infoHash=[redacted]"` But I'm not seeing anything regarding this action in the cross-seed logs. I'm quadruple checked my API key and it is correct. The logs show autobrr's cross-seed API calls working correctly as well. Since cross-seed is running as expected for all other pieces, I suspect the issue has something to do with this container, but I'm honeslty clueless at this point. 

Hey everyone. Not really sure what's going on, any help would be appreciated.

 

qBittorrent was working fine until a couple days ago. Now when I start my container in Unraid, it fails to start and then goes back into stopped mode.

I get this in the container logs.

 

[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2023-12-13 09:13:33,064 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

2023-12-13 09:27:26,999 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 09:42:27,324 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 09:57:27,667 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 10:12:27,968 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 10:27:28,270 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 10:42:28,587 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 10:57:28,916 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 11:12:29,242 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 11:27:29,553 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 11:42:29,859 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 11:57:30,162 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 12:12:30,474 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 12:27:30,804 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 12:42:31,116 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 12:57:31,425 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 13:12:31,746 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 13:27:32,042 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 13:42:32,359 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 13:57:32,680 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 14:12:32,998 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 14:27:33,303 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 14:42:33,626 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 14:57:33,952 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 15:12:34,261 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 15:22:38,877 WARN received SIGTERM indicating exit request
2023-12-13 15:22:38,888 DEBG killing watchdog-script (pid 267) with signal SIGTERM
2023-12-13 15:22:38,888 INFO waiting for start-script, watchdog-script to die
2023-12-13 15:22:38,889 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22663020333008 for <Subprocess at 22663020332752 with name watchdog-script in state STOPPING> (stdout)>
2023-12-13 15:22:38,889 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22663017967440 for <Subprocess at 22663020332752 with name watchdog-script in state STOPPING> (stderr)>
2023-12-13 15:22:38,889 WARN stopped: watchdog-script (exit status 143)
2023-12-13 15:22:38,889 DEBG received SIGCHLD indicating a child quit
2023-12-13 15:22:38,889 DEBG killing start-script (pid 266) with signal SIGTERM
2023-12-13 15:22:39,890 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22663020233424 for <Subprocess at 22663019963088 with name start-script in state STOPPING> (stdout)>
2023-12-13 15:22:39,929 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22663020352784 for <Subprocess at 22663019963088 with name start-script in state STOPPING> (stderr)>
2023-12-13 15:22:39,929 WARN stopped: start-script (terminated by SIGTERM)
2023-12-13 15:22:39,930 DEBG received SIGCHLD indicating a child quit

** Press ANY KEY to close this window ** 

 

1 hour ago, Boy Kai said:

Hey everyone. Not really sure what's going on, any help would be appreciated.

 

qBittorrent was working fine until a couple days ago. Now when I start my container in Unraid, it fails to start and then goes back into stopped mode.

I get this in the container logs.

 

[info] qBittorrent process started
[info] Waiting for qBittorrent process to start listening on port 8080...

2023-12-13 09:13:33,064 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8080

2023-12-13 09:27:26,999 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 09:42:27,324 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 09:57:27,667 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 10:12:27,968 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 10:27:28,270 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 10:42:28,587 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 10:57:28,916 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 11:12:29,242 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 11:27:29,553 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 11:42:29,859 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 11:57:30,162 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 12:12:30,474 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 12:27:30,804 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 12:42:31,116 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 12:57:31,425 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 13:12:31,746 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 13:27:32,042 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 13:42:32,359 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 13:57:32,680 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 14:12:32,998 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 14:27:33,303 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 14:42:33,626 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 14:57:33,952 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 15:12:34,261 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '38560'

2023-12-13 15:22:38,877 WARN received SIGTERM indicating exit request
2023-12-13 15:22:38,888 DEBG killing watchdog-script (pid 267) with signal SIGTERM
2023-12-13 15:22:38,888 INFO waiting for start-script, watchdog-script to die
2023-12-13 15:22:38,889 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22663020333008 for <Subprocess at 22663020332752 with name watchdog-script in state STOPPING> (stdout)>
2023-12-13 15:22:38,889 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22663017967440 for <Subprocess at 22663020332752 with name watchdog-script in state STOPPING> (stderr)>
2023-12-13 15:22:38,889 WARN stopped: watchdog-script (exit status 143)
2023-12-13 15:22:38,889 DEBG received SIGCHLD indicating a child quit
2023-12-13 15:22:38,889 DEBG killing start-script (pid 266) with signal SIGTERM
2023-12-13 15:22:39,890 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22663020233424 for <Subprocess at 22663019963088 with name start-script in state STOPPING> (stdout)>
2023-12-13 15:22:39,929 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22663020352784 for <Subprocess at 22663019963088 with name start-script in state STOPPING> (stderr)>
2023-12-13 15:22:39,929 WARN stopped: start-script (terminated by SIGTERM)
2023-12-13 15:22:39,930 DEBG received SIGCHLD indicating a child quit

** Press ANY KEY to close this window ** 

 

For anyone else, going into the docker docker application settings, attempting to update a field, and selecting 'Apply' showed better error logs.

I had a port allocated twice somehow, not sure when it got introduced. Removed it from the config, and the docker started.