PIA next gen servers change #30
Comments
|
I'm also having this problem, no matter what value I set for |
|
There is a temporary fix for this, you can create your own ovpn config. This is mine for reference $config.ovpn auth-user-pass /config/openvpn/openvpn-credentials.txt ca.rsa and crl.rsa are available from PIA. auth-user-pass shouldnt be nessecary as you already fed it those arguments when you made the container. |
|
Please can you elaborate where those commands should be entered?
|
|
If you download this there is the config for all the different locations along with the encryption files. Make the opvpn point at the ca and crl files as i have done. You need to go into super user and move the files into your config. Remember to change the ovpn config's name into config.ovpn. This needs to be in the config folder where you mount the docker image. Along with the crl and ca files. Aditionally you may need to make a openvpn-credentials.txt file in the same location. containing your PIA user name and pw. Im unsure if the docker image can grab the username and pw from the docker arguments. You just run the docker image lige so and it should work. $ docker run --cap-add=NET_ADMIN -d Hope it helps you guys, and that my typings make sense. |
|
Thank you that helped. I needed to move the |
|
Thats the way I did it however you can pretty much place them wherever as long as you point the .ovpn to them :) Great to hear that it helped |
|
hi, I've implemented a fix, see my comment here #33 |
|
Looks like its working, but seems that there is still problem with port forwarding... Any idea if its my fault or...? I am using guillaumedsde/alpine-qbittorrent-openvpn:development Thanks.. Log below |
|
I'm having the same issues with port forwarding and PIA. Using the development branch as well, but it wasn't working for me in the latest branch either. |
|
I've tried updating the port forwarding script based on haugene's updates in commit 3f4b8ad in the development branch if you can try it out, hopefully its fixed, but its hard to debug without a PIA subscription |
|
I just pulled the new image and tested it but got an error about missing the |
|
exactly same for me |
|
I've submitted a pull request (#37) that fixes port forwarding with PIA, but there are still some errors I'm not sure how to solve. |
|
Thanks I can confirm that I'm unable to get port forwarding to work either. |
|
It will be fixed in the development branch once my pull request is approved. |
|
Thanks for the PR 🙂, I'll look it over this weekend |
|
Thanks! I downloaded the :development build, and whilst the logs are showing no errors (I think), all downloads on qBittorrent start at around 300kbps, then get slower until they are 'stalled'. It doesn't seem to be fixed :( |
|
Could the issue be related to this bit in the log? |
|
Everything is working fine for me now, thanks all :)
It looks like that you have just problem with storage patch(permissions etc.) and qbito cannot write files there... |
|
Thanks Ungrady, which part of the log file suggests this? Qbitt is now saying "Free Space: Unknown" which it never used to. |
You're welcome! :) |
My free space is showing properly: I'm guessing there are permission issues on your host. This won't show in the docker logs necessarily, but if you can't see free space that means the docker can't read the mount locations. Check your mount locations on the host using |
|
Thanks Tony, Something has changed since the latest build. I have reverted to Linuxservers qbittorrent and the downloads work as expected and the free space is shown. However in the development build this isn't the case. I'm not sure it's to do with my setup, but more a recent update. |
|
I am really sorry for bothering you guys again, but is it still working for you? I had to restart server, and I cannot run it anymore Log below |
|
Ok, its because of this |
|
Came across this now that you linked it to my container repo. As you've noticed we're trying to move away from having all the configs checked into the repo. They will be replaced by scripts to download the configs on startup where that is possible, and whatever configs has to be fetched from some logged in pages will be moved out into a separate repo for configs only. There is a pattern here. Any provider that has a I can help out with suggestions and standardizing this if you want this project to piggy-back on the config-fetching as keeping them up to date has proven to be a continuous effort - and I welcome a collaborative effort to fix this problem for both projects. Let me know if anyone is up to the task and I can assist 😄 |
@Ungrady, have you tried changing it from |
|
@gurmukhp I would recommend opening another issue for the problem you're having. Use the bug report form so we can see your environment better. |
|
Use this formatting for the PIA server name. https://www.privateinternetaccess.com/openvpn/openvpn.zip |
lol, its working now many thanks |
|
Hi @haugene thanks for all your efforts, maintaining such a large repo of VPN provider configs is certainly an impressive feat :) . I've been quite busy, but if I'm able to contribute 'upstream' while developing this image, I will certainly submit a PR to your repo :) as for the the issue, it looks like its fixed for @Ungrady so I've merged the fix into master and I'll close the issue, but feel free to reopen you encounter any problems :) |
The latest haugene/docker-transmission-openvpn does not contain the server opvn anymore. As such when running this docker it complains that it can't find the openvpn config file:
ERROR: Could not find OpenVPN configuration "US East" for provider PIA
The changes are referenced in haugene/docker-transmission-openvpn#1334
The text was updated successfully, but these errors were encountered: