Updating that it announces the port every 15 minutes, my subnet did change from xfinity's 10.0.0.1 and as far as I am aware my new subnet is 192.168.4.1 and changing my lan network to 192.168.4.0/24 leaves me unable to access my server webui located at 192.168.4.157:8080 from my pc located at 192.168.4.35, all of this with vpn enabled, and running curl ifconfig.me does return my vpn ip, not my ip, so I know the vpn is connected, any help would be appreciated and let me know if I need to provide any more information

On 8/4/2024 at 6:18 PM, cwebb said:

Error response from daemon: driver failed programming external connectivity on endpoint binhex-qbittorrentvpn (6f338e9fd54a4aa2f0ff411e32b3afc803bc76c7111556ff8cbba32c219b344e): Bind for 0.0.0.0:58946 failed: port is already allocated.

hi getting this message when i try to apply the docker container , and the docker will not start , just says server error 

I am also getting this same issue. Is there a resolution for this?

On 9/13/2024 at 3:13 PM, nekromantik said:

Anyone else have issue recently where Qbitorrent creating a folder of the finished torrent even though the torrent did not contain its own folder?

 

To explan:

 

I download torrent with following file in the torrent: torrent.txt

The finished torrent is saved to: completed/torrent/torrent.txt instead of completed/torrent.txt

Settings -> Torrents -> When Adding a Torrent -> Torrent Content Layout -> change this from "Create Subfolder" to "Original"

I installed the binhex-qbittorrentvpn docker and changed a few of the ports since it was interfering with my SABNZBD docker however the Qbit docker will not even open a webUI and just gives me the basic "this site cant be reached"


the only port i changed was the "Port: Web Interface: 8081" (default is set to 8080 which is what my sab docker is using.)
I also changed the "Variable: WEBUI_PORT: 8081" (default is also set to 8080)

Not sure what else to really do, I've tried to search around for videos and I'll follow the entire step outside of the above changes and still it will not work.



 

46 minutes ago, ColtonT said:

still it will not work.

For a test, set the VPN to no, and see if the interface loads.

Just now, JonathanM said:

For a test, set the VPN to no, and see if the interface loads.

negative still the same issue. "site cant be reached"

Just now, ColtonT said:

negative still the same issue. "site cant be reached"

https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Have you gone through binhex's docs?

20 minutes ago, JonathanM said:

https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Have you gone through binhex's docs?

So i just went through this for the one specific to qbit and followed the Q4 and A4 as that was my issue. However I rebooted the entire OS and now whenever i open the webui (for qbittorrent) now on port 8888 it opens up my SAB docker for some reason. I did this resolution for both port 8888 and 8081 and same results of opening up sab.. the URL still opens on the default port of 8080

EDIT:

I have figured out how to get to the login screen with VPN Disabled, the "webUI" Option under "advanced view" was directing to "IP:8080" I changed this to reflect my updated port of "8888"

However if I turn VPN ON the webui/docker doesnt seem to work anymore.

Edited September 19, 20241 yr by ColtonT
added info

11 minutes ago, ColtonT said:

However if I turn VPN ON the webui/docker doesnt seem to work anymore.

That means the VPN isn't configured or connecting properly. Look through the supervisor.d log after a failed attempt for clues.

10 minutes ago, JonathanM said:

That means the VPN isn't configured or connecting properly. Look through the supervisor.d log after a failed attempt for clues.

Wonderful, Thank you much for the assistance and pointing me in the correct direction!

Hi, 

After a very long time of seamless usage, I suddenly lost access to the WebUI through Tailscale. Previously, after configuring the VPN, I didn’t have access via local addresses, but it always worked through Tailscale. I’ve tried reboots.

Can you help me?

Edit1: Also Prowlarr lost conncection with qbit. 

 

Solution: I just needed to download new config file from my vpn. 

 

Edited September 24, 20241 yr by Gobblerpl
solution

Hello,

Having some inbound issues i think? Might be a messed up port setting? Seems I'm unreachable to any PT's, though I can download from all of them. Hopefully someone that has eaten a few less crayons than myself can help. Hopefully these are the logs being requested as I'm not entirely sure!

One further issue, my watch folder is improperly setup somehow. I'm sure I'm not passing something along correctly, but any help on that issue would be much appreciated. If someone can actually get this working, ill gladly buy you a beer, or a case. Possibly a truck load.

Help.txt supervisord.log

3 hours ago, Zarroc said:

Having some inbound issues i think?

Do you intend to use a paid VPN to hide behind? If not, you need to open and forward a port through your router and into the container.

11 hours ago, JonathanM said:

Do you intend to use a paid VPN to hide behind? If not, you need to open and forward a port through your router and into the container.

I do have PIA, however with a few PTs it seems to be a problem with being connectable. Thats why its currently turned off. I believe you are correct for port forwarding. However I feel like i opened the correct port? but i could be wrong. the TCP port for Qbit is set for 55001, and i did go to router settings and open 55001, but i think i did it incorrectly. my internal should be 55001 correct? I guess I'm just not sure what the external port to open should be? Or am i going about this incorrectly?

