Ignored by support / Kaspersky VPN completely broken on routers (OpenVPN & WireGuard)

[Telles0808]

Hey everyone,

I wanted to share a really frustrating experience I’ve been having with Kaspersky’s support and their VPN service lately, mostly to see if anyone else is dealing with the same thing.

The Support Experience Last week, I contacted chat support because the VPN is not working on my router, never worked, I bought a new one and still not working. The agent gave me a 2-day resolution window and promised to email me the support protocol and follow-up updates. None of that happened. They completely ignored the deadline, never sent an email, and left me with zero updates or explanations. It feels like a total lack of respect for the customer's time.

The Technical Issues On top of the bad support, the service itself has serious flaws right now:

• The OpenVPN files are useless: The configuration files Kaspersky provides just don't work with standard router firmware (I'm using an Archer AX53 now). When trying to connect, the status just sits on "Connecting" forever. It seems like their files don't even follow the standard, true compatible router OpenVPN protocol, making them completely ineffective for standard routers.

• No WireGuard alternative: Ever since the changes back in January, WireGuard is nowhere to be found. So when OpenVPN fails, there isn't even a modern alternative to fall back on.

Right now, the VPN is completely unusable at the router level, and support is just missing in action.

Has anyone actually managed to get their OpenVPN config working on a router recently, or is everyone else getting ignored by support too?

[undead_skeleton]

Hi, I had difficulties with the .ovpn file the system automatically created as well. I don't know why, but for some reason it adds the 'udp' prefix to the end of the 'remote' statement, which causes the connection to fail completely. Here is how i managed to get it working on my setup (OpenWRT 24);

- Remove the 'UDP' keyword from the remote statement, and add another line to define the protocol to be used per your taste (i prefer udp for vpn connections)

proto udp
or
proto tcp

- I personally don't like to specify remote nodes as domain names, so i always state them via IP addresses. This is not necessary, but my dns comes up a little late, and i don't like to wait after power outages.

- I don't like the fact that PureVPN servers push 1500 bytes MTU setting for the tunnels, so i configure a pull-filter that filters out the MTU setting pushed by the server. This prevents packet fragmentation.

pull-filter ignore "tun-mtu"
tun-mtu 1420

- Remove the line 'compress' since it's both a security risk and an unnecessary cpu burden. PureVPN servers also push additional compression settings, so you need to deal with that as well with pull-filters.

pull-filter ignore "compress"
pull-filter ignore "comp-lzo"
allow-compression no

- Since i'm using OpenWRT, i need to add the username and password into the config file.

<auth-user-pass>
username provided by Kaspersky
password provided by Kaspersky
</auth-user-pass>

When you're done with these changes, you should have a working OpenVPN configuration file.

Edited June 8 by undead_skeleton

[Telles0808]

Now I can't even download or modify the config of my OpenVPN due to a site error...
polyfills.aea03dd5.js:1  DELETE https://my.kaspersky.com/api/ksec-vpn/creds 555

[leeks]

On 6/8/2026 at 1:21 PM, Telles0808 said:

• The OpenVPN files are useless: The configuration files Kaspersky provides just don't work with standard router firmware (I'm using an Archer AX53 now). When trying to connect, the status just sits on "Connecting" forever. It seems like their files don't even follow the standard, true compatible router OpenVPN protocol, making them completely ineffective for standard routers.

• No WireGuard alternative: Ever since the changes back in January, WireGuard is nowhere to be found. So when OpenVPN fails, there isn't even a modern alternative to fall back on.

 

I have the same exact problem on a TP-Link BE-550 (BE-9300) 

so far support hasn't been supporting a lot. 

[leeks]

On 6/8/2026 at 3:22 PM, undead_skeleton said:

 

Solved following some advice from Undead_skeleton. 

Pasting the last lines from the credentials.ovpn file.

I changed the "Remote" statement by removing "udp" and converting the server name with the resolved IP. In my case it is the belgium server. you can get the ip of any other server just by pinging it. 

I also added 

"pull-filter ignore "tun-mtu"
tun-mtu 1420"

Here are the last lines of configuration for belgium: 

key-direction 1
remote-cert-tls server
cipher AES-256-GCM
route-method exe 
route-delay 0 
route 0.0.0.0 0.0.0.0
script-security 2
remote 154.47.27.97 15021
proto udp
pull-filter ignore "tun-mtu"
tun-mtu 1420
explicit-exit-notify

Getting 700Mbps down - 350Mbps Up - not bad

Someone tell tech support. 

[Danila T.]

Good afternoon.
We’ll look into it. Thank you for bringing this to our attention.

[Telles0808]

The problem was solved by support, but due to 10Mbps of upload and 30Mpbs download limits, I can't use it for homeworking...

[undead_skeleton]

On 6/22/2026 at 4:02 PM, Telles0808 said:

The problem was solved by support, but due to 10Mbps of upload and 30Mpbs download limits, I can't use it for homeworking...

These numbers sound about right for an AX53 which only has 1.0Ghz dual core CPU. You'll need a beefier router to get faster speeds out of a OpenVPN connection. You can always install OpenVPN Connect on your computer and connect from there to get much better speeds if you want to go faster with your current setup.

[Telles0808]

17 minutes ago, undead_skeleton disse:

These numbers sound about right for an AX53 which only has 1.0Ghz dual core CPU. You'll need a beefier router to get faster speeds out of a OpenVPN connection. You can always install OpenVPN Connect on your computer and connect from there to get much better speeds if you want to go faster with your current setup.

I'm using my old VPN service, which achieve 100Mbps through the router VPN for the entire house, instead of configuring each user point... I use TV, laptops, tablets, cameras... So, that's not a problem with my router, it's software limited by Kaspersky.

[undead_skeleton]

2 hours ago, Telles0808 said:

I'm using my old VPN service, which achieve 100Mbps through the router VPN for the entire house, instead of configuring each user point... I use TV, laptops, tablets, cameras... So, that's not a problem with my router, it's software limited by Kaspersky.

You gotta be using WireGuard with your old VPN service then. I suggest you check out this github page where people collectively benchmark their devices' WireGuard performance and gather them together in a list. As you can see there, you should be able to saturate a 100mbps connection with a dual core CPU if you're lucky enough. OpenVPN on the other hand, is way more taxing on the CPU compared to WireGuard so you won't even be getting near those speeds. If i were you, i would try importing my OpenVPN configuration onto a computer running OpenVPN Connect and test it out there before claiming Kaspersky is intentionally limiting my speed.

Edited June 26 by undead_skeleton

[Danila T.]

Hello,

We are pleased to inform you that WireGuard configuration files are now available to you in My Kaspersky.

 

[Telles0808]

On 03/07/2026 at 00:28, Danila T. disse:

Hello,

We are pleased to inform you that WireGuard configuration files are now available to you in My Kaspersky.

 

Hi, thank you for letting me know. I have tried the new protocol and it stuck in the archer AX53 saying the IP is in wrong format.
 

[Telles0808]

I found a solution with Gemini. Add /32 after the IP and it will work fine.

[leeks]

5 hours ago, Telles0808 said:

I found a solution with Gemini. Add /32 after the IP and it will work fine.

I can confirm that this solves the issues. 

Belgian server on wireguard: 697.92 Down - 36.28 Up

https://www.speedtest.net/my-result/d/abed8f2f-fcb3-40f3-9310-d3daa85306f7