[05:19] <emma> I have a VPN (private internet access) but I don't always use it.  But suddenly I cannot connect to any webpage UNLESS i am connected to the VPN.
[05:20] <emma> I think it might be some DNS setting but I'm not sure nor sure how to change it.
[12:19] <geodb27_> People : hi !
[12:42] <BluesKaj> Hey folks
[13:35] <emma> I have a VPN (private internet access) but I don't always use it.  But suddenly I cannot connect to any webpage UNLESS i am connected to the VPN.
[13:35] <emma> I think it might be some DNS setting but I'm not sure nor sure how to change it.
[13:42] <diogenes_> emma, try private window
[13:44] <BluesKaj> emma, I use PIA and never encountered that...which browser?
[13:49] <BluesKaj> emma think the PIA app has a setting which makes it default at startup , maybe that's been enabled somehow
[14:02]  * BluesKaj doesn't use the PIA provied GUI , I just use the config  files and connect the vpn from the konsole
[14:02] <BluesKaj> provided
[14:06] <aurelia> ciao
[14:22] <emma> BluesKaj: firefox.
[14:23] <BluesKaj> emma, using The PIA GUI to connect or??
[14:23] <emma> yeah
[14:23] <emma> I think it is a DNS problem
[14:23] <BluesKaj> ok , look in the GUI to make sure it isn't setup to autostart on boot
[14:25] <emma> it is set to auto-connect on launch
[14:26] <emma> and start application at login
[14:26] <BluesKaj> ok, think that's the culprit , it's overriding your network-manager setting
[14:27] <BluesKaj> set the app to manual start
[14:29] <BluesKaj> you may need to run sudo systemctl enable network-manager then sudo systemctl  start network-manager
[14:29] <BluesKaj> and perhaps a reboot
[14:30] <emma> Yeah i set the PIA to manual start.  Then I used sudo service network-manager restart
[14:31] <emma> now PIA is not connected (but the PIA app is still running) and firefox cannot connect to any web pages.
[14:31] <emma> interestingly ssh is still working which is how I am chatting now.
[14:34] <emma> BluesKaj: you think it needs to reboot the machine?
[14:36] <BluesKaj> open system monitor in the Kmenu and in the search type pia, right click on pia and choose send signal, then choose terminate or kill , then try your browser again
[14:36] <BluesKaj>  if that doesn't work try a reboot
[14:36] <BluesKaj> emma,^
[14:37] <emma> ok
[14:38] <emma> hm, i don't have that right click option.
[14:38] <emma> to send a signal.
[14:38] <emma> Im using kubuntu tho
[14:39] <emma> it's just add to pannel, pin to task manager, that sort of thing.
[14:41] <emma> I'll be back when I can. I am going to try to reboot the machine @ BluesKaj
[14:42] <BluesKaj> use the process tab
[14:42] <emma> the process tab?
[14:43] <emma> BluesKaj: it's probably pia_nw ?
[14:43] <BluesKaj> yes system monitor has 2 tabs, load and process
[14:43] <BionicMac> BluesKaj: May I ask you the quality of your connection with PIA? I'm comparing vpn providers atm.
[14:44] <emma> oh didn't know i was using system monitor. Where do I find that?
[14:44] <BionicMac> BluesKaj: really though, I should ask that question to you in another channel.
[14:44] <emma> oh i see it there
[14:45] <BluesKaj> BionicMac, PIA is quite good dependin on the server , NYC , Florida, Mexico are all very good , avoid LA , it's throttled
[14:46] <BionicMac> Have you done a speed test?
[14:46] <BluesKaj> Toronto, Montreal and Vancouver , and Seattle ,Texas as well
[14:47] <emma> BluesKaj: i have killed pia_nw
[14:47] <emma> I restarted firefox and it still connects to no pages.
[14:47] <BluesKaj> yes, I lose about 5% on the download and none on the upload on the googlr speed test https://www.google.ca/search?q=speed+test&oq=speed+test&aqs=chrome..69i57j69i60.8513j0j8&sourceid=chrome&ie=UTF-8
[14:48] <emma> "We're having trouble finding that site"
[14:48] <emma> BluesKaj: could this be a DNS thing?
[14:48] <emma> somehow the DNS settings got corrupted?
[14:48] <emma> and it things the DNS are by proxy or something?
[14:48] <BluesKaj> emma, try sudo dhclient in the cli
[14:49] <emma> em@nova:~$ sudo dhclient
[14:49] <emma> RTNETLINK answers: File exists
[14:50] <BluesKaj> ok now try the browser again
[14:50] <BluesKaj> emma I have my DNS settings set to my providers DNS recommends in my router
[14:50] <emma> not working. cannot find google.
[14:51] <BluesKaj> the router should be the best location to set your DNS
[14:51] <BluesKaj> can you ping google.com
[14:51] <emma> i don't have access to the router and this was a problem in two different households with two different routers
[14:51] <emma> yeah one sec
[14:52] <emma> em@nova:~$ ping google.com
[14:52] <emma> ping: google.com: Temporary failure in name resolution
[14:56] <BluesKaj> emma you could trty setting google DNS or your provider's DNS  in /etc/systemd/resolved.conf
[14:56] <emma> okay what is google's dns?
[14:56] <emma> 8.8.8.8 ?
[14:56] <BluesKaj> yes
[14:57] <BluesKaj> secondary is 8.8.4.4
[14:57] <BionicMac> My VPN provider's App has a setting called "network_lock". If that is set to "yes" it will block your internet traffic for security. I do not use or have experince with PIA but it could be a setting like this. Or it may be a default. BluesKaj can surely assist with PIa specifics since he uses the provider.
[14:58] <emma> [Resolve]
[14:58] <emma> DNS=8.8.8.8
[14:58] <emma> #FallbackDNS=
[14:58] <emma> #Domains=
[14:58] <BionicMac> clarification: the app will block internet traffic IF you lose your vpn connection that it.
[14:59] <emma> I removed the comment #  and put it to DNS=8.8.8.8
[14:59] <emma> is there some way to refresh that conf?
[14:59] <BluesKaj> BionicMac, I haven't seen that setting in PIA, but i don't use the GUI
[14:59] <emma> or do i have to reboot?
[14:59] <emma> @ BionicMac yeah i remember seeing something like that in a older version of PIA  -- I don't see that now but I'll look again.
[14:59] <BluesKaj> emma, not sure, but reboot to make sure :-)
[14:59] <BionicMac> BluesKaj: Yep, ok cool. Yes my provider has a cli interface only. (except for the browser extension)
[15:00] <emma> Im going to reboot now. See you guys as soon as I can.
[15:00] <BluesKaj> ok emma
[15:04] <emma> BluesKaj: just restarted -- the problem still persists. I can use ssh so I know I am connected to the internet
[15:04] <emma> but firefox won't connect to any page.
[15:04] <BionicMac> BluesKaj: If you have done a speed test with PIA, what are the results?
[15:04] <emma> im sure if i would now turn on PIA it would connect.
[15:05] <emma> firefox gives the error "hmm. we are having trouble finding that site'
[15:05] <emma> that's why I think this is a DNS thing
[15:05] <emma> it's not saying you are offline
[15:05] <emma> it says cannot find the site
[15:06] <diogenes_> emma, you could try with dnsmasq
[15:06] <emma> should i see if chrome also cannot connect?
[15:06] <emma> diogenes_: how's that?
[15:06] <diogenes_> emma, first see this: systemctl status NetworkManager
[15:07] <emma> chrome also will not work. It says 'the site cannot be found'.
[15:08] <emma> diogenes_: says it is active and running
[15:08] <diogenes_> ok let's see
[15:09] <diogenes_> it's gonna be a bit long process if you have time
[15:09] <emma> when i was able to get online i googled "Firefox won't connnect unless I am using VPN" and I got some stuff but I can't go to google now since it can't find the site
[15:10] <diogenes_> run: cat /etc/NetworkManager/NetworkManager.conf | nc termbin.com 9999
[15:10] <diogenes_> share the link
[15:11] <emma> em@nova:~$ cat /etc/NetworkManager/NetworkManager.conf | nc termbin.com 9999
[15:11] <emma> nc: getaddrinfo for host "termbin.com" port 9999: Temporary failure in name resolution
[15:12] <emma> this is the same error i get when i try: ping google.com
[15:12] <emma> it comes back with 'temporary failure in name resolution'
[15:12] <emma> I believe this is all the same problem.
[15:12] <emma> could you google: kubuntu temporary failure in name resolution
[15:12] <emma> I think if that can be solved then it would slove this?
[15:13] <diogenes_> ok you can create a new channel and you can use that channel for pasting direct output
[15:13] <diogenes_> and give me the name of the channel
[15:13] <emma> ok
[15:14] <emma> diogenes_: #temp
[15:59] <emma> diogenes_: well now my wireless dongle will not connect
[16:00] <emma> Previously the problem was that my wifi adapter would connect to the router but firefox would not work. Now my wireless adapter does not initialize.
[16:02] <emma> diogenes_: I need to use a usb wireless adapter because the built in wireless card on this laptop is so weak.
[16:02] <diogenes_> ok
[16:02] <diogenes_> I am on #temp
[16:05] <emma> Now the usb wireless adapter gets to configinuring interface in ntework manater and gthan fails
[16:05] <diogenes_> emma, let's talk in #temp
[16:05] <emma> Now I cannot even type here in irssi because the built in wireless card is so weak that i am lagging very very badly
[16:06] <emma> that's why i needed the wusb wireless adpeter
[16:06] <diogenes_> try to remove the previous wireless connections and connect again
[16:06] <diogenes_> also try systemctl restart NetworkManager
[16:11] <emma> this is painfully broken
[16:11] <emma> i can't type anything here
[16:12] <diogenes_> why is your wifi so weak? take your laptop closer to the access point so we can chat
[16:13] <D0U91E> 4 more sleeps til 18.04 LTS
[16:14] <BluesKaj> D0U91E, I'm already there
[16:14] <D0U91E> nice BluesKaj with beta 2 right?
[16:16] <BluesKaj> dunno, i just keep upgrading :-)
[16:16] <D0U91E> same...
[16:16] <D0U91E> once I chatted with you I got on the 18.04 - I think beta1 or earlier... weeks now tho
[16:19] <D0U91E> my 16.04 was giving me issues and there were more issues running 15.10 so I just went with the latest I could get of 18.04
[16:20] <emma> ouch
[18:11] <user|76292> hi kubuntu 18.04   I am having an update issue that I can solve this problem
[19:03] <BionicMac> emma: Did you correct you vpn connection issue?
[19:03] <BionicMac> emma: Just curious.
[19:03] <emma> BionicMac: yes got it fixed thanks to BluesKaj
[19:04] <BionicMac> WHat was the problem? I can scroll back but maybe you can put it short and sweet .. =)
[19:05] <emma> BionicMac: i do not understand the problem but i can tell you the solution.  Maybe you can tell me the problem because to me the solution seems so random and magical.
[19:05] <BionicMac> ok shoot
[19:05] <BionicMac> or should I scroll...
[19:05] <emma> The problem was this:  I run the PIA VPN and all of a sudden Firefox (or any other browser) was unable to open any webpage UNLESS the VPN was turned on.
[19:05] <emma> Here was the solution:
[19:06] <emma> (1) Install ifupdown
[19:06] <BionicMac> I like magically random things. =)
[19:06] <emma> (2) Edit etc/resolv.conf to say nameserver 127.0.0.53
[19:06] <emma> (it had previously said 127.0.0.1)
[19:06] <emma> and that was it.
[19:09] <BionicMac> hmmm ..
[19:17] <emma> BionicMac: this isn't the way we fixed it but it seems very likely to be the same problem: https://www.privateinternetaccess.com/forum/discussion/22079/can-no-longer-connect-to-internet-when-i-exit-pia-app-ubuntu-16-04
[19:17] <BionicMac> emma: I am curious about something: If you could run this and paste it somewhere? Are you still in #test ? ->> run this 'sudo systemd-resolve --status'
[19:18] <BionicMac> brb... give me about 5 minutes please.
[19:19] <emma> Yeah sure.
[19:19] <emma> BionicMac: you mean now while the vpn is turned off?
[19:19] <BionicMac> emma: more related discussio: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320n
[19:19] <BionicMac> aaaah ha
[19:19] <BionicMac> brb
[19:21] <BionicMac> emma: yes now please. then maybe you could run it after vpn is on and do some comparisons ... these are the important files [ /etc/resolv.conf ... and ... /lib/systemd/resolv.conf ** ( /lib/systemd/resolv.conf is static) ]
[19:22] <BionicMac> coffee is calling me.. brb
[19:23] <emma> BionicMac: here is what it looks like right now while the VPN is off: http://dpaste.com/0PPYV6W
[19:25] <BionicMac> emma: while it is off cat both of the resolv.conf files I just mentioned too. so 3 things in both states 1) cat /etc/resolv.conf ...2) cat /lib/systemd/resolv.conf ...3) 'sudo systemd-resolve --status' ... so all three tasks in each state please for comparison. without you having edited anything.
[19:26] <BionicMac> emma: I am curious about this because I an into dns issues setting vpn several times here. I do believe I am on the way to understanding "why". =)
[19:26] <BionicMac> s/I an/I ran/
[19:27] <emma> okay
[19:37] <marrow16180> kubuntu sucks
[19:40] <BluesKaj> good riddance :-)
[19:40] <BionicMac> BluesKaj: =)
[19:47] <BionicMac> emma: What do your two resolv.conf files look like right now while the vpn is off?
[19:49] <BionicMac> emma: plus, according to your paste you are getting dns from a lan ip 192.168.1.1 on a particular interface Link 6  ... while your global dns is set to google 8.8.8.8
[19:50] <BionicMac> My global and per interface are both set to the same servers.
[19:53] <emma> BionicMac: this is with vpn off: http://dpaste.com/1TWA5YC
[19:55] <BionicMac> looks the same. and you are connecting properly with both setups?
[19:56] <BionicMac> I'm real curious to see both resolv.conf fils in each state also.
[19:56] <BionicMac> So you have edited /etc/resolv.conf yourself though.
[19:57] <BionicMac> cn you 'cat /etc/resolv.onf' and 'cat /lib/systemd/resolv.conf' in both states?
[20:00] <BluesKaj> BionicMac, they both using the same nameserver 127.0.0.53  here
[20:02] <BionicMac> BluesKaj: ok . im just curious why tge hand edit is needed for emma though.
[20:02] <BionicMac> i under
[20:02] <BionicMac> the system shod take care of that ideally
[20:04] <BionicMac> sorry for thr mistype "i under" . switched to phone and my hands are big.
[20:21] <emma> BionicMac: well it's gone back to not working now
[20:22] <BionicMac> emma: ok, so did you checkout both resolv.conf files?
[20:22] <BionicMac> emma: before you edit them , while it is not resolving, cat both files and paste please.
[20:23] <emma> hey sorry i missed our chance for that.
[20:24] <BionicMac> emma: may as well look at 'sudo systemd-resolve --status' again also. If you don't mind pasting all of that it may help coming to a permanent solution other than editing the file every time.
[20:24] <emma> I already went to that resolv.conf and somehow it put itself back to 127.0.1.1
[20:24] <emma> so i put it to 127.0.0.53 again
[20:24] <emma> and now it works again.
[20:24] <BionicMac> emma: systemd-resolve is doing it. /etc/resolv.conf is dynamic.
[20:24] <emma> sorry i have to go now but i would love to find out why this happens later.
[20:25] <BionicMac> ok thanks. =)
[20:26] <Sakkn> hey guys
[22:35] <emma> BionicMac: I think /etc/resolv.conf probably reverts back when I unplug my USB wiress adapter. (Which I have to use).  As in, when I plug it in, NetworkManager sets it to 127.0.1.1
[22:36] <DiamondDish> s