MXPI provides UNSUPPORTED version MullvadVPN-2025.6

[Stevo]

Yet 2025.6 is still in their apt repo?

[Stevo]

Hmmm:

Update

We've decided to temporarily mark 2025.6 as supported. 2025.6 is safe to use, and we don't want to alarm people by saying that it is unsupported. We know that some people might experience issues with this release, but those users can safely downgrade back to 2025.5 again.
What will happen now?

Our plan is to pull the 2025.6 release in roughly 24 hours from now. This will allow as many desktop clients as possible to pull down the new information from our API. When we subsequently remove the 2025.6 release from our API the VPN client will no longer warn users that are on 2025.6.

Many users complain that downgrading to a previous release loses all their settings, so don't. Wait for 2025.7.

[siamhie]

Hmmm:

Update

We've decided to temporarily mark 2025.6 as supported. 2025.6 is safe to use, and we don't want to alarm people by saying that it is unsupported. We know that some people might experience issues with this release, but those users can safely downgrade back to 2025.5 again.
What will happen now?

Our plan is to pull the 2025.6 release in roughly 24 hours from now. This will allow as many desktop clients as possible to pull down the new information from our API. When we subsequently remove the 2025.6 release from our API the VPN client will no longer warn users that are on 2025.6.

Many users complain that downgrading to a previous release loses all their settings, so don't. Wait for 2025.7.

That's a big FUBAR if I've ever seen one. Maybe .7 will fix everything.

[bwhawk]

I like this comment:

What should have been done instead was to release 2025.5 as a "new" 2025.7 version, so that everyone would see there was a revert through normal update channels and why, and could immediately update to it. If your release process is so complicated it is difficult to fork off an old version, change its number, and re-release it, thats also an issue.

[Stevo]

I like this comment:

What should have been done instead was to release 2025.5 as a "new" 2025.7 version, so that everyone would see there was a revert through normal update channels and why, and could immediately update to it. If your release process is so complicated it is difficult to fork off an old version, change its number, and re-release it, thats also an issue.

Except it seems to remove the user settings.

Debian and MX have done same kind of thing before, except as "2025.7really2025.5" sort of versioning.

[siamhie]

I like this comment:

What should have been done instead was to release 2025.5 as a "new" 2025.7 version, so that everyone would see there was a revert through normal update channels and why, and could immediately update to it. If your release process is so complicated it is difficult to fork off an old version, change its number, and re-release it, thats also an issue.

Except it seems to remove the user settings.

Debian and MX have done same kind of thing before, except as "2025.7really2025.5" sort of versioning.

I remember this one like it was yesterday (xz-utils 5.6.1+really5.4.5-1)

[Melber]

@Pretty Vacant
Perhaps you could change the thread title now it's clear that mullvad messed up and it's nothing to do with MXPI. Something like "MullvadVPN 2025.6 - unsupported version"

In future also consider generally using less dramatic titles and fewer ALLCAPS. Focus on providing information and asking a civil question (eg. I'm getting this popup/found this website which is saying xxx. What does this mean?) rather than immediately implying someone is up to nefarious ne'er-do-well shenanigans. Being careful is good, being paranoid less so.

[Jerry3904]

Well said.

[Mauser]

https://mullvad.net/en/download/vpn/linux doesn't, but more important:



So we reckon something isn't right.

I have been running Mullvad VPN roughly for the past two years and the correct current version as of now is Mullvad VPN version 2025.6 without issue. In my experience Mullvad VPN has a completely different installation and update processes than other VPN's which I learned from my own experiences with it. There might be a reason why in your case you have such issues. If you downloaded and installed Mullvad VPN from their site you could end up with the issues you are experience. I know this because I did it that way myself at first. The other thing is if you file an issue with Mullvald they won't help you and will claim they don't support MX LINUX but support Debian which is a laughable claim since MX LINUX is based off of Debian. The fix is to uninstall Mullvad VPN and re-install Mullvad VPN only through the MX Package Installer which you will find it in (Popular Applications) then scroll down to Network and click on Network to expand the tree which you will then see Mullvad VPN and put a check in the far left box and then click install in the lower right hand corner. Once finished installing Mullvad VPN, reboot your computer. You will then have Mullvad VPN version 2025.6 which is the latest correct version regardless of what anyone might claim and you will have no errors. If you have any issues go through the settings which you mighty have to chance some only if you have any issues. I recommend you go through the Mullvad VPN settings anyway and set up Mullvad VPN version 2025.6 to your personal preferences. Certain things set a certain way might cause issues as these types of settings are mentioned by Mullvad VPN on what issues they might cause. When ever Mullvad VPN notifies you that you have an update there are two ways to do it: 1) The right way which is by re-installing Mullvad VPN only through the MX Package Installer which will update it. 2) The wrong way is to upgraded through the Mullvad application or the Mullvad site. Let me and others know you end result.