binhex
-
Posts
7898 -
Joined
-
Last visited
-
Days Won
37
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by binhex
-
-
13 hours ago, dgs2001 said:
Just wondering if I can get the two nzbget dockers to play nice (They are named differently and using different port allocations)
definitely possible, just ensure the name, the host port is different for each container and also you must have completely separate /config for each container, they cannot share the same path.
13 hours ago, dgs2001 said:check ip address which cannot be reached and Ich777 nzbget is now attempting to open localhost:6799 instead of localhost:6789
The fact it was fixed by a restart probably points the finger of blame at unraid web ui, but you can verify the port used to connect to the web ui by edit/toggling 'advanced view' (top right) and then checking the 'WebUI' port is what you expect, it is possible the web ui port did not update when you changed it.
-
It's automated and yes it's already there#
# Binhex updated this docker
#
Any way to manually update this to v1.20.60, or do I simply need to wait for binhex to update the docker?
I see now that v1.20.60 was only released today. I'll just be a little patient.
Sent from my 22021211RG using Tapatalk
-
50 minutes ago, qiosas said:
Is there any workaround to get webui access when using tailscale? It works perfectly otherwise, but cannot figure out setup to access when tailscale is running.
add the tailscale network range to LAN_NETWORK using a comma to separate values.
-
2 hours ago, nickydd9 said:
What, since when?
since the inception of this image in 2016, it was designed around the default 'bridge'.
2 hours ago, nickydd9 said:I don't think I am experiencing any issues with accessing the container locally or remotely via WireGuard.
so from a device with a 192.168.1.xxx ip you can connect to the qbittorrent web ui on ip 192.168.1.50?
-
28 minutes ago, Flyinace2000 said:
tcp4 0.0.0.0:58846: bind: address already in use.
docker thinks the port is already in use, so either you have another container running with that port (if so stop it), or docker is having a senior moment (it happens), try a reboot of your server.
-
31 minutes ago, derjp said:
i am wondering if these should be that big?
On 1/5/2024 at 6:41 PM, worldspawn said:Seems way too big for a docker that shouldn't be storing any large data (media or large files).
The base OS i use is not optimised for docker usage (rolling distro for a start) thus the images are larger than other base OS's such as Alpine, but there are advantages too. In short there is nothing i can do to optimise the image over what it currently is, do keep in mind though that the size shown in the screenshot is not the size you download on update (or size on disk), firstly its compressed and secondly and more importantly there is sharing of layers, its typically more around the 450MB range.
If it really annoys you then the only option is to switch to another image, LSIO use Alpine so the container size will be smaller. -
10 hours ago, bnovotny said:
--net='br0' --ip='192.168.1.12'
This is one issue, you cannot assign an ip to the docker container that is in the same range as your LAN_NETWORK (which it is), switch it back to the 'Bridge' (the default) then try again.
10 hours ago, bnovotny said:I'm stumped and pretty sure I just suck at iptables, any help is appreciated.
Feel free to tweak iptables, but be extremely careful, unless you know what you are doing you can easily cause a ip leak without knowing it.
-
5 hours ago, benjipewpew said:
ProtonVPN username 'MY_PROTON_USERNAME_REDACTED' does not contain the suffix '+pmp' and therefore is not enabled for port forwarding, skipping port forward assignment...
you have set STRICT_PORT_FORWARD to 'yes' and yet you have not added the suffix for the username as shown in the log, either set STRICT_PORT_FORWARD to 'no' or fix the username.
-
3 hours ago, jakeisrollin said:
i ended up changing my IP scheme from 192.168.1.2 to 10.10.0.1. i created a separate vlan for my server as 10.10.20.1 and assigned unraid to this network. i got most things running but deluge GUI is one of the ones i dont.
as you have been messing with your lan, check that LAN_NETWORK is still valid, also if you have vlan's and need access from different vlans then add those as well to the LAN_NETWORK list (comma separated).
for help on how to do this see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
-
1
-
-
1 hour ago, VRA said:
This has happened again
Looking at the protonVPN the config should be valid until next year. I don't really undestand why it seems to "expire" (or just stop working) after a while.Is there something I might be doing wrong? Either on generation of them or on the configuration on unraid?
i would contact ProtonVPN, this should not be happening.
-
On 1/21/2024 at 2:06 AM, Liquidbings said:
I can get deulge running on the vpn no problem. When I try and run any of the arr containers through it they seem to work as far as being able to use the gui, but can no longer talk with any of the other containers?
the missing part is you need to bypass the proxy for local addresses and also define 'Ignored Addresses', example:-
-
On 1/21/2024 at 10:28 PM, nickydd9 said:
From what I understand, the first step is resolving the VPN Provider's remote gateway, which uses the DNS on your host
Incorrect, it uses the name servers defined for NAME_SERVERS, it does not use whatever your host is using.
On 1/21/2024 at 10:28 PM, nickydd9 said:So now I am wondering what NAME_SERVERS is for.
To resolve the vpn endpoint (if its a name) and to do all name resolution for the application e.g. resolving peers/seeds from name to ip (if talking about a torrent client).
On 1/21/2024 at 10:28 PM, nickydd9 said:Is this the DNS servers to resolve for anything after the VPN tunnel has formed?
Before AND after the tunnel is connected, but once connected all future name server lookup is restricted to vpn tunnel only, if the tunnel goes down then name server lookup for the endpoint is done via cached lookups in the form of hosts file.
On 1/21/2024 at 10:28 PM, nickydd9 said:wouldn't we want to be using the VPN providers DNS servers and not manually specifying DNS to avoid leakage?
Not all vpn providers provide name servers to use, and even if they do not all vpn name servers are publicly accessible, so name resolution for the vpn endpoint (prior to being connected to the vpn) would be blocked resulting in the inability to establish a connection.
On 1/21/2024 at 10:28 PM, nickydd9 said:I am only asking because when I visit IPleak.net on a firefox container that I have routed through your qbittorrent vpn container, I do see my VPN Public IP address, but the DNS servers are listed as Cloudflare (which I currently have 1.1.1.1 configured as NAME_SERVERS because I skimmed through the template setup and didn't bother to change). I just kind of expected to see that I would be using my VPN providers DNS servers over the tunnel as I have always been told its best for security so you don't split DNS outside of the tunnel accidentally.
Firstly lets correctly define what name server ip leakage really is, this is leaking your ISP assigned ip via name server lookup, this cannot happen with this image, as mentioned above name server lookup is restricted to vpn tunnel only once connected, in the above scenario firefox will be using a public name server (1.1.1.1) but the requests will be coming from your vpn provider ip address and will not be from your isp assigned ip address, thus no leak.
For anybody else reading this, please keep in mind that nickydd9 is using a firefox browser in a container, and thus all traffic is sent down the vpn tunnel, if you are using a browser via privoxy (proxy) then this is a different scenario and name server leakage will occur.-
1
-
-
10 hours ago, krazytaco said:
I'm also trying to setup the container using protonVPN/wireguard and have yet to get the webUI working. I generated a fresh wireguard config file from proton, ensured port forwarding was allowed, and uploaded that to the config/wireguard directory - the container accepted it and auto-renamed to wg0.conf then started up seemingly fine, however when I try to visit the WebUI I get a connection timeout error. I was reading this guide from Proton and when I get to the part about verifying that port forwarding (natpmpc) is allowed I get a -7 Failed response for readnatpmpresponseorretry - I don't see why it would fail though since I just created the config file with the option toggled.
from your log file:- [info] ProtonVPN username 'vpn username' does not contain the suffix '+pmp' and therefore is not enabled for port forwarding, skipping port forward assignment...
follow Q31:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
-
5 hours ago, TheMarf said:
Hi! All of a sudden I'm unable to view my UI for this docker with VPN enabled, UI access is fine with it disabled. Had been working fine for a while. Not sure when the issue began as I rarely check on qbit as I primarily utilize sabnzbd.
VPN Provider: Privado
Actions Taken:
- Changed VPN password
- Replaced OVPN files
- Panicked
- Deleted and rebuilt the docker
- Followed the instructions here to make sure I addressed the UI port correctly.
- Searched reddit/github/here etc to see if I could find anything specific
- Edited the openvpn file to uncomment the section about version later than 2.5 (didn't resolve, was unsure if it'd help)
- Attempted to read the container logs via unraid UI.
- Found: "WARNING: file 'credentials.conf' is group or others accessible" and was unsure if it was a meaningful error
- Followed instructions on page 1 of the thread to get logs (I even waited an extra minute)
- Removed VPN name/pw from log.
- Posted on here trying to add a bit of humor and jest as I'm sure you get angry people yelling at you all the time
- ????
- Profit?
- supervisord.log
from your log:- 2024-01-17 22:41:00 [UNDEF] Inactivity timeout (--ping-restart), restarting
See Q17:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
-
On 1/16/2024 at 3:44 PM, illegal-deference8464 said:
oh its off the development branch not the nightly. ok thank you
Sorry looks like i was wrong, the upstream is targeting nightly, so hopefully you should have your fix, i will at some point switch this to releases only once Readarr gets a little more stable.
-
15 minutes ago, VRA said:
Hello,
I had a fully working qbittorrent with protonvpn.Yesterday I added a disk to an array. After that the qbittorrent fails to start up. The web UI is not accesible.
I have made no other changes.
All other containers are working normally.
I'm attaching the log, the vpn config, and the container config.
I'm not sure whats wrong and how can I fix it.
supervisor.log 4.35 MB · 0 downloads dockerContainer.log 5.16 kB · 0 downloads wg0.conf 327 B · 0 downloads
Looks like the endpoint you are specifying (via ip) is not operational any more, download a new wg0.conf from protonvpn for a different endpoint, from your log:-
readnatpmpresponseorretry() failed : the gateway does not support nat-pmp
-
53 minutes ago, K1LLA_KING_KING said:
It seems there is a network problem. All was fine before
firstly you cannot ping an ip address specifying the port.
And as you highlighted, the LAN_NETWORK is incorrectly configured, see Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md -
16 minutes ago, derjp said:
So as i tried to make changes in settings of nzbget-ng i receive the following error:
you dont know were i can find this folder or what i can do to solv this?
you need to go to the support thread for that image, i'm sorry i cannot support other images.
-
1 minute ago, derjp said:
so i need to install a driver for unraid from community app?
Possibly, yes, Realtek NIC's are notorious for having bad linux drivers leading to issues, i think there are drivers available via unraid 'plugins' but i have no idea if they will fix your TLS issue or not.
2 minutes ago, derjp said:and what do you mean with "nic"
NIC = Network Interface Card.
-
6 minutes ago, derjp said:
You are talking about the network port on mainboard? or am i totally on the wrong way?
Realtek RTL8125BG is the one from GIGABYTE B760M DS3H DDR4
whichever nic is connected.
-
14 minutes ago, derjp said:
I only have these in Community Apps, so try the ng one or not? sry i am pretty new to all this
for TLS think i always have messages like:
not sure if this is what you asked for/needed, if not let me know what you need and i will try to find it
i guess you could try the nzbget-ng image, but i have no idea if the unpack issue exists or not.
As for the TLS issues it maybe driver related, are you running Realtek NIC's by any chance?
-
5 minutes ago, derjp said:
unpack issue is just a thing on unraid right? on my normal pc using windows it works without a problem.
you tell me :-), i only have experience of running nzbget on unraid.
6 minutes ago, derjp said:so it doesn´t matter if i use another nzbget container from unraid community apps
i hate to say this but you may have better success with the Linuxserver nzbget image, i THINK it has less occurances of the unpack isssue, NO idea why it doesnt suffer from it so much *shrug*
7 minutes ago, derjp said:where can i found the workaround for TLS on which page? looks like i missed it.
the workaround is built into the image, are you saying you are still seeing TLS related issues then, if so detail what you see.
-
4 hours ago, illegal-deference8464 said:
what determines the build of readarr you are using in this repo?
releases, as can be seen here:- https://github.com/Readarr/Readarr/releases when a new release is created then a build will be automatically triggered and if successful it will be pushed to multiple registries.
-
1 hour ago, raindove said:
misconfigured LAN_NETWORK, from your log:-
2024-01-15 23:35:13.714631 [info] LAN_NETWORK defined as '192.168.0.1/24'See Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
[Support] binhex - qBittorrentVPN
in Docker Containers
Posted
please can you do this:-
Left click the container and select 'Edit', make any change to a value, then switch it back to what it was and click on 'Apply', then copy and paste the 'Command execution' shown to a file and attach and post here.