Docker-transmission-openvpn: curl encountered an error looking up new port: 56

[kornflex]

Hello,

I'm using this for a while but my synology crash and I have to reinstall :/

So, I'm using docker on synology with PIA provider.

I have created TUN.sh and resolv.conf.

I have this error when lauching the container :

curl encountered an error looking up new port: 56

And close with timeout.

I change the location of PIA server : DE, Spain ( https://www.privateinternetaccess.com/helpdesk/kb/articles/how-do-i-enable-port-forwarding-on-my-vpn ) in order to use the right location with port forwarding but, nothing....

Someone can help me ?

Thank you

[kornflex]

with this error :
curl encountered an error looking up new port: 52

In docker :
curl ifconfig.me return a germany IP

resolv.conf are googles

So, for me, I'm connected, with google DNS.

But I don't have the transmission webUI to confirm :/

[im-mortal]

Experiencing same here. I suspect it's somehow related to the "Next Generation Network" initiative from PIA.
Also see #1357

[ambell7]

FYI I have the same setup and I’m having the same problem.
I contacted PIA support and their response 3 days ago was ...

“The server migration that is happening does not involve changing existing servers to next gen. The current generation of networks will remain as-is until they are retired — the next generation servers are completely separate and exist simultaneously to the legacy servers until they are retired.

When testing this from our end, we were able to confirm that some of the port forwarding enabled servers are not allowing access to the feature as expected. The server and operations teams have been notified and will resolve this as soon as possible. In the meantime, I have been able to confirm that Toronto, Montreal, and France are all still fully functional.”

So they’re saying they do have issues, but not with Toronto, Montreal or France and yet I’m still getting the “error looking up new port: 52” message from this docker image.

[kornflex]

Thnak you very much !

So that's why I don't have the webUI in 9091 port ? Because port forwarding doesn't succeed, it stops here ?

[ambell7]

FYI reply just now from PIA support re this issue:

We sincerely apologize for the inconvenience and issue you are having with manual port forwarding script. We are currently investigating the issue and
rest assured our DevOps are aware and working on the fix for the issue as a priority. As much as we would like to provide estimated time of fix but we do not
have and ETA to share at this time.

For now, we may recommend using PIA Application to ulitise port forwarding while waiting for manual port forwarding to get fixed:

• https://www.privateinternetaccess.com/helpdesk/kb/articles/how-do-i-enable-port-forwarding-on-my-vpn

[ambell7]

kornflex: not sure about the web UI, mine is still working ok - it’s just the port forwarding that’s broken

[kornflex]

OK , I will make a topic on this.

Hope PIA will correct soon this port forward problem !

[plexyprice]

I am having the same issue too keep getting the '56' error code. I have tried 10 different locations thinking something was wrong at the usual sights but to no avail. I think we are just in hurry up and wait mode while PIA figures it out.

[rcdailey]

This issue should not be closed. I'm getting the error as well.

Port forwarding is already activated on this connection, has expired, or you are not connected to a PIA region that supports port forwarding
curl encountered an error looking up new port: 56

[rcdailey]

Can we incorporate this into the container @haugene?

https://github.com/fm407/PIA-NextGen-PortForwarding

[kornflex]

Issue reopenned with the Last comment of rcdailey

[phil-hudson]

+1 here, also PIA.

[code-is-art]

Tried it with different countries but nothing. Any workarounds for this?

[rcdailey]

I ended up switching to a different service. I'm tired of PIA's crap. If you read the PIA reddit, a lot of folks are upset by their next gen server nonsense.

[code-is-art]

I haven't read thru the issue yet but some people seemed to have solved the problem here.

[rcdailey]

Mullvad is what I switched to, it's expensive but great.

[plexyprice]

I have just left my container up and disabled it for use in the UI's of other tools. I forgot about disabling is in one of them and today something showed up in my drives and I was surprised. It auto-got and came through Transmission. The really odd thing is that the Docker Dashboard logs are still showing the error. I restored one of my other services and it is now working fine with that too. I am starting to think that docker is not reading my logs correctly or is caching something somewhere.

[DaftHonk]

Mullvad is what I switched to, it's expensive but great.

Did you need to do anything special to get Mullvad to work with the container? Did you use the built-in profiles or did you use custom?

[rcdailey]

I had to customize the built in one, because of ipv6 issues. This isn't the right place to discuss that, though. Just google/search the issues tab here and you'll find the answer.

[haugene]

Hey guys. I'm closing this and we'll follow up in #1334. A pull-request with the new configs is in place and @mizzi0n is working on getting a PR with the port forwarding. Anyways, the port forwarding is part of the switch to nextgen servers and will be fixed in that issue.