This repository is a support-repo for: https://github.com/haugene/docker-transmission-openvpn It is an effort to separate the development and maintenance of that project and the VPN configs it relies on.
The split is thought to have multiple benefits. It will reduce noice in the main project and hopefully create a meaningful separation that can make it easier to test changes in configs and contribute to keep the providers up to date.
If you have a .ovpn file from your VPN provider and you want to use it with this project
then CONTRIBUTING.md is the guide you're looking for.
The main project currently only support OpenVPN but we're hoping to support Wireguard as well. To plan for that we are separating configs here based on technology and then provider.
So the structure becomes:
<vpn-technology>/<provider>/<bundle-name>/configs.ovpn
For example:
openvpn/mullvad/tcp80/mullvad_ch_tcp80.ovpn
| Provider Folder | Provider Status | Configs tested | Successful |
|---|---|---|---|
| anonine | π (0%) | 10 | 0 |
| anonvpn | π (0%) | 8 | 0 |
| blackvpn | π (0%) | 10 | 0 |
| btguard | π― | 2 | 2 |
| bulletvpn | π (70%) | 10 | 7 |
| cryptostorm | π― | 10 | 10 |
| expressvpn | β (90%) | 10 | 9 |
| fastestvpn | π (80%) | 10 | 8 |
| freevpn | π (0%) | 10 | 0 |
| froot | π― | 7 | 7 |
| frostvpn | π (0%) | 10 | 0 |
| getflix | π (80%) | 10 | 8 |
| ghostpath | π (70%) | 10 | 7 |
| giganews | π― | 10 | 10 |
| goosevpn | 10 | 6 | |
| hideme | π (80%) | 10 | 8 |
| hotspotshield | π― | 10 | 10 |
| integrityvpn | π― | 1 | 1 |
| ironsocket | π (80%) | 10 | 8 |
| ivacy | β (90%) | 10 | 9 |
| ivpn | π― | 10 | 10 |
| mullvad | π (70%) | 10 | 7 |
| octanevpn | π (70%) | 10 | 7 |
| ovpn | π (80%) | 10 | 8 |
| privado | π (70%) | 10 | 7 |
| privatevpn | π (80%) | 10 | 8 |
| protonvpn | π― | 10 | 10 |
| proxpn | π (0%) | 10 | 0 |
| purevpn | π― | 10 | 10 |
| ra4w | π (0%) | 10 | 0 |
| safervpn | 10 | 5 | |
| slickvpn | π (70%) | 10 | 7 |
| slickvpncore | β (90%) | 10 | 9 |
| smartdnsproxy | π (80%) | 10 | 8 |
| smartvpn | 3 | 1 | |
| surfshark | π― | 10 | 10 |
| tiger | π (0%) | 10 | 0 |
| torguard | π (70%) | 10 | 7 |
| trustzone | π (0%) | 10 | 0 |
| tunnelbear | π (80%) | 10 | 8 |
| vpnac | π― | 10 | 10 |
| vpnarea | 10 | 6 | |
| vpnbook | π― | 9 | 9 |
| vpnfacile | π (0%) | 10 | 0 |
| vpnht | π (0%) | 10 | 0 |
| vpntunnel | π (80%) | 10 | 8 |
| vpnunlimited | π (87%) | 77 | 67 |
| wevpn | π― | 10 | 10 |
| windscribe | 10 | 6 | |
| zoogvpn | π (0%) | 10 | 0 |
There is a work in progress to automate periodic checks of all our configs. The table above is the current output of that work. As we can't automate this completely without having an active subscription to every supported provider we do basic connectivity tests to assert the overall health of the providers and config bundles.
Some testing is better than none, and we believe that this will help maintain and manage providers going forward.
If you have Python experience and want to contribute - you're more than welcome! Create an issue and we can start a discussion on what the next steps are. They're just runnung locally for now, but we plan to move them into a CI. Probably GitHub workflows.
For now the tests are run in a simple setup with docker-compose. We throw the configs from this repo into
the main project container, mount the test script and override the container command.
The results are written to a data folder mounted in the current location. Results will be owned by root for now,
we'll address that later. For now sudo chown is your friend.
Start it locally by running:
docker-compose -f configtest-compose.yml up
Then you can generate the markdown table by running:
python3 generate_results_md_table.py data/result1234.json >> README.md
Or something similar depending on the data file you want to use.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent