Proton VPN servers marked deprecated

[Forage]

Do you have the latest provider files?

• I have checked that the provider are the latest

Have you tested the provider files?

• I have tested the provider files

Can you create a PR for this config?

• I can create a PR for this

Provider details

I received an e-mail from Proton the other day telling me that I'm using some servers marked deprecated and that they'll be taken offline soon.

The PR I created already before this notification has now been updated with a second round of config updates to fix this issue. Would it be possible to get the PR pulled in?

Fixed by #318

Anything else?

No response

[bramvanderp]

Do you know a good workaround until your PR is merged? I tried cloning your fork in my config folder, but the script overwrites this change and clones the original haugene/vpn-configs-contrib repository instead. Is there another way to load the updated config?

[Forage]

@bramvanderp You can by setting the GITHUB_CONFIG_SOURCE_REPO environment variable to GITHUB_CONFIG_SOURCE_REPO=Forage/vpn-configs-contrib.
See https://github.com/haugene/vpn-configs-contrib/blob/main/CONTRIBUTING.md for more info.

[bramvanderp]

Thanks a lot for the reply. Your comment helped me fix the issue for me!

However, I did have to create my own fork because your suggested changes for the proton servers seem to be outdated again already. I still got the error that the authentication failed at least.

I was able to fix this in my own fork by downloading a new version from https://account.protonvpn.com/downloads and updating the config with the IPs I found in the file I downloaded (see bramvanderp@9bcdeb5)

Or does Proton link servers/ports to specific user accounts maybe?

Anyway, thanks for the help!