Jump to content
Not connected, Your IP: 34.201.121.213
TheDieselBoiler

Ubuntu 16.04 Xenial won't connect via network manager

Recommended Posts

Hello,

I have recently encountered problems with connecting to AirVPN via the network manager in ubuntu 16.04.

I followed the guide correctly and the gnome network manager plugin is installed and works correctly.

I have downloaded the correct configs and separate files, and everything is configured to work correctly.

When I use firefox or even ping www.google.com i get no response and firefox doesnt connect, even though i get a message that the VPN connection is established successfully.

Any fix for this? Could this be related to DNS issues or something ?

Share this post


Link to post

This fixed my problem too. But I am very confused. The .ovpn profile was working with one ISP for several days then today would not work with a different ISP until I enabled "LZO data compression" (I am using wireless hotspots). Why would LZO compression be required with one ISP and not another - could there be any reason, or did something change on the AirVPN side?

Share this post


Link to post

did something change on the AirVPN side?

 

No.


Four simple things:
There's a guide to AirVPN. Before you ask questions, take 30 minutes of your time to go through it.

Amazon IPs are not dangerous here. It's the fallback DNS.
Running TOR exits is discouraged. They're subject to restrictions on the internet and harm all AirVPN users.

Furthermore, I propose that your paranoia is to be destroyed. If you overdo privacy, you'll be unique among the mass again.

 

XMPP: gigan3rd@xmpp.airvpn.org or join our lounge@conference.xmpp.airvpn.org

Share this post


Link to post

There's something I don't understand...

 

Isn't the problem with the .ovpn files you provide? comp-lzo is set to "no" although it is activated on the server. Shouldn't you set it to "yes"?

 

It seems the only problem in Network Manager is that it doesn't tell the user there is a problem with the config. I had this issue on my new pc with a fresh 16.04 install, although I had no issue with my older pc which was upgraded to 16.04, so I had a hard time figuring where the problem was...

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image

×
×
  • Create New...