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."

20 minutes ago, Burizado said:

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."

maybe the message is finally getting through that they have a problem, its only taken them two weeks! 🙄

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."

Edited September 10, 20205 yr by Burizado

For those that have not yet been able to connect rest assured you can, it took me many tries but I was finally able to connect to Spain my normal go to is Toronto comparing speeds its less than half with the Spain server but still way faster than just not using port forwarding. I hope this helps some of you who might be discouraged.

 

As some of you I still have 6 months left with PIA and have been them for years now but I will also look at alternatives if this is not taken care.

I am currently connected to the Czech Republic endpoint with port forwarding enabled. None of the Canadian ones were working for me even though Vancouver and Toronto both worked earlier this week.  Perhaps it is a timing issue and too many connection requests were being made for those endpoints.

I managed to connect to Spain. Took 5 container restarts before it finally connected.

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.

Just submitted a support ticket to PIA.  Everyone put in a ticket and maybe we won't have to switch providers!

2 hours ago, Burizado said:

I was able to connect to Toronto once I turned off STRICT_PORT_FORWARD

Thanks for the suggestion. (for those that do not know where this is, it is under "EDIT", then change the STRICT_PORT_FORWARDING line to say "no" and your all set. I would restart all your relevant containers.

It is not an ideal solution, but at least I can now (after almost a week) get back on!

16 hours ago, wgstarks said:

Doesn’t work for me.

Seems to be a tossup. Worked fine for me. I think their servers are just going nuts right now.

11 hours ago, BigDaddyNehi said:

Just submitted a support ticket to PIA.  Everyone put in a ticket and maybe we won't have to switch providers!

Yes agree just got a reply

Quote

 

Thank you for contacting PIA Support.

I am sorry to hear that you cannot connect to PIA's port-enabled Next-Generation server.

Our DevOps team is still on the process of updating the Port-Forwarding API to connect to the Next-Generation server.  Unfortunately, we don't have an ETA about this.

We apologize for the inconvenience.

 

 

PSA if you're using Privoxy:

 

My Deluge VPN container has been mis-behaving, potentially since the last update.  I started regularly receiving the "Maximum number of open connections reached" message when connecting to the Deluge.  This is always something that has happened for me from time to time, but usually took a couple of days of uptime. Since the last update, it started happening within an hour or so.

 

Netstat shows a very large number of connections from the internet to the Privoxy proxy port.

 

I have confirmed that it's possible to connect to Privoxy from the internet e.g. Privoxy is working as an open proxy.

 

Not sure if something has changed but I thought that I would share with you all.

 

It should easy enough to fix through the Firewall.

Edited September 11, 20205 yr by JDBall

39 minutes ago, JDBall said:

I have confirmed that it's possible to connect to Privoxy from the internet

only if you port forward on your router, or if your vpn allows you to, setup a port forward that points at privoxy port 8118 (not required and not recommended!).

39 minutes ago, JDBall said:

Privoxy is working as an open proxy.

privoxy has always been a proxy without authentication, this has been the state since day 1 of this image, if you decide to port forward to it then it's your lookout.

Edited September 11, 20205 yr by binhex

Thanks for quick response.

 

Yes, I realised after posting that Port Forwarding was enabled in my config and once disabled I can no longer connect from the outside  I've been running this container and config for several years but haven't had this problem before - strange.

1 minute ago, JDBall said:

I've been running this container and config for several years but haven't had this problem before - strange.

perhaps the port scanning bots only just around to finding out about your open proxy :-), lesson learned is dont port forward to privoxy on your router 🙂

I mean that I had changed the container variable STRICT_PORT_FORWARDING to no which I thought had fixed the issue as I wasn't seeing any remote connections to Privoxy.  I've just tested from outside of my network and can stil connect.

 

My Firewall isn't port-forwarding to Privoxy - the inbound connections are coming over the VPN.

4 minutes ago, JDBall said:

I've just tested from outside of my network and can stil connect.

how have you tested this outside?, are you connecting to your vpn providers external ip address then or your isp external ip address?

Yes, using the Public IP Address assigned by my VPN provider as the Proxy IP Address, Port 8118, on my Laptop when tethered to my phone works.

5 minutes ago, JDBall said:

Yes, using the Public IP Address assigned by my VPN provider as the Proxy IP Address, Port 8118, on my Laptop when tethered to my phone works.

if you set STRICT_PORT_FORWARDING to no then no port assignment will be made so its technically impossible for incoming connections to be established (over the vpn that is), and further more, even if port forwarding was enabled, pia doesnt allow you to set the port forward assignment so it will be random and will not be in the 8xxx range.

 

edit - i suspect your laptop is not using your tether, have you got wifi still enabled on your laptop?, if so it will connect internally and thus allow you to see the proxy.

Edited September 11, 20205 yr by binhex

I'm using iPredator not PIA.

Just now, JDBall said:

I'm using iPredator not PIA.

ok in that case the STRICT_PORT_FORWARDING does nothing, this is for pia users only, check ipredator portal and see if you have a incoming port defined for 8118 (or whatever port delugevpn has set for privoxy).

There's no options at all in their portal.  It's an extremely bare bones solution only having infrastructure in Sweeden.

 

I tried PIA recently as an alternative but the performance from Singapore wasn't great.

 

I wonder if iPredator has changed something on their side?

A quick google around iPredator and i see no mention whatsoever of configuring or support of port forwarding, so i can only assume iPredator does not support it, thus whatever it is you are connecting to is NOT privoxy, try this:-

 

edit the container and set ENABLE_PRIVOXY to 'no' apply change, can you still connect to the proxy?, if so then its most likely you are connecting to the iPredator proxy server (assuming they run one).

Edited September 11, 20205 yr by binhex

So set to No I can't connect, set to yes I can everytime.

 

Netstat from the container console shows the IP Address from my mobile provider connected to 8118.

 

The 404 error pages returned are from Privoxy.

 

Happy to share the IP Address with you via PM if you want to try connecting yourself?

Just now, JDBall said:

Happy to share the IP Address with you via PM if you want to try connecting yourself?

sure, go for it.