binhex
-
Posts
7899 -
Joined
-
Last visited
-
Days Won
37
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by binhex
-
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.
-
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.
-
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? Sent from my 22021211RG using Tapatalk
-
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
-
i know what you are trying to connect to, my question is what is the ip of the machine running the web browser?
-
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.
-
thats a successful start, what is the ip address of the machine running the web browser that you are attempting to connect with?
-
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. Can you verify that the host path you set for /media exists and has the correct permissions set Sent from my 22021211RG using Tapatalk
-
that is very odd, i dont understand that at all. 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?. 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 deleted Sent from my 22021211RG using Tapatalk
-
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. Sent from my 22021211RG using Tapatalk
-
This has now been pushed to main, please remove the tag :test 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. 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 main Sent from my 22021211RG using Tapatalk
-
stalled means transfer speed was/is near or at zero, i see you are transferring thousands of files, so stalling can happen under this circumstance, but it shouldnt be anything to worry about. yes its fine and no you do not need to stay connected to vnc in my experience the answer is yes you can trust krusader, but feel free to do a compare once the copy is complete to verify everything is copied across.
-
Nope, wanna be the guinea pig? [emoji16] Sent from my 22021211RG using Tapatalk
-
Read Q24 for full instruction:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md
-
i need the full log to really help you out, can you please do the following:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md
-
it looks like the openvpn config file does not match your vpn providers openvpn servers configuration, re-download from your vpn provider.
-
none of this is due to the update, you have something else going on, file corruption, usb key failing, mover moving config files perhaps, i run this image myself and there were zero breaking changes going from the previous version to the latest. you can see any changes committed here:- https://github.com/binhex/arch-qbittorrentvpn/commits/master and as you can see the main change was the addition of protonvpn, this will not of affected any of the things you listed.
-
set the container toggle for 'Privileged' to on.
-
yeah ignore this, its of no consequence, lets check for database corruption, see Q4 (yes i know plex is starting but lets rule it out):- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md
