Burizado
-
Posts
113 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Burizado
-
-
11 minutes ago, UnraidDuck said:
I'm using the binhex-plexpass version.
This is what I have in settings for the binhex-plexpass version.
I just tested and it is transcoding to RAM.
Edit: I just updated a few hours ago so it should be the latest build.
-
I don't want to jinx it, but I have been up successfully for months after switching to the Wireguard setup. My container does restart nightly for backups, so it is restarted often and still works.
I will go find some wood to touch now. If I come back tomorrow stating it is not working, I will only blame myself.
-
Hello All. I thought this might me the best place to post this topic as it's not really "issue" related that needs support help.
I have a fairly good size library of my movies mostly all 1080p content. I am looking at starting to update some of them to 2160p. I would like to keep the 1080p files in case I am streaming to phones or tablets and don't want to transcode down the 2160p files, or if I am accessing my content away from home. My main question is what is the best way to go about this?
In my research I have found basically two thoughts on Plex organization:
- Setup a separate 'Movies-4k' directory and put all 4k content in there. Keeping all the 1080p files in the 'Movies' directory. I would then have a separate Plex library for 'Movies-4k' content.
- Update the current 1080p files to 2160p. Then use Plex to create an optimized 1080p version. This would keep both versions in the same Plex library, and I could just select which version to play depending on the device I am on.
I realize option #2 will require additional processing and probably space, since Plex is probably not going to compress the files down to H.265 size. Is there an advantage to one option over the other? Is there another option I am not thinking about?
Any thoughts on how you have your 1080p and 2160p content organized in your Plex server?
-
3 hours ago, Kishin said:
Hello, does anyone has a script to move files between disks ?
I would like to download to my cache then move them to the array where i can continue to seed / hardlink for plex.
Thanks.
In my setup I rely on the nightly mover to move my downloads from the cache to the array. This occurs every day at 04:00.
-
3 minutes ago, binhex said:
yes, dont touch the port, 1337 is pia's choosen port for wireguard, port 1198 is used for openvpn.
Awesome! That's what I assumed, but just wanted to clarify. 😉
Thanks again for all your hard work on this!
-
First off thank you Binhex for all your hard work on keeping all your apps up to date.
I recently switched over to the wireguard setup following A21 in the FAQ doc:
https://github.com/binhex/documentation/blob/master/docker/faq/vpn.mdThe switch was painless and easy to get up and running. You made it very easy to follow. Thank you!
One question I have on changing endpoints, we just need to change the first part of this line, and leave the port at 1337 correct?
Endpoint = nl-amsterdam.privacy.network:1337
When I look at the nextgen Netherlands.ovpn file I see this line:
remote nl-amsterdam.privacy.network 1198
I am assuming the ports are specific to the type of connection, udp or wireguard, and should be left untouched.
-
52 minutes ago, kaiguy said:
For what it’s worth, I have never disabled turbo boost and have not had a hang. Granted though I rarely ever hit anywhere close to my CPU Max. But I have put it through some stress tests though without issue (Folding, for example).
Same here, minus the stress tests. Turbo boost is still active on my system, and has been running fine (touch wood).
-
1 hour ago, boianski said:
any help would be appreciated.
Is everyone having trouble with the WebUI?
Nope. My webui comes up just fine. For reference I am using the latest binhex deployment and nextgen PIA endpoints. My network type is set to 'Bridge' in the binhex-delugevpn container settings.
-
18 minutes ago, worldspawn said:
Hey! That was it, when did that change? The last several versions I've used required the generated password set.
I believe it changed with the new endpoint setup. I was using the generated user and password, but a few weeks ago in this thread we discovered you need to use the main user and password. Hopefully others will see these posts. 😉
-
5 minutes ago, Mor9oth said:
Now i am afraid about this comment:
👇
So is this maybe the reason for no iGPU passthrough and the aspeed Graphics output in my VM instead?
So do i need a graphics card? Any recomendations? Quadro P2000 - or is a gaming GPU better if i want to use it too in a Windows 10 VM?
Hi @Mor9oth. I see in your image it looks like you have an image stating you have the ASRock E3C246D4U type motherboard? If so, and depending on what CPU you are running, you can have a look at this thread regarding the capabilities of that motherboard.
Intel Socket 1151 Motherboards with IPMI AND Support for iGPU
-
4 hours ago, xxDeadbolt said:
It's not the socks credentials you need, it's your main username (pXXXXXXX) & password for PIA.
Awesome! I changed my credentials in the docker setup and it came up perfectly! Thank you for this information!
-
1
-
-
3 minutes ago, Cytomax said:
which ovpn file did you pick (what location)? is it one of the approved locations that it mentions in the log when starting deluge
Yes. I am using CA Toronto. It is one of the locations mentioned in the my legacy log. It doesn't get that far in the nextgen log, but I am assuming it works based on a previous post someone stating it works with nextgen.
Thanks for the follow-up question. I forgot to mention what location I am testing.
-
OK, I have been reading through all the new posts regarding the nextgen setups. I updated my docker which was successful. I can connect successfully using legacy ovpn files from PIA.
Deluge: 2.0.4.dev38
PIA ovpn files: legacy
Port Forward: no
Errors: none; connects fine and everything resumesI downloaded the nextgen files via the instructions form Q19 in the VPN Docket FAQ. I removed the old ovpn and cert files and replaced them with the nextgen files. I also changed the STRICT_PORT_FORWARD variable to 'yes' since it was set to 'no' while using the legacy files.
When I try to start my docker I get the following error in the log:
2020-10-02 10:11:11,741 DEBG 'start-script' stdout output:
Fri Oct 2 10:11:11 2020 AUTH: Received control message: AUTH_FAILEDI saw Q16 in the VPN Docker FAQ which states my VPN_USER and/or VPN_PASS are not correct. I regenerated my username and password from the PIA account site and updated them in the docker settings, but I am still receiving the error. I even failed back to legacy ovpn files, setting STRICT_PORT_FORWARD to 'no', and everything works fine. So I am thinking my user ID and password are good/valid since they work with the legacy files just fine. A couple of questions to those with PIA and have it working with nextgen files:
1. Did you download the NextGen zip from the link labeled 'OpenVPN Configuration Files (Recommended Default)'? The step in Q19 doesn't specify which set of files to use, but I was assuming the top link.
2. Are you using the 'PPTP/L2TP/SOCKS Username and Password' from PIA? I wasn't sure if I should be using a different username and password for VPN_USER and VPN_PASS for the NextGen setup. This is what works with my legacy ovpn files.
3. Are there any other settings you need to change outside of what is stated in Q19 from the VPN Docket FAQ? I am assuming no or else it would be called out in those steps to switch over to NextGen.
I also tested setting STRICT_PORT_FORWARD variable to 'yes' with legacy files, and another test with nextgen files and the setting it to 'no'. Both were still failures and I assumed neither of these were the ideal setup so I am not working on troubleshooting those failures.I am attaching my logs for legacy files port forwarding set to 'no', and nextgen files port forwarding set to 'yes' just if anyone wants to look at anything not stated here in my working and not working logs.
LegacyPortFwdNo.txtNextgenPortFwdYes.txt
So I am not sure if I need something in my PIA account flagged so I can use the NextGen servers or something else with my PIA account not setup correctly. I know I am grasping at straws but I am not sure what is going on here. I can open a ticket with PIA but I wanted to make sure what I am doing is correct before having them check my account on their side.
Any help from anyone would be....well....helpful.
Thanks. -
21 minutes ago, hiddenpcmaster said:
JasonK and Burizado Thank you! I've turned off "strict port forwarding" by saying "no" and now I'm up again! (toronto) Just curious, are you using the nextgen endpoints file or the original? (
I am experiencing a hit on performance thoughbut it's working, After running for awhile it's running much better)Glad you are up and running! I am using the same files I have been using since I set it up back in March. I believe they are the legacy files with the original endpoints. I set it up following Spaceinvader's walkthrough.
-
1
-
-
16 minutes ago, JasonK said:
Im connected to toronto without issue (with strict port forwarding set to off) - torrents happily transferring. have been for a couple days now.
Same here. Same endpoint. Same strict port forwarding setting. And I would add I have not seen a degradation of speed with the setting to 'no'.
-
1
-
-
4 hours ago, JohanSF said:
My binhex-rtorrentvpn using PIA stops and starts every night when the mover runs. For the last couple of months it has been random if it was running when I woke up or not.
For example I just restarted right now and get this:
I can restart the container a minute later and then it will work - it seems completely random and this has been going on for more than a month now. Just haven't had the time to properly deal with it
Now from reading your comments it seems like I'm not the only one.
Yes, this is the same experience I have been having the past few months. After setting 'STRICT_PORT_FORWARD = no' I have not seen issues the past couple of mornings. It seems PIA is aware of the issues and working on a fix. I will run like this until they fix the their 'next gen' servers...or legacy, whichever they are working on.
-
15 minutes ago, sigfreund said:
When Kape Technologies purchased PIA many warned that it was time to find a new VPN provider but I didn't heed the warning but now is the time to look elsewhere and when my contract is up move else where. This is just the tip of the iceburg from what we can expect out of Kape Technologies.
Can you please expand on your statements? Putting a post like this with general statements and opinion does not help anyone in these forums.
-
1
-
-
Yeah, this morning all the CA endpoints were not connecting. I am guessing as @Hoopster said they were probably overrun with everyone jumping to them. I was able to connect to Toronto once I turned off STRICT_PORT_FORWARD. I got the same down speeds as normal.
-
5 minutes ago, binhex said:
maybe the message is finally getting through that they have a problem, its only taken them two weeks! 🙄
Well this is what I sent them. Maybe the possibility of losing customers is a higher priority to them.
"I am using the legacy OVPN connections with port forwarding in a docker on my unRAID server. The community seems to be having major issues with connections to endpoints that support port forwarding. It seems like these issues have started happening in the past recent few weeks. I would like to know if there is a plan to support OVPN connections on your next generation servers? There is a section of your customer base that are using these connections that I fear you will loose if you do not address this concern."
-
6
-
-
What I received back from PIA on the ticket I opened with them. I will give them credit that they seem to be working on the issue.
"Thank you for reaching out here to PIA customer support, I am sorry to hear that you are having issues with using the OpenVPN, please note that we are fully aware of the situation and we are working hard to resolve this the soonest possible, for now, we do not have an ETA for the fix, rest assured that this is acknowledged and being worked on."
-
1
-
-
16 minutes ago, xxDeadbolt said:
I was also told by their chat support that port forwarding would be fully supported on next gen 😕
Edit:
Well that is good they are aware of the issue and seem to be working on fixing it.
I to am experiencing increased issues today, and I opened a ticket with PIA to ask if they will support OVPN connections with their next gen servers.
-
1 hour ago, kingJahfy said:
Changed from CA Toronto to DE Berlin. Issue(s) remains.
5 minutes ago, kingJahfy said:Unfortunately for me - no luck with CA Vancover....😦
......
Stating the obvious --- This frustrating, PIA is very popular and i've had little issue with the service until now
I am not denying you are having issues as seen in your log, but I mentioned previously, and it still remains, CA Toronto works for me. Also not denying there are issues with PIA for others in this forum. I just wanted to confirm that some endpoints people have issues with work for other people. Not sure why.
-
4 minutes ago, binhex said:
ca-montreal is working fine (im using it), others may also work, but as you mentioned until the whole next-gen work is done things could be up and down.
I have been using CA-Toronto for a long time with no issues.
-
1
-
-
13 minutes ago, JasonK said:
Yeah - it's not that - I don't have any backups pulling from the Process folder (or any subfolders). Thanks for the thought tho!
My backups are not on my Process directory either. I believe it is the appdata nightly backup that shuts down all my dockers. I am guessing if it is timed just right (or wrong), it is shut down as they finished downloading but not copied yet.
I also have the issue where the WEBUI does not come up, and I usually need to restart Deluge a couple of times in the morning to get it back. I'm not sure if this might be the cause as well. If downloads are still occurring but Radarr and Sonarr cannot access Deluge (I have seen errors in the Sonarr docker stating it cannot connect to Deluge).
Just my experiences with my setup. I know everyone's setup is a little bit different.
-
1
-
Now from reading your comments it seems like I'm not the only one.
[Support] binhex - DelugeVPN
in Docker Containers
Posted
I have been using PIA consistently for the past 3-5 months on the same endpoint, since I switched to next gen servers and Wireguard setup when PIA ended the life on the old gen servers. (touch wood)