DNS Issue RUSSIA

justSomeGuy

Freshly Joined Member
Since about 2 weeks its not possible to use the Perfect-Privacy VPN when connecting with a russian ISP.

The connection to the PP Servers works without any issues and the connection is marked as "green" / "successfull" but then nothing else is working.
Every website i try to open gets me: Hmm. We’re having trouble finding that site.
Ping command in commandline also indicates DNS issue.
I tried different Networks and all have the same problem.

In between I have been few days in another country and with the same setup everything worked fine.

After checking the forum i saw that some users report issues when using russian VPN Server as first Hop.

I also tried to use aswell PP DNS as Custom DNS Server but nothing resolves the problem.
I also tried to connect to a lot of different Servers in different countries but all have the same problem.

It looks like all VPN connections are made useless by somehow killing all DNS when using the VPN.

As soon as I turn off the VPN everything works blazing fast.

I tried to setup different Stealth methods but without any success. (I am on linux)

🔐 Enter Auth Password: ************
2024-09-09 11:19:00 us=664100 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2024-09-09 11:19:00 us=665432 No valid translation found for TLS cipher 'TLS_CHACHA20_POLY1305_SHA256'
2024-09-09 11:19:00 us=665442 No valid translation found for TLS cipher 'TLS_AES_256_GCM_SHA384'
2024-09-09 11:19:00 us=666560 Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
2024-09-09 11:19:00 us=666575 Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
2024-09-09 11:19:00 us=666581 Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
2024-09-09 11:19:00 us=666586 Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
2024-09-09 11:19:00 us=666636 Control Channel MTU parms [ L:1655 D:1154 EF:96 EB:0 ET:0 EL:3 ]
2024-09-09 11:19:00 us=666653 Data Channel MTU parms [ L:1655 D:1450 EF:123 EB:411 ET:32 EL:3 ]
2024-09-09 11:19:00 us=666667 Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1583,tun-mtu 1532,proto TCPv4_CLIENT,cipher AES-256-GCM,auth [null-digest],keysize 256,key-method 2,tls-client'
2024-09-09 11:19:00 us=666682 Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1583,tun-mtu 1532,proto TCPv4_SERVER,cipher AES-256-GCM,auth [null-digest],keysize 256,key-method 2,tls-server'
2024-09-09 11:19:00 us=666691 TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:10000
2024-09-09 11:19:00 us=666712 Socket Buffers: R=[131072->131072] S=[16384->16384]
2024-09-09 11:19:00 us=666717 Attempting to establish TCP connection with [AF_INET]127.0.0.1:10000 [nonblock]
2024-09-09 11:19:00 us=666811 TCP connection established with [AF_INET]127.0.0.1:10000
2024-09-09 11:19:00 us=666819 TCP_CLIENT link local: (not bound)
2024-09-09 11:19:00 us=666823 TCP_CLIENT link remote: [AF_INET]127.0.0.1:10000
2024-09-09 11:19:00 us=919402 Connection reset, restarting [0]
2024-09-09 11:19:00 us=919599 TCP/UDP: Closing socket
2024-09-09 11:19:00 us=919783 SIGUSR1[soft,connection-reset] received, process restarting
2024-09-09 11:19:00 us=919835 Restart pause, 5 second(s)
...

has same DNS issue as soon as I am connected to the VPN

🔐 Enter Auth Password: ************
2024-09-09 11:16:05 us=65909 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
2024-09-09 11:16:05 us=67789 No valid translation found for TLS cipher 'TLS_CHACHA20_POLY1305_SHA256'
2024-09-09 11:16:05 us=67822 No valid translation found for TLS cipher 'TLS_AES_256_GCM_SHA384'
2024-09-09 11:16:05 us=73319 Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
2024-09-09 11:16:05 us=73353 Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
2024-09-09 11:16:05 us=73364 Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
2024-09-09 11:16:05 us=73375 Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
2024-09-09 11:16:05 us=73492 Control Channel MTU parms [ L:1655 D:1154 EF:96 EB:0 ET:0 EL:3 ]
2024-09-09 11:16:05 us=73528 Data Channel MTU parms [ L:1655 D:1450 EF:123 EB:411 ET:32 EL:3 ]
2024-09-09 11:16:05 us=73559 Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1583,tun-mtu 1532,proto TCPv4_CLIENT,cipher AES-256-GCM,auth [null-digest],keysize 256,key-method 2,tls-client'
2024-09-09 11:16:05 us=73568 Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1583,tun-mtu 1532,proto TCPv4_SERVER,cipher AES-256-GCM,auth [null-digest],keysize 256,key-method 2,tls-server'
2024-09-09 11:16:05 us=73591 TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:10000
2024-09-09 11:16:05 us=73638 Socket Buffers: R=[131072->131072] S=[16384->16384]
2024-09-09 11:16:05 us=73648 Attempting to establish TCP connection with [AF_INET]127.0.0.1:10000 [nonblock]
2024-09-09 11:16:05 us=73815 TCP connection established with [AF_INET]127.0.0.1:10000
2024-09-09 11:16:05 us=162121 TCP_CLIENT link local: (not bound)
2024-09-09 11:16:05 us=162288 TCP_CLIENT link remote: [AF_INET]127.0.0.1:10000
2024-09-09 11:16:05 us=318160 Connection reset, restarting [0]
2024-09-09 11:16:05 us=318375 TCP/UDP: Closing socket
2024-09-09 11:16:05 us=318522 SIGUSR1[soft,connection-reset] received, process restarting
2024-09-09 11:16:05 us=318585 Restart pause, 5 second(s)
...

I appreciate any help to get the vpn running and working again.

Thank you in advance!
 
In between I have been few days in another country and with the same setup everything worked fine.
I wonder why another country makes a difference.

As far as I can observe, this problem is only related to the Russian servers. It seems that Russian traffic is blocked for political reasons.
 
it indeed seems like russian authorities drop all traffic when connected to the VPN service.
for example for mullvad I cant even open their website.
With PP I can access the website, connect to the vpn server but then have the above described issue.
There is planet VPN on android which many russians are using to for example access instagram, this is still working.
I hope somebody of the PP-team can investigate the issue and provide me with an solution.
I wonder why another country makes a difference.

As far as I can observe, this problem is only related to the Russian servers. It seems that Russian traffic is blocked for political reasons.
 
I think your ISP is blocking VPN traffic and there is nothing we can do if all obfuscation methods don't work.
I saw your post in the other thread. the connection to the PP vpn servers works for me too but then the when trying to access any website it isnt working.

Now I just bought a mullvad subscription (needed to use proxies to access their website and download the client ((both works for PP without proxy))
And now I am conntected to mullvad vpn without any problems.

So there need to be something you can do since mullvad's domain even is blocked but for you its just that the DNS isnt working when I am connected to any of your servers.
 
I think your ISP is blocking VPN traffic
I saw your post in the other thread. the connection to the PP vpn servers works for me too but then the when trying to access any website it isnt working.
This is similar to the multihop scenario.

Whether I use a Russian server and create a 2nd hop behind it, or just want to access a website with the Russian VPN, in both cases it doesn't work.

Saying that the ISP blocks VPN traffic doesn't seem to be true, because we can connect to all servers, but with a Russian VPN you can't access the Internet.

So in this case there is something odd with the Russian servers that needs to be fixed.
 
So in this case there is something odd with the Russian servers that needs to be fixed.
But I can write something in the forum with the Russian server and access all other websites. That shouldn't work if the server was the reason.

1725963397149.png

Write a ticket. This may enable the technicians to find out what the reason is on your side.
 
Due to bad experiences with tickets, as I don't get response to them, so I write it here.

I've just tried a Russian server (single hop) and this happened to me:
Moscow2: It was not possible to open web pages.
Moscow1: The web page could be opened, but after a few seconds the VPN server automatically disconnected. Here is my connection log:
My ISP is Vodafone.
 
Due to bad experiences with tickets, as I don't get response to them, so I write it here.

I've just tried a Russian server (single hop) and this happened to me:
Moscow2: It was not possible to open web pages.
Moscow1: The web page could be opened, but after a few seconds the VPN server automatically disconnected. Here is my connection log:
My ISP is Vodafone.
I am telling you thats russian ISPs that block it.
When connecting from any russian ISP to any PP server nothing is working.
I get connection to the server but then no websites are working anymore. Not even if I try to open a website by its ip.

Then I went to try mullvard (I have been PP user since many years) and with mullvard everything is working fine with any of their servers.

But with clear russian IP mullvard website is blocked where as PP is working.

So their client seems to do better in obfuscating the traffic so that its not detected as vpn traffic and still usable.
 
So what's the takeaway here? Does PP need to switch to new IP addresses to solve this issue?
I believe the solution lies in obfuscation.
Russian goverment invests more than 500 Mio Eur till 2030 to detect and block VPN traffic.
It looks like that PP isnt interested in solving this issue which means for me after almost 10 years of using PP I have to use another provider 😥
 
Back
Top