RGauld
-
Posts
117 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by RGauld
-
-
Having the same issue as well... unbalance wont run unless started from a command line...
Also, I've been having this problem for a while now... unbalance is set to use port 6237,
and yet when I try to open it using said port, it won't run... However, if I run it using
port 6238, it works fine... Am I missing something here? I've attached image files
and the log in the hopes this can be fixed...
-
In regards to unbalance not working, this was your response:
"Hi, checked the logs, there are several successful gathers, and towards the end of the log, some attempts that get flagged due to
flag:(rsync: failed to set times on "/mnt/disk11/Media2": Operation not permitted (1))
Not sure what's the issue with that share (Media2), but for some reason rsync can't set times on it."
I added the -O switch to the settings, Custom RSYNC Flags, and it appears to have solved the problem...
Also, I've had an issue where the setup for unbalance specifies port 6237, but I can't get the plugin to work
unless the web page I open uses ********:6238.... not a big deal, just weird....
-
-
I seem to be having an issue with unbalance... Whenever I run it to move files across my disks, it always ends with an error...
After checking the disk the files were supposed to be moved to, I see it made the directory and sub-directories but there are
no files within them. It doesn't matter if I use scatter or gather, I end up with the same error... I have tried deleting the .conf
file, as well as uninstalling and reinstalling the plugin...
-
21 hours ago, wgstarks said:
Care to share the reason PIA used for this? I don't mean personal stuff, just wondering II f this is something others need to be concerned about.
No reason, other than I guess they thought i wanted to cancel my account... I just dont like the auto-renewal option... I prefer to renew manually...
-
16 hours ago, jonathanm said:
Reading between the lines, I'd say it's because the account was cancelled for non-payment, and they refused to reactivate it and wanted him to sign up for a new account instead of applying the payment to the cancelled account and reactivating it. With auto-renewal off, it's on the user to make sure payment is kept up to date to keep the account active.
No, the account was in good standing, and had 20 months left on it... I simply didn't want the auto-renewal on...
-
After all of the issues I've had, it would appear that PIA went ahead and cancelled my account, which was the reason that I couldn't get the docker to work properly... After some time spent with PIA support, they finally refunded my purchase, and I decided to go with another vpn provider... I have since re-configured all the docker containers to the new vpn provider, and they work perfectly! My thanks to Binhex and everyone else who helped me with this problem!
-
1
-
-
My apologies to all who have helped me with this issue.... I finally received a response to my support ticket from PIA....
It seems that because I turned off the auto-renewal option on my account, they decided that my account was no longer
active... I'm sorry for suggesting it was an unRAID issue, or a docker issue, as I had no idea PIA would cancel my account...
I have since informed PIA that my account is not to be cancelled, considering I paid for a 2 year subscription, and that I'd
appreciate it if they would re-enable my account.... I will let you all know what the results are as soon as they fix their error...
-
4 hours ago, binhex said:
one more thing to check, are you copying and pasting the credentials or are you manually typing the credentials into the unraid web ui configuration for the docker?, if you are copying and pasting then watch out for spaces at the beginning/end of the username and/or password (encountered by other user).
I am not cutting and pasting (I thought of that some time ago...), I made sure to type in the login details manually...
I'm currently waiting on a support ticket with PIA to see if it's something on their end, although I can log into my
account on their website using the exact same credentials with no problems.... This issue is becoming more and
more frustrating, to say the least... I'm hoping it has something to do with PIA at this point...
-
23 hours ago, binhex said:
im sorry but there is no way this is related to unraid, and if there were issues with this container then with all respect i would expect a lot more reports than 1 (10+ million downloads of this image). i have seen this symptom before and every time its been related to login details, not sure what else i can say or suggest at this point, maybe contact the vpn provider and see if they can see anything on their end as to why you cant authenticate correctly.
If its not related to unRAID, then perhaps the docker image itself (current version is 18.06.1-ce), as I remember someone saying I should revert to a previous version of the docker image (not sure how to do that...). I have a support case running with PIA to make sure it is not on their end, and I'm waiting to hear back from them...
-
3 hours ago, binhex said:
Ok try the following:-
Ensure you are using the correct account details, not forum login details, make sure it's the right login name.
Change your password and then change it for container to match to ensure there is no issues on the providers end.
Double check your account is still active and you have paid.
I have done all of this... I have triple checked all the login details, my account with PIA is active and working...
I also run Sabnzbd-vpn and I get exactly the same error, which is why I believe it to be an issue with unRAID
or the docker itself....
-
On 10/2/2018 at 6:05 PM, jonathanm said:
Possible. Do you have non-alpha numerics in your password? If so, try changing to a long password with letters and numbers only.
No, there are no non-alpha numerics in my password, just consists of letters and numbers....
I still get the same error... I would really like to get this problem fixed, as paying for a vpn service I cant use is frustrating to say the least....
I still think it has something to do with unRAID, as this docker worked before unRAID updated to version 6.6.x
-
On 10/1/2018 at 4:35 AM, binhex said:
wrong username and/or password for your vpn connection, from your log:-
Sat Sep 29 08:06:41 2018 AUTH: Received control message: AUTH_FAILEDI have changed my password with PIA, and in the settings for Deluge, and I still get:
"AUTH: Received control message: AUTH_FAILED"
Am I missing something?
-
-
I seem to be having trouble getting binhex-sabnzbdvpn to work in UNRAID v6.6.0.... I have setup my vpn
account with PIA and know it to be working... When I try to open the docker with the vpn option enabled,
it refuses to connect (unable to open the WebUI), however when I disable the vpn, it connects fine... I had
this all working in the previous release of UNRAID, but with this release candidate, I can't get the docker to
work when I try to enable the vpn connection. I'm not sure how I can fix this, and would rather not revert
to the previous version of UNRAID, as I like this new version.
Image 1 shows the docker page.
Image 2 shows binhexx-sabnzbdvpn settings.
Image 3 shows the error when i try open the WebUI with the "VPN_ENABLED" set to yes.
-
I seem to be having trouble getting binhex-delugevpn to work in UNRAID v6.6.0.... I have setup my vpn
account with PIA and know it to be working... When I try to open the docker with the vpn option enabled,
it refuses to connect (unable to open the WebUI), however when I disable the vpn, it connects fine... I had
this all working in the previous release of UNRAID, but with this release candidate, I can't get the docker to
work when I try to enable the vpn connection. I'm not sure how I can fix this, and would rather not revert
to the previous version of UNRAID, as I like this new version.
Image 1 shows the docker page.
Image 2 shows Deluge-vpn settings.
Image 3 shows the error when i try open the WebUI with the "VPN_ENABLED" set to yes.
Image 4 shows the WebUI when the "VPN_ENABLED" set to no.
-
On 1/19/2018 at 11:28 AM, jbrodriguez said:
I could have increased the hard limit, but since the min free space is configurable, I decided to leave it be.
I understand that XFS is better behaved with regards to fully populated disks, but people in the forum with knowledge on the matter still recommend not filling up a disk.
What would you suggest filling the available hard drives to?
I have my array set to fill approx. 85% of my drives....
-
thanks for the update! I no longer receive that message when I boot unRAID now...
Boot up screen show no errors, and the unBALANACE interface works great!
Thanks for your help!
-
I seem to be getting this every time I start unRAID:
"/bin/bash: line 3: /usr/local/emhttp/plugins/unbalance/scripts/stop: No such file or directory"
[Plugin] unbalanced
in Plugin Support
Posted
So, in the unbalance settings on the settings page, should I change it from 6237 to 6238?