-
Posts
7,934 -
Joined
-
Last visited
-
Days Won
38
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by binhex
-
-
24 minutes ago, Mainfrezzer said:
Is that already implemented? Only working for openvpn or still an upcoming feature?
Im currently using the container to connect to a wireguard server thats behind a dynamic ip and its been a bit of a hassle to restart the container each time the endpoint has a new ip assigned (which happends either once every 24h or, if the telekom decides to be muppets again, 20 times a day)nope, its still to be done.
- 1
-
1 hour ago, SoleInvictus said:
if this is a stupid way to configure this, I'm open to ideas. Just don't want to leak my IP.
oh and btw if i were you i would keep this simple and use the delugevpn image instead of doing network pass through, its a lot less hassle.
- 1
-
24 minutes ago, SoleInvictus said:
Of course. Two ways: the IP address shown in the webGUI, plus I got a nasty email from my ISP regarding certain alleged activities, which is what made me realize all this was going on. What's extra weird is the IP in the GUI shows my ISP assigned IP, but curl ifconfig.io shows my VPN IP. I'm super confused here.
Here's a super recent copy of the log. Thank you so much for your help.
OK i have been able to replicate your issue partially - deluge web ui is showing the vpn ip address for me not my isp assigned ip but i can make deluge leak when incorrectly configured, which is what you have done, let me explain the issue...
So from your logs i spotted that you have set the following:-
VPN_INPUT_PORTS defined as '3000,3389,58846,58946,8112' VPN_OUTPUT_PORTS defined as '3000,3389,58846,58946,8112'
This is incorrectly set, you only need to add in the web ui port, you have in effect permitted the deluge daemon incoming port to be accessible from your internet connection and thus its bypassing the vpn, the values should instead be as follows:-
VPN_INPUT_PORTS defined as '3000,3389,8112' VPN_OUTPUT_PORTS defined as '3000,3389'
Note the fact that i have removed the default incoming ports (58846 tcp and 58946 udp), also you do not need an outgoing port defining for the web ui (port 8112).
This should fix your issue, to confirm go here:- https://www.top10vpn.com/tools/do-i-leak/ and do a torrent ip leak test, do not worry about ipv6 its blocked, also ignore any web browser leaks, its of no concern as your browser will return your isp ip, its the torrent client you need to concentrate on.
- 1
-
29 minutes ago, SoleInvictus said:
While binhex-deluge is showing my home IP
can you detail exactly how you are identifying that deluge is using your isp assigned ip?, also please can you post your privoxyvpn log found at '/config/supervisord.log'
- 1
-
5 hours ago, Bushibot said:
Wow that is kind of confusing but a little more digging on my end suggests this is actually PIA vpn issue. Maybe port forward?
downloading to specific paths on your host has nothing whatsoever to do with the vpn provider or port forwarding, you simply do not yet grasp how docker bind mounts work.
firstly you need to create a new 'path' for the container or edit the existing path, e.g.:-
once this is done then wait for deluge web ui to be accessible and then configure deluge, for example assuming a host path of ' /mnt/user/datapool/watch' you would configure deluge watch to be '/data/watch' that is because ' /mnt/user/datapool' = '/data' thus the subfolder watch = '/data' + '/watch' you get it?.
-
Just be careful out there guys and don't use default creds and for the love of God turn off upnp.
https://torrentfreak.com/qbittorrent-web-ui-exploited-to-mine-cryptocurrency-heres-how-to-fix-230902/
Sent from my 22021211RG using Tapatalk- 2
-
On 8/22/2023 at 2:55 PM, twistedlabel said:
Ive finally had time to do the above. I hope it helps!
Thanks!
Err thats a log from Krusader container not Deluge, try again.
-
On 8/20/2023 at 8:13 PM, Alias_ZA said:
Figured my issue out. Seems my whole config reset, including password and default folders.
Any idea why this happens?
if you server has had a unclean shutdown due to crash or power interruption for instance then data loss can occur, including loss of configuration.
-
6 hours ago, sdballer said:
I installed kate via apt-get update, apt-get install kate
not if you are using this image you didn't, this is an arch based image, package management is done via 'pacman' not 'apt-get', check which image you are using and use the correct support thread.
-
3 hours ago, doctortt said:
Krusader is correctly showing you the disk space available within the docker image, i would guess you have a 30GB docker image created right?, i would also suspect you are not doing a docker bind mount from your host path to '/3_unraid_shares' and thus its writing inside the docker image and not to your host.
To correct this create a new 'path' e.g.:-
-
Where is the wg0.conf file located?Heya,
Container won't start for me all of a sudden, has been working fine all week.
Error I get:
2023-08-19 14:54:15.619603 [info] Host is running unRAID
2023-08-19 14:54:15.638155 [info] System information Linux 45f93a930e14 6.1.38-Unraid #2 SMP PREEMPT_DYNAMIC Mon Jul 10 09:50:25 PDT 2023 x86_64 GNU/Linux
2023-08-19 14:54:15.660715 [info] OS_ARCH defined as 'x86-64'
2023-08-19 14:54:15.681645 [info] PUID defined as '99'
2023-08-19 14:54:15.718547 [info] PGID defined as '100'
2023-08-19 14:54:15.759454 [info] UMASK defined as '000'
2023-08-19 14:54:15.779683 [info] Permissions already set for '/config'
2023-08-19 14:54:15.801727 [info] Deleting files in /tmp (non recursive)...
2023-08-19 14:54:15.827788 [info] VPN_ENABLED defined as 'yes'
2023-08-19 14:54:15.848815 [info] VPN_CLIENT defined as 'wireguard'
2023-08-19 14:54:15.869467 [info] VPN_PROV defined as 'custom'
2023-08-19 14:54:15.897223 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2023-08-19 14:54:15.928502 [crit] VPN configuration file /config/wireguard/wg0.conf does not contain 'Endpoint' line, showing contents of file before exit...
** Press ANY KEY to close this window **
It's not showing contents of file before exit if that helps.
my wg0.conf file looks like this:
[interface]
# Device: Just Moth
PrivateKey = ***
Address = 10.67.102.237/32
DNS = 10.64.0.1
[Peer]
PublicKey = ***
AllowedIPs = 0.0.0.0/0
Endpoint = 154.47.30.143:51820
Any help would be great!
Sent from my 22021211RG using Tapatalk
-
1 minute ago, Nowjon said:
Ah sorry! My current IP is 10.10.10.146 and I can get to 10.2.2.10 just fine via traceroute
routing maybe working fine but this image is locked down hard to prevent ip leakage, if you are connecting from a different network range than what is defined in LAN_NETWORK then you will be unable to connect, change LAN_NETWORK value to 10.2.2.0/24,10.10.10.0/24
-
50 minutes ago, Nowjon said:
I'm attempting to connect to http://10.2.2.10:8112/
i know what you are trying to connect to, my question is what is the ip of the machine running the web browser?
-
On 8/11/2023 at 12:03 AM, binguser said:
Using ProtonVPN and occasionally natpmpc will fail, has anyone else encountered this? Not sure if this is a ProtonVPN issue or a Deluge issue.
That will be a protonvpn related issue, deluge is in no way involved in natpmpc, deluge is simply configured to use the incoming port once assigned via natpmpc.
- 1
-
3 hours ago, Nowjon said:
I'm having this same issue, were you able to resolve this?
If not, I'd appreciate any assistance, I've followed https://github.com/binhex/documentation/blob/master/docker/faq/help.md for the attached log file. supervisord.logthats a successful start, what is the ip address of the machine running the web browser that you are attempting to connect with?
-
17 minutes ago, optiman said:
@binhex Any update on fixing this? I'm still on 4.0.1-1-01, which is working fine.
if the issue is with a third party script (which it looks like it is, right?) then you will need to raise an issue and say the script is not compatible with the latest version of sabnzbd, a quick google looks like you would raise an issue here:- https://github.com/clinton-hall/nzbToMedia/issues
EDIT - looks like this is a match for your issue, your script is out of date most likely:- https://github.com/clinton-hall/nzbToMedia/issues/1960
-
This is odd! I am using this image myself, just restarted the container and it started with no problems.Seeing this exact same issue. Did you ever get it resolved? I even tried completely deleting the container/appdata and i'm still getting the issue.
Can you verify that the host path you set for /media exists and has the correct permissions set
Sent from my 22021211RG using Tapatalk
-
10 hours ago, Mooseknuckles said:
For some folders yes, for some folders no.
that is very odd, i dont understand that at all.
10 hours ago, Mooseknuckles said:I notice that the scripted in terminal is only referring to Disk 1 for the share when there are 2 disks. Maybe that is why ?
no, this should not be the cause, the script will look through al disks looking for a matching top level folder named after --media-shares, which in your case is 'Server' (case sensitive), you do have a share called 'Server' right?.
10 hours ago, Mooseknuckles said:At this point I actually want to disable but I cannot as I want to delete some folders.
run the script as follows:-
/tmp/no_ransom.sh --lock-files 'no' --media-shares 'Server' --debug 'yes'
post the output, this will definitely unset any attributes set by this script.
-
Try doing a refresh in Windows explorer after what looks like a successful delete, I think you will find the file isn't actually deletedThanks for that, deleting through windows explorer. SMB permissions are public and I can make a folder and delete it no problem there. Enabling the script back does not stop me from deleting.
Sent from my 22021211RG using Tapatalk
-
1 hour ago, Mooseknuckles said:
For some reason, after inputting "/tmp/no_ransom.sh --lock-files 'no' --media-shares 'Server' --debug" into terminal I am only able to delete files and not folders. I also tried re re-enable and it is in the same state as applying no, can delete files but not the folder.
how are you attempting to delete the folders via windows explorer?, if so then it could be your SMB share permissions that are preventing this or even folder permissions (this script sets attributes not permissions).
-
Parity is still worthwhile as it allows you to recover from physical hard drive failure with no data loss, but parity is not backup as you have found out.Ok, sorry for the misunderstanding. In this case, I see even less sense in it, in comparison to a backup (you can rebuild from backup, too, so it seems top be just a matter of backup frequency: Parity/RAID for instant mirroring of immediate data, including all mistakes I make, vs. backup for delayed mirroring of slowly changing data that can revert mistakes I make).
This actually makes me reconsider if I really need a parity disk for personal data use...
Sent from my 22021211RG using Tapatalk
- 1
-
This has now been pushed to main, please remove the tag :testThat worked. Thanks so much!
Sent from my 22021211RG using Tapatalk
-
Well I am, I get great comfort in knowing I cannot accidentally delete my media, and of course protection against ransomware. The only two alternatives I can think of currently are offline backups or zfs snapshots.Is anybody using this script still? Or are there any newer ways to projetct your data from encryption?
Sent from my 22021211RG using Tapatalk
-
I have created a new test image with Java included can you please give it a try by appending :test to the name of the repository for the container and applying, let me know if it works so I can push to mainHi there! Is there a way to add a variable or something to fix this message?
Using direct disc access mode
AACS directory not present, assuming unencrypted disc
This disc requires Java runtime (JRE), but none was found. Certain functions will fail, please install Java. See http://www.makemkv.com/bdjava/ for details.
Sent from my 22021211RG using Tapatalk
- 1
[Support] binhex - Sonarr
in Docker Containers
Posted
sonarr is reporting correctly, there is no /download bind mount for the sonarr container as can be seen from your screenshot, you need to do as @wgstarks mentioned and ensure all containers download to the same path, see Q4 for an explanation:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md