I started experiencing this issue a while ago, probably not too long after OSX 10.9.1 update
(not sure about this but would make sense), while it was working just fine before.
I basically cannot access github.com at all, only when on WIFI. I also realized I cannot access Facebook either
Ethernet connection works correctly. I am using that machine 99% of the time at work, and I naturally put the blame on the Proxy used here, but then I brought it home and experienced the same issue from my wifi network.
My PC can access Github without problems over the same network. Colleagues can access Github over the same Wifi network as well.
The Error I am getting: "This webpage is not available / Unable to Connect"
I've tried all the following so far:
- Tried all available browsers, as well as from a VM (Virtual Box running Win8, configured in NAT).
- Rebooting, resetting PRAM
- Deleting the location profile (in network settings) and recreated it
- Enabled/Disabled Proxy settings
- Tethered connection from iPhone (it will just hang on "resolving host"
- Tried Different DNS (Google: 8.8.8.8, 8.8.4.4)
- Traceroute will throw:
traceroute: bind: Can't assign requested address
- Host file is clean
I literally don't know what to try next and try to isolate the problem
Being a Javascript developer, I don't need to say that it is hindering my work quite a bit;
Looks like some VPN config MIGHT be in cause here too:
I have Juniper Network Connect
installed to connect to a Client's VPN
When I am connected to the Client's VPN, I can access Facebook.com, but not Github.com
Any help is greatly appreciated!
Edit:
dig github.com output:
; <<>> DiG 9.8.3-P1 <<>> github.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41616
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;github.com. IN A
;; ANSWER SECTION:
github.com. 20 IN A 192.30.252.130
;; Query time: 32 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed May 7 15:34:52 2014
;; MSG SIZE rcvd: 44
Edit2: Fired Console App and got this output - probably the most helpful piece of info I've got:
2014-05-07 3:50:47.593 PM Google Chrome Helper[14672]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd. : LSXPCClient.cp #426 ___ZN26LSClientToServerConnection21setupServerConnectionEiPK14__CFDictionary_block_invoke() q=com.apple.main-thread
2014-05-07 3:50:47.593 PM Google Chrome Helper[14672]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd.
2014-05-07 3:50:47.601 PM Google Chrome Helper[14672]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
2014-05-07 3:50:47.876 PM Google Chrome Helper[14673]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd. : LSXPCClient.cp #426 ___ZN26LSClientToServerConnection21setupServerConnectionEiPK14__CFDictionary_block_invoke() q=com.apple.main-thread
2014-05-07 3:50:47.877 PM Google Chrome Helper[14673]: Process unable to create connection because the sandbox denied the right to lookup com.apple.coreservices.launchservicesd and so this process cannot talk to launchservicesd.
2014-05-07 3:50:47.882 PM Google Chrome Helper[14673]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1100)
Edit 3:
I tried killing the launchservicesd
process, which brought the machine to an unbearable crawl (it even had trouble registering click events O_o) so I shutdown and restarted and Lo! It now works O_O I am not sure I should mark this question as resolved as I feel we didn't find a cause/real fix yet, but for now things are fine. The question now is "until when"... Thanks for your help all
launchservicesd
process, which brought the machine to an unbearable crawl (it even had trouble registering click events O_o) so I shutdown and restarted and Lo! It now works O_O I am not sure I should mark this question as resolved as I feel we didn't find a cause/real fix yey, but for now things are fine. The question now is "until when"... Thakns for your help all