Skip to content

PrivateVPN: Update SE Stockholm IP#356

Open
jucor wants to merge 1 commit into
haugene:mainfrom
jucor:patch-1
Open

PrivateVPN: Update SE Stockholm IP#356
jucor wants to merge 1 commit into
haugene:mainfrom
jucor:patch-1

Conversation

@jucor
Copy link
Copy Markdown

@jucor jucor commented Dec 7, 2025

Breaking change

<placeholder>

Proposed change

Previous IP doesn't respond anymore. 
Replacing with one obtained from https://privatevpn.com/serverlist which indicates 
hostname `se-sto.pvdata.host` which resolves into various `45.130.87.XX` (including `.16`), 
not all of which are responsive. `45.130.87.16` is one of those that work.

Type of change

  • Bugfix (non-breaking change which fixes an issue)
  • New provider (thank you!)
  • 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

I used to make do with local modifications to the configuration, but since post-#2953 versions will overwwrite them, I figured it's time to make a PR :)

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

Checklist

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

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

  • Documentation added/updated

Previous IP doesn't respond anymore. Replacing with one  obtained from https://privatevpn.com/serverlist which indicates hostname `se-sto.pvdata.host` which resolves into various `45.130.87.XX` (including `.16`), not all of which are responsive. `45.130.87.16` is one of those that work.
@haugene
Copy link
Copy Markdown
Owner

haugene commented Apr 12, 2026

Hey! 👋 Thanks for contributing and sorry about the late reply.
It seems that all privatevpn configs have been updated since you opened this PR.

Please let me know if you still have issues or I will assume that it is now resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants