This message was deleted.

cc @fancy-wire-61616

@brash-optician-30337 We have not seen any issues with any specific VPN. Would you be able to point to some sessions and participant identities who is having trouble. October 7th does not line up with anything on our side. Maybe, there was a Chrome release or NordVPN extension update around that time? Could you please share details of extensions/VPNs you are testing the connection tester? We will try that also. One potential issue with VPNs is MTU. Typically, MTU is 1300 for VPNs.

libwebrtc

uses 1200 byte packets primarily for that reason. Maybe, VPNs are using smaller MTUs under some conditions?

I use NordVPN as well and have no problems connecting to Cloud. Do you know which NordVPN locations that users have had issues with? Perhaps we could try it ourselves

I think germany was one

yes, Germany was one of the countries, when performing some connection tests we could see results as follows:

Connecting to signal connection via WebSocket

Connected to server, version 1.5.0.

Establishing WebRTC connection

udp 142.132.215.106:59512 host

tcp 142.132.215.106:7881 host (passive)

tcp [2a01:4f8:262:53c1::2]:7881 host (passive)

udp [2a01:4f8:262:53c1::2]:52145 host

udp 172.17.0.1:59462 host (private)

tcp 172.17.0.1:7881 host (private)

udp 172.25.0.1:50471 host (private)

tcp 172.25.0.1:7881 host (private)

WARNING: error with ICE candidate: 600 Address not associated with the desired network interface. turns:<http://livekit-turn.decentral.io:443?transport=tcp|livekit-turn.decentral.io:443?transport=tcp>

WARNING: error with ICE candidate: 701 turns:<http://livekit-turn.decentral.io:443?transport=tcp|livekit-turn.decentral.io:443?transport=tcp>

Can connect via TURN

ERROR: could not establish pc connection

Can publish audio

published 19 audio packets

Can publish video

ERROR: Requested device not found

Resuming connection after interruption

PASS

oh, this is self-hosted LiveKit?

no, sorry, @brash-optician-30337 shared the one with the self-hosted one, but we also tried with cloud

thanks! ok we have different errors now.. this is Nord Chrome extension?

don't worry about the video part though, the token was restricted to audio only

Hey @dry-elephant-14928 I'm running 3 LiveKit servers for livekit.decentral.io and livekit-turn.decentral.io for the last year, configuration wasn't changed for a long time and only few weeks ago some users started receiving such warns

WARNING: error with ICE candidate: 600 Address not associated with the desired network interface. turns:<http://livekit-turn.decentral.io:443?transport=tcp|livekit-turn.decentral.io:443?transport=tcp>

WARNING: error with ICE candidate: 701 turns:<http://livekit-turn.decentral.io:443?transport=tcp|livekit-turn.decentral.io:443?transport=tcp>

Where is the problem? In configuration? How to fix it?

interesting.. I'm able to repro this going through Germany VPN. Tried a few other NordVPN regions and they appear to work fine. I'm not sure what's unique about their server in Germany..

I'm also not sure where the failure is exactly, because ICE seems to be successful right?

It's unclear why audio couldn't be sent.. it's possible the VPN is filtering them out.. or some sort of MTU issues as Raja mentioned.

Can you try ping with different sizes and check if there is a cut off point?

I don't think so because it's a browser extension 😢

NordVPN Chrome extension says this

• Protection from IP leaks
NordVPN's VPN proxy extension will disable Chrome's WebRTC protocol to prevent your IP address from being leaked.

Do you have to enable WebRTC explicitly?

@great-nail-93964 can you check this?

Oh, currently I don't have NordVPN on my laptop. Let me ask someone to share creds.

Interesting that it's specific to Germany for you. I've had this issue with virtually anywhere I connect (Canada, Mexico, etc) with their browser plug-in.

hmm..maybe something's still changed there

Looks like I was removed from this slack, but wanted to check if there were any updates here.

Hey @creamy-kitchen-7734, I'm not sure what happened with Slack, we didn't remove anyone. Re: this issue, we do not yet have an update. We need to understand better how Nord is handling the blocks in the new version

Thank you for the response @dry-elephant-14928. Couple things to mention; This is not exclusive to Nord. We have had reports of the same issue using Express, Titan, and PIA. I was able to connect using Nord for the first time since (roughly) October 7th yesterday but others are still experiencing the issue.