Update all ProtonVPN configs

haugene / vpn-configs-contrib

A collection of configs for various VPN providers

GNU General Public License v3.0

180 stars 744 forks source link

Update all ProtonVPN configs #113

Closed Forage closed 2 years ago

Forage commented 2 years ago

This change uses the original configs as-is except:

Replace "auth-user-pass" with "auth-user-pass /config/openvpn-credentials.txt" to read credentials
Comment out up/down lines

Tor configs are excluded

Breaking change

Proposed change

Update all ProtonVPN configs

Type of change

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New provider (thank you!)
[x] Updated provider (thank you!)
[ ] New feature (which adds functionality to a provider script/repo usage)
[ ] Breaking change (fix/feature causing existing functionality to break)

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue: relates to #
Link to documentation updated (if done separately): https://...

Checklist

[x] The code change is tested and works locally.
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated

Moohan commented 2 years ago

It would be awesome if this could be merged. I've started getting emails from proton saying I'm using a config for a server that is about to get shut down 😟

Hi!

At Proton, we continuously work towards improving and growing our infrastructure. Sometimes this requires retiring certain servers. You recently connected with either your router or some downloaded configuration of OpenVPN and/or StrongSwan to a deprecated server. This server will soon be retired and it will no longer be possible to connect to it. In order to keep enjoying Proton VPN, please download a fresh configuration for your client or router from

https://account.protonvpn.com/downloads#openvpn-configuration-files

Thank you, The Proton Team

Forage commented 2 years ago

Those messages were my motivation to update the configs in the first place. Do note that updating the profiles might still give you the notification in some cases though. I've seen it again with my PC connection as well. So either their message is invalid or not all updated profiles have been made available on the site yet.

haasanen commented 2 years ago

@Forage This new list includes non-p2p configs for ProtonVPN, where as the previous list only included p2p configs.

ProtonVPN Free configs (e.g. nl-free-*). See #105.
Configs for e.g. Vancouver (01-08 and 33-36) and Toronto (49-76) weren't previously provided for Canada as ProtonVPN doesn't want P2P traffic on those servers.

You also have seemed to remove the second certificate in the CA chain. I'm not sure if this will cause problems, but the configuration files downloaded from ProtonVPN has the second certificate. See e.g. diffs of nl-25.protonvpn.net.* files.

I understand that you downloaded "all configurations", but this doesn't provide a curated list of P2P only servers.

Forage commented 2 years ago

The previous list included all configs as well, non-P2P included, I simply reproduced the same (see #30), about to include them or not see #118
I did not remove nor altered more than described, no certificates were touched

If there is an issue with a config than the Proton VPN site provides invalid configs.