1 minute ago, Zarroc said:

However I feel like i opened the correct port?

I didn't see any indication that you added the port to the container config.

 

Normally with binhex's VPN enabled containers there is no port defined in the container template, because it is assumed you will be using a VPN with port forwarding inside the VPN tunnel.

 

I suggest trying to get PIA working again, being sure that you select an endpoint that supports port forwarding. If you can't get it working, look through the supervisord.log file after the attempt, redact all your PIA credentials (probably multiple places) then attach it to your next post.

45 minutes ago, JonathanM said:

I didn't see any indication that you added the port to the container config.

Alright, so perhaps this is the issue? is the port not taking effect? or am i looking at the wrong thing and thinking ive done something that i havent. I just expanded the "more settings" at the bottom of the docker properties menu and it shows that setting? I can send a screenshot if im not describing this well? 

When I had used PIA it was still showing as unconnectable. I was using a canada ome, i think ontario. which was listed as available for port forwarding. 

Is "canyouseeme.org" a good test for whether my address/port are connectable?

I'm sorry for not attaching Supervisor log! I followed your instructions but there is no supervisord.log file in Qbittorrent's /config. Not sure what to do about that, so I attached the qbittorrentvpn debug log instead.

 

The issue I'm having is being unable to access my webUI while connected to a VPN. I can however access the webui when I set VPN_ENABLED to "no." With VPN enabled, I keep getting a "gateway does not support nat-pmp" error in my qbit log, even when I enable NAT-PMP and select a P2P-enabled Proton server in the config.

Command execution.docx Qbit debug log.docx

Edited September 24, 20241 yr by Andible

2 hours ago, Zarroc said:

I can send a screenshot if im not describing this well? 

The docker run command would contain what's needed to check.

 

canyouseeme is good for non-vpn connections.

 

31 minutes ago, JonathanM said:

The docker run command would contain what's needed to check.

 

canyouseeme is good for non-vpn connections.

 

Is this what you need?

CommandExecution.txt

44 minutes ago, Zarroc said:

Is this what you need?

 -p '55001:100/tcp'
 -p '55001:000/udp'

 

Those are wrong.

 

They should look more like this

-p '8080:8080/tcp'

with the same numbers on both sides.

 

If you select advanced mode on the template you should be able to find and correct them.

1 hour ago, JonathanM said:

 -p '55001:100/tcp'
 -p '55001:000/udp'

 

Those are wrong.

 

They should look more like this

-p '8080:8080/tcp'

with the same numbers on both sides.

 

If you select advanced mode on the template you should be able to find and correct them.

the :100/tcp and :000/udp looks to be the container port from what i can see? Is that correct? If so for some reason when I go to edit that setting those two are greyed out. 

1 minute ago, Zarroc said:

the :100/tcp and :000/udp looks to be the container port from what i can see? Is that correct? If so for some reason when I go to edit that setting those two are greyed out. 

Delete and recreate those two port entries, but with 55001 on both host and container.

Unable to access Qbit Web GUI

I'm running qbit by binhex as a docker container on my Unraid 6.12.10. I followed this trash guide to set it up:

 
According to the log the VPN and Qbit are running just fine, however, I cannot access the Web GUI  for qbit once it has started. I get a timeout and the page won't load. I usually access hosts on my LAN via another subnet but I've included both my LAN and Subnet IP ranges in the LAN_NETWORK section of the container. I also tried accessing the GUI directly from my LAN but it also times out. I am forwarding port 8080 to 8083 but I've confirmed the container is properly forwarding to that port and I have no conflicting ports.

supervisord.log commandexecution.txt

10 minutes ago, captainkegs said:

Unable to access Qbit Web GUI

I'm running qbit by binhex as a docker container on my Unraid 6.12.10. I followed this trash guide to set it up:

 
According to the log the VPN and Qbit are running just fine, however, I cannot access the Web GUI  for qbit once it has started. I get a timeout and the page won't load. I usually access hosts on my LAN via another subnet but I've included both my LAN and Subnet IP ranges in the LAN_NETWORK section of the container. I also tried accessing the GUI directly from my LAN but it also times out. I am forwarding port 8080 to 8083 but I've confirmed the container is properly forwarding to that port and I have no conflicting ports.

supervisord.log 31.38 kB · 1 download commandexecution.txt 1.59 kB · 0 downloads

From your log-

Quote

The WebUI administrator username is: admin
The WebUI administrator password was not set. A temporary password is provided for this session: TghmEjZuU

Are you using these temporary credentials?

34 minutes ago, JonathanM said:

Delete and recreate those two port entries, but with 55001 on both host and container.

Ho Lee Jesus. I think that did it. canyouseeme is able to see that port is open now, seems im also uploading one or two of the public trackers im using to test so i dont kill my PTs. Going to wait till i see that connectable status on a few PTs and then im buying you a case of beer.