proxy-nl.privateinternetaccess.com will not work with qbittorent for me anymore using socks5 proxy.I use ip addresses that pia uses on this webpage.I change them several times a day. http://tejji.com/ip/url-to-ip-address.aspx?domain=proxy-nl.privateinternetaccess.com Anyone else have the same problem.I tried to change my password to no avail
Just yesterday I have asked about using the proxy for the torrent account, and the support replied with:
The proxy contains no inherit encryption, and as such we would expect your Internet Service provider to be able to track your activity. The only purpose of the Proxy is to make websites believe you are connecting from somewhere else, but the lack of an encryption means it is pretty easy for your ISP to see what you are using it for. We recommend the VPN for this purpose.
Then the traffic is not clear, and your ISP can only see traffic addressed to an IP for proxy-nl.privateinternetaccess.com (there are several) - but not read the packet contents.
This is similar to you using a VPN. The traffic is encrypted, but your ISP can still see that the packets are addressed to the VPN gateway - but not read the packet contents.
The PIA proxy works well with Deluge - never had a problem and my daemon is always running.
Same issue on qbittorrent. SOCKS5 proxy stopped working a couple days ago.
I get errors such as: qBittorrent failed listening on interface 0.0.0.0 port: SOCKS5/32058. Reason: Access is denied. qBittorrent
failed listening on interface 0.0.0.0 port: SOCKS5/32058. Reason: A
connection attempt failed because the connected party did not properly
respond after a period of time, or established connection failed because
connected host has failed to respond.
I've tried several ports and also IP addresses instead of the proxy-nl.privateinternetaccess.com address.
Yea socks5 is a no go for me right now. going nuts here tryin to fix it
Okay, so its not just me having this problem. The damn thing seems to be intermittent. Connect and disconnect, I'll have to search through the forums and see if someone has found a solution.
yes, it seems that a lot of their socks servers have gone offline or are having major problems and their DNS resolution isn't up to date with this so one resolves the proxy name to a bad ip address many times. This has happened in the past week or 2 I think.
Hey everyone, I'm very sorry for the trouble here. We're aware of the
troubles with this right now, and are working with our DC partners to
resolve these issues. We'll continue working with them until it's
resolved and running at full efficiency. For now I'd need to recommend using the VPN instead.
@dingho I'm sorry about this, I'll make sure the whole team's aware of this so we can provide the right information.
Hey everyone, I'm very sorry for the trouble here. We're aware of the
troubles with this right now, and are working with our DC partners to
resolve these issues.
Thanks for letting us know of the issue. Appreciate the update.
I use the proxy with JDownloader and for the last few days, I have been getting errors in JD when trying to download from different hosts. Many downloads take a really long time to start if at all.
I actually use the proxy way more than the VPN which is slow as molasses covered shit in winter. These issues with the proxy are not making me want to stay with PIA. TorGuard has a proxy service that is many times better than PIA's and I am thinking about jumping ship.
Comments
Because PIA is a VPN provider and not a proxy service.
http://tejji.com/ip/url-to-ip-address.aspx?domain=proxy-nl.privateinternetaccess.com
Anyone else have the same problem.I tried to change my password to no avail
In other words the traffic is clear, and I I drawn in this sketch: https://www.dropbox.com/s/1pet3ur7othv9kl/schema%20proxy%20PIA%20clear
Set Inbound Encryption to Forced.
Set Outbound Encryption to Forced.
Set Encryption Level to Full Stream.
Tick the box "Encrypt entire stream".
Then the traffic is not clear, and your ISP can only see traffic addressed to an IP for proxy-nl.privateinternetaccess.com (there are several) - but not read the packet contents.
This is similar to you using a VPN. The traffic is encrypted, but your ISP can still see that the packets are addressed to the VPN gateway - but not read the packet contents.
The PIA proxy works well with Deluge - never had a problem and my daemon is always running.
I get errors such as:
qBittorrent failed listening on interface 0.0.0.0 port: SOCKS5/32058. Reason: Access is denied.
qBittorrent failed listening on interface 0.0.0.0 port: SOCKS5/32058. Reason: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
I've tried several ports and also IP addresses instead of the proxy-nl.privateinternetaccess.com address.
"Error: The network connection was aborted by the local system"
"Error: The I/O operation has been aborted because of either a thread exit or an application"
@dingho I'm sorry about this, I'll make sure the whole team's aware of this so we can provide the right information.
Regards,
I actually use the proxy way more than the VPN which is slow as molasses covered shit in winter. These issues with the proxy are not making me want to stay with PIA. TorGuard has a proxy service that is many times better than PIA's and I am thinking about jumping ship